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
From discussion with @jonathanolson over in phetsims/axon#447, we thought there could be better support for CT to know when an infinite loop is. The solution in my mind is to add a new event that is added to each browser test: "test start". That way we don't overload what loading the page means, and we have better data about if we just never started the test (took too long to load (totally normal and fine)), or started but then never got a pass/fail (infinite loop?).
This may not be too hard, but wouldn't be something I could just squeeze in. It may be important enough over in phetsims/axon#447, but I doubt it will raise the priority of this issue.
The text was updated successfully, but these errors were encountered:
zepumph
changed the title
Add support for infinite loop testing
CT: Add support for infinite loop testing
Feb 14, 2024
From discussion with @jonathanolson over in phetsims/axon#447, we thought there could be better support for CT to know when an infinite loop is. The solution in my mind is to add a new event that is added to each browser test: "test start". That way we don't overload what loading the page means, and we have better data about if we just never started the test (took too long to load (totally normal and fine)), or started but then never got a pass/fail (infinite loop?).
This may not be too hard, but wouldn't be something I could just squeeze in. It may be important enough over in phetsims/axon#447, but I doubt it will raise the priority of this issue.
The text was updated successfully, but these errors were encountered: