When publishing open source projects, it’s important to give developers confidence that your project is error free and has a certain level of quality. This talk will cover the best practices in testing your open source project and giving people the confidence in using your project. No matter your experience, no matter the language you use, what operating system you use, you can use these techniques in your private and public open-source projects.

1. Best Practices for Testing
*Open Source Projects

2. Best Practices for Testing
Closed Source Projects

5. • Objectively Understand the Quality
• Stakeholders Understand the Risks
• Find Bugs / Test for Regressions

10. is most visible to humans
is “irritating”
is stop

11. 1. Some Evolutionary Psychology Thing
2. Coincidence

15. Running tests in the cloud when code submitted to source control.

16. 1. Helps find errors on another computer
1. No more “It works on my machine”
2. Tests pull requests from other developers
3. Notifies you of issues after merging / tagging
4. Gives you a badge

20. 1. The process to measure your code is covered
guarantee the quality of the code
3. Gives you a badge

21. Codecov Coveralls

25. Snyk

26. 1. Add A Contributors File
1. Teach how to contribute
2. Delegate
1. Give people projects and get them to test too
2. Even if you want to learn the thing
3. Coach / Be Nice
4. Celebrate Newcomers

27. • Test your docs
• Adds value to docs
• Easy first contributions

29. Questions?