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
After a testrun with failing tests, the next run could provide useful results faster by running the failed tests first. Within the two categories, failed and passed, tests could be ordered by runtime, running tests that take less time first.
Need to figure something out to gather the necessary stats and persist them. Idea: Hidden input/textarea, filled with joined-array of testname|pass/fail|runtime, eg. "jsDump.parse|pass|12". Read that before running tests again, eg. in QUnit.init().
Non-browser runtimes would require a different storage, so the persistance should be abstracted.
The text was updated successfully, but these errors were encountered:
Instead of reordering the actual results, try to defer execution of low-priority tests, eg. by having the test call synchronize again to put itself at the end of the queue.
After a testrun with failing tests, the next run could provide useful results faster by running the failed tests first. Within the two categories, failed and passed, tests could be ordered by runtime, running tests that take less time first.
Need to figure something out to gather the necessary stats and persist them. Idea: Hidden input/textarea, filled with joined-array of testname|pass/fail|runtime, eg. "jsDump.parse|pass|12". Read that before running tests again, eg. in QUnit.init().
Non-browser runtimes would require a different storage, so the persistance should be abstracted.
The text was updated successfully, but these errors were encountered: