How Do We Assess and Maintain the Health of the Perl 5 Codebase?

James E Keenan

New York Perlmongers
May 24 2017

Table of Contents

1. Introduction
2. Where We're Going
3. Five Stages of Testing

4. Individual Contributor
6. Include Tests in Your Patch
7. Run entire test suite before mailing perlbug

8. Committer
9. Bug Report Copied to Perl 5 Porters
10. Triage by Committer

11. Smoke Testing
12. Patch Example
14. Test-Smoke
15. Test-Smoke Directories
16. Manual vs Automatic
17. test-smoke.org: Search Options
18. test-smoke.org: Results by Platform
19. test-smoke.org: Individual Platform
20. perl.develop-help.com
21. Smoke Test Summary for Locale-Codes Patch
22. Why Is Diversity Important?
23. I Set Up a FreeBSD Virtual Machine
24. Capture Compiler Warning
25. I Set Up Another FreeBSD Virtual Machine
26. lib/locale.t: Failures on FreeBSD-11.0
27. Two Months of Work

28. CPANtesters
29. Test Results by Perl Version and Platform
30. BBC Bug Tickets
31. How We Handle "Blead Breaks CPAN"
32. Importance of Testing CPAN against Perl 5 Blead
33. Security Problem During 5.25 Development Cycle
34. Secondary Test Suite: All of CPAN
35. The "DarkPAN": Perl in Production
36. Fatalization During 5.25 Development Cycle

37. Outer World
38. The "Autoconf Problem"
39. Autoconf Presumes '.' in @INC
40. The "Go Test Suite Problem"
42. Next Steps: A Tertiary Test Suite?
43. A Tertiary Test Suite

44. Summary
45. Thank You
46. References