Context Navigation

Changes between Version 3 and Version 4 of Ticket #1698, comment 13

v3	v4
9	9	When `coverage` is run from `bin/tahoe` using `@`, it gets the correct `PYTHONPATH`, and so does the script that it runs. This was one of the main motivations for adding `@`. Importantly, `bin/tahoe` will expand `@tahoe` to the absolute path of the support script --not its own path-- before invoking `coverage`. If it expanded `@tahoe` to its own absolute path, then the tests would still be running in a subprocess of `coverage` which wouldn't work for the same reason as above.
10	10
11		Which Python interpreter is used to run `coverage` (and therefore the tests suite) will be determined by the value of `sys.executable` in `bin/tahoe`.
	11	Which Python interpreter is used to run `coverage` (and therefore the test suite) will be determined by the value of `sys.executable` in `bin/tahoe`.
12	12
13	13	Note that tests that the test suite runs in a subprocess, e.g. `test_system.SystemTest.test_filesystem_with_cli_in_subprocess`, will not contribute to coverage. I don't know how to fix this. `trialcoverage` also had that problem.