#28520: Add --start-at/after options to runtests.py
------------------------------------------+------------------------
Reporter: Marten Kenbeek | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
When making changes that affect large parts of Django, there can often be
a lot of test failures. I commonly use the `--failfast` option to tackle
these one at a time. After encountering a test failure, I want to do one
of two things:
* Fix the error and test again.
* Skip the error and look for the next one.
In both cases you often have to rerun a large part of the test suite of
which you are fairly certain it passes, which can take a lot of time. In
the second case you either have to remove `--failfast` and manually check
for errors, or mark the test as an expected failure or skipped test.
I propose to add two options to Django's internal test suite, `--start-at`
and `--start-after`. Both allow you to specify a top-level module where
the test suite should start running tests. `--start-at` includes the
specified module, `--start-after` excludes it.
--
Ticket URL: <https://code.djangoproject.com/ticket/28520>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/047.12c0fadb3c6bf735a0f65bf012fb0c4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
