#32270: Changing Django’s default test runner to be more robust
-----------------------------------+--------------------------------------
Reporter: Diptesh Choudhuri | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: testing | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by Diptesh Choudhuri):
* version: 3.1 => master
Old description:
> 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.
>
> Best,
> Diptesh
New description:
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.
Best,
Diptesh
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32270#comment:1>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.30a20a187950dc262fe81b6d7f6c709f%40djangoproject.com.
