Changing Django’s default test runner to be more robust

[Diptesh Choudhuri]

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

[Aditya parashar]

yes you can there are many good advantages that I see by viewing through There are a lot more features overall, but I think one major reason people use nose/djano_nose is that it allows you to very easily do code coverage. nose comes with a number of builtin plugins to help you with output capture, error introspection etc . So sure you can do it I Don't know pytest much

[Mariusz Felisiak]

Anyone who has used pytest with django will immediately agree that it is much more pleasurable to work with, ...

We shouldn't generalize, I've used pytest but I don't agree that it's much better then Django's test runner.

I think it's basically a duplicate of #25707.