Testing - Best Practices in Open Source World
summary
Shows how to create a test harness for open source projects, with concrete steps to add automated tests, integrate them into CI pipelines, and measure coverage so regressions get caught earlier. Explains how to alter your development model toward continuous testing and code review practices that reduce bugs, gives rules for when to file a bug versus fix locally, and gives hands-on troubleshooting steps for reproducing, isolating and patching defects in community projects.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:57Testing - Best Practices in Open Source World By: Amita Sharma, Senior QA at Red Hat
- 3:38Testing is the best way to start with - It is the best way to learn new things. Manual/automation Testing, Functional Testing, Feature Testing. - Test plans, Test case, Test Days, Bug reporting, Testing release candidates, Bug verification, Automation framework - Reporting bugs & Testing patches
- 6:48Executing tests using test library and generating reports. - Test scripts should be able to handle different test data and test scenarios. - Automated test frameworks
- 9:42Include Testing in Development How that can be done???
- 11:51Test Driven Development Try to use OOP - Avoid bug prone code Include Unit Testing - Continuous Integration
- 16:30Bugs - Know difference between error, BUG, fault, failure - Bug tracking Tools Writing bug report - Using tools - ABRT - Follow-ups with verification and validation
- 18:58Troubleshooting - Logs logs and logs - Read code - Use tools like valgrind etc.
related talks
26mMake a career out of Opensource Software testing
35mMigrating Testing to Open Source
15mHow Can Testers Contribute to Open-Source Projects
15mUltimate Guide on Starting Your Open Source Journey
30mBest Practices for Accelerating Continuous Testing
22mA beginner's guide to Open Source
42mUse testing to Develop Better Software Faster
15mTransforming Testing: The Power of TestOps