You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The order of tests matters, with some tests failing if the order is changed. As pytest does not isolate the environment between tests, some state can persist and influence the result of subsequent tests.
Initialising flags should be done each time and care should be taken when modifying/mocking of imports - as these may persist across suites(?).
Opened #23 to restore shared state after the response, inventory, TCLI, and end-to-end test fixtures. Scoped patches and flag savers replace persistent mocks/rebindings, including the end-to-end module's import-time inventory/accessor assignments.
All four fresh-process isolation regressions fail on current master and pass with the fix. The complete 99-test suite passes in both normal and reversed test-module order on Linux/Python 3.13. Verification used container-local snapshots after a Windows bind-mounted collection attempt timed out. Production code and existing assertions are unchanged.
Activity
vinsymoyya commentedon Nov 14, 2026
Opened #23 to restore shared state after the response, inventory, TCLI, and end-to-end test fixtures. Scoped patches and flag savers replace persistent mocks/rebindings, including the end-to-end module's import-time inventory/accessor assignments.
All four fresh-process isolation regressions fail on current master and pass with the fix. The complete 99-test suite passes in both normal and reversed test-module order on Linux/Python 3.13. Verification used container-local snapshots after a Windows bind-mounted collection attempt timed out. Production code and existing assertions are unchanged.