#15051 closed (wontfix)
django.test.reorder_suite isn't a stable sort
| Reported by: | w004dal | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | 1.2 |
| Severity: | Keywords: | ||
| Cc: | w004dal@… | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I have run into cases where tests must run in a specific order (ie. if I'm going to test terminating the web server and see how the web services behind it respond, then I want that test to run last).
The reordering and grouping of tests together in django.test.reorder_suite isn't a "stable sort".
If all of the tests are of the same type, then if I have an array of tests called 'x', then for all permutations of the elements of 'x', stable_sort(x) == x.
Change History (3)
comment:1 by , 14 years ago
| Cc: | added |
|---|
comment:2 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , 14 years ago
What about a general wisdom to "fail early and fail fast"? Wouldn't it be a 'nice-to-have' to run them in ascending order of cost?
Note:
See TracTickets
for help on using tickets.
Unit tests, by definition, can be run in any order. If you have tests that need to run in a particular order, then you don't have unit tests.