Opened 3 months ago

Last modified 8 weeks ago

#28520 assigned New feature

Add --start-at/after options to runtests.py

Reported by: Marten Kenbeek Owned by: Marten Kenbeek
Component: Core (Other) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Change History (2)

comment:1 Changed 3 months ago by Marten Kenbeek

Has patch: set
Owner: changed from nobody to Marten Kenbeek
Status: newassigned
Last edited 3 months ago by Tim Graham (previous) (diff)

comment:2 Changed 8 weeks ago by Tim Graham

Component: UncategorizedCore (Other)
Needs documentation: set
Triage Stage: UnreviewedAccepted

A note in docs/internals/contributing/writing-code/unit-tests.txt would be useful.

Note: See TracTickets for help on using tickets.
Back to Top