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
In theory, tests should each receive a rr fixture that corresponds to an isolated instance of the rerun-sdk module. Somehow. In practice, maybe some Python module shenanigans might achieve that (needs to be researched and experimented with).
The text was updated successfully, but these errors were encountered:
abey79
changed the title
Global SDK state (mainly: strict mode) is not correctly handled in our Python test suite (
Global SDK state (mainly: strict mode) is not correctly handled in our Python test suite
Nov 6, 2024
Our Python test suite handles extremely bad the global state of the SDK, which leaks from tests to tests.
Symptom
For example, the suite currently passes if run in its entirety:
If you run only the quaternion suite, it fails:
Why? Because that test expect strict mode but doesn't set it. It just happens to be set by the previous test(s) in the suite.
Proof:
Solution
In theory, tests should each receive a
rr
fixture that corresponds to an isolated instance of thererun-sdk
module. Somehow. In practice, maybe some Python module shenanigans might achieve that (needs to be researched and experimented with).The text was updated successfully, but these errors were encountered: