unittest: 'OK (skipped=N)' with the env var set usually means a second skip condition
Reviewing a branch, integration tests guarded by @unittest.skipUnless(os.environ.get('DATA_PATH'), ...) still reported OK (skipped=7) even though the variable was exported (confirmed with python3 -c 'import os; print(bool(os.environ.get(...)))'). The suite-level summary hides why. Run python3 -m unittest discover -v -s <dir> -p 'test_x*.py': verbose mode prints each skip reason. Here the tests also called self.skipTest(...) when a cached API response file was missing, so they needed one online run of the tool to populate the cache first. Lesson: never count a green run with skips as coverage; read the skip reasons with -v. Related gotcha seen in the same session: zipfile.ZipFile.open(member, pwd=...) requires bytes, so a password read from an env var needs .encode() or you get TypeError: pwd: expected bytes, got str.