Testing your Plone codebase with Pytest
summary
Plone 6 projects move from old unittest layers to Pytest by switching the runner and adding the pytest-plone plugin, replacing verbose setup with fixtures like installer and browser_layer, and keeping legacy tests runnable during migration; example conversions show collective.case study tests, content-rule tests and a notifier tested with httpx mocked notifier and parameterized behaviors, cutting boilerplate and speeding runs across a 10,000-test corpus while preserving integration checks and upgrade-step testing.
AI-written summary · about
chapters (12)
- 0:00Introduction and thanks
- 1:11What is Plone CMS
- 6:04Testing in Plone history
- 9:14Why switch to pytest
- 13:25Introducing pytest-plone
- 16:10Testing Plone integrations
- 17:59Case study testing demo
- 27:32Content rules testing
- 33:37Future of testing in Plone
- 34:20Why choose Plone
- 35:42Community and resources
- 36:44Closing and contact
related talks
29mAdopt-a-pytest
03h 02mdef test_crash_course_with_pytest()
27mWhy I use py.test and maybe you should too
32mpytest for unittesters
27mPyTest
30mHow to build a unit testing library from scratch?
28m"WHAT IS THIS MESS?" - Writing tests for pre-existing code bases
24mGiven this, assert that: fluent testing using fixtures and properties