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

James E Keenan

The Perl Conference - North America - 2017
Alexandria, Virginia
June 19 2017

Table of Contents

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

4. Individual Contributor
5. Include Tests in Your Patch
6. Run Entire Test Suite Before Mailing
7. Where Do I Send a Patch?

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

11. Smoke Testing
12. Patch Example: Locale-Codes
13. Committer Creates Smoke-testing Branch from Patch
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 Maintained by Tony Cook
21. Smoke Test Summary for Locale-Codes Patch
22. We Want Perl to Work "Everywhere"
23. A Concrete Example of Need for Testing Everywhere
24. A FreeBSD-10.3 Virtual Machine
25. FreeBSD-11.0 Released
26. A FreeBSD-11.0 Virtual Machine
27. lib/locale.t: Failures on FreeBSD-11.0
28. Two Months of Work

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

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

41. Summary
42. Thank You
43. References

44. Bonus Slides
45. Working with the Perl 5 Source Code
46. Fatalization During 5.25 Development Cycle
47. The "Go Test Suite Problem"
49. Individual Smoke Test Reports
50. Capture Compiler Warning
51. lib/locale.t: Failures on FreeBSD-11.0