The realities of open source testing: lessons learned from “Adopt pytest month”
summary
A month-long pairing program pairs 26 pytest helpers with open-source projects, resulting in 8 projects officially participating and 4 informal cases; two projects are open-sourced specifically for the event. Helpers convert and write tests, add fixtures and plugins, update CI and one project ships a pytest-friendly release. Reported effort ranges up to 80 hours, five helpers say they would repeat it, and maintainers who respond keep using pytest — concrete conversions, plugin updates and a measurable multiplier effect decide whether it worked.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 3:04Sign up the tightest helpers
- 4:40Sign up open source projects
- 5:42Adopt pytest month projects
- 7:57Adopt pytest month activities
- 8:55Protest helpers
- 9:37Time commitment
- 11:57Survey results
- 13:05The feedback
- 13:25Observations
- 14:25Expectations
- 15:49Advocates
- 17:03Code review
- 17:17Opensource projects
- 19:41Open Source Maintainer
- 20:01Suggestions for Open Source Maintainer
- 21:58Conclusion
- 22:48Thank you
- 23:06Next steps
- 23:31Advertising
related talks
29mAdopt-a-pytest
28mHow I migrated a huge OSS project to use pytest
28mEgad! How Do We Start Writing Better Tests?
27mWhy I use py.test and maybe you should too
45mPatterns to Whole-Team Test Automation Transformation
29mEgad! How Do We Start Writing (Better) Tests?
21mDon't just test, my friend, test better
32mpytest for unittesters