Anthony Sottile and Brian discuss changes that would be cool for pytest, even unrealistic changes. These are changes we'd make to pytest if we didn't ahve to care about backwards compatibilty.

Anthony's list:

The import system
Multi-process support out of the box
Async support
Changes to the fixture system
Extend the assert rewriting to make it modular
Add matchers to assert mechanism
Ban test class inheritance

Brian's list:

Extend assert rewriting for custom rewriting, like check
pytester matchers available for all tests
Throw out nose and unittest compatibility plugins
Throw out setup_module, teardown_module and other xunit style functions
Remove a bunch of the hook functions
Documentation improvement of remaining hook functions which include examples of how to use it
Start running tests before collection is done
Split collection and running into two processes
Have the fixtures be able to know the result of the test during teardown

Links:

Help support the show AND learn pytest:

The Complete pytest course is now a bundle, with each part available separately.
- pytest Primary Power teaches the super powers of pytest that you need to learn to use pytest effectively.
- Using pytest with Projects has lots of "when you need it" sections like debugging failed tests, mocking, testing strategy, and CI
- Then pytest Booster Rockets can help with advanced parametrization and building plugins.
Whether you need to get started with pytest today, or want to power up your pytest skills, PythonTest has a course for you.

★ Support this podcast on Patreon ★

Amanda Lehmann Preparing for the Steve Hackett Tour, Solo Gigs and New Album News