Opened 4 years ago
Last modified 4 years ago
#32270 closed New feature
Changing Django’s default test runner to be more robust — at Version 2
Reported by: | Diptesh Choudhuri | Owned by: | nobody |
---|---|---|---|
Component: | Testing framework | Version: | dev |
Severity: | Normal | Keywords: | testing |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
The default django test runner gets the job done, but it (and the entire django codebase) can benefit from a more robust runner, like pytest or nose. I will take the example of pytest because I am familiar with it and it is more widely used.
Anyone who has used pytest with django will immediately agree that it is much more pleasurable to work with, albeit a bit more intimidating. I intend work on the intimidating part and make it easier by adding a lot of documentation.
Please let me know your opinions on this topic. If it gets traction, I will work on compiling a list of what pytest has over the default runner, and what I intend to do to solve all of this.
NOTE: If accepted, this will be my proposal for GSoC 2021 to the Django Organization.
EDIT: I also made a post about this in the django developers google group (https://groups.google.com/g/django-developers) but for some reason, it said that it needs to be approved before being moade available to the public. If someone could look into that, it'd be great.
Best,
Diptesh
Change History (2)
comment:1 by , 4 years ago
Description: | modified (diff) |
---|---|
Version: | 3.1 → master |
comment:2 by , 4 years ago
Description: | modified (diff) |
---|