Continuous testing
Download as PPTX, PDF2 likes553 views
The document discusses the benefits of continuous testing in software development, emphasizing the importance of integrating testing throughout the development process. It suggests that collaboration between coders and testers, along with automation of various testing processes, can significantly reduce risks and costs associated with fixing bugs. Recommendations include including testers in sprints, automating smoke tests, and not postponing testing until the end of a sprint.
Continuous testing
- 1. Continuous Testing Breaking the Shackles of IV&V
- 2. A Little About Me… @brandonraines brandon.raines@shokuninadvisors.com
- 3. Where We are Now
- 6. Where We Should Go
- 7. Collapsing the “V” to the “I” 1. Analysis / Architecture 2. Design 3. Code / Unit Test 4. Integration Test 5. Acceptance Test Time 3. Test Driven Development 2. Design/ Integration Test 1. Analysis/ Acceptance Test Time
- 9. Coders and Testers Collaborate!
- 11. Continuous Integration Cycle Developer Deploy Server Version Control Repository 1. Check-in 2. Monitor changes 3. Update Build Workspace 4. Build 5. Run Tests CI Server 6. Send Build Report 7. Clean Build Deploy App
- 12. Be An Explorer With Your Testing
- 13. What are the Benefits • Reduce Risk • Cost of fixing now vs later - 30x cheaper • Easier to fix now when it’s fresh vs stale
- 14. What You Can Do Now • Include testing and testers as part of the sprint and the team • Automate the smoke test • Automate bug fixes • Don't wait till the end of the sprint to test • Establish a Work in Progress (WIP) Limit