Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test reordering for faster results #49

Closed
jzaefferer opened this issue Nov 4, 2010 · 2 comments
Closed

Test reordering for faster results #49

jzaefferer opened this issue Nov 4, 2010 · 2 comments

Comments

@jzaefferer
Copy link
Member

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.

@jzaefferer
Copy link
Member Author

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.

@jzaefferer
Copy link
Member Author

Defer test execution when previous run passed, persisted via sessionStorage. Closed by f32d1c9

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant