Downloaded 76 times
Uploaded byZbyszek Mockun
Test Strategy
The document outlines a test strategy developed by Zbyszek Moćkun, detailing methodologies like the V Model and Agile approaches, alongside planning, execution, and metrics for testing. It emphasizes the importance of coverage, avoiding test duplication during regression, and the adaptability of testing processes like BDD, TDD, and continuous integration. Additionally, it includes references to sources and highlights the need for effective reporting and evidence of test case management.
More Related Content
Test Strategy
- 1. Test Strategy Zbyszek Moćkun © 2010 Cognifide Limited. In commercial confidence only.
- 2. Agenda 1. V Model 2. Agile Way 3. Test Planing 4. Control & Execution 5. Metrics 6. Demo © 2010 Cognifide Limited. In commercial confidence only.
- 3. V Model Perfect world © 2010 Cognifide Limited. In commercial confidence only.
- 4. V Model •Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 5. Preventive or reactive • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 6. Test Pyramid • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 7. Agile New way? © 2010 Cognifide Limited. In commercial confidence only.
- 8. Agile Manifesto • Coverage • Do not duplicate tests during regression • Test specific functionality Source: blog.twg.ca © 2010 Cognifide Limited. In commercial confidence only.
- 9. Agile against waterfall Coding,new functionality Requirements Bug fixing Design Coding Testing Testing Release Release Iteration © 2010 Cognifide Limited. In commercial confidence only.
- 10. Agile ways Processes Methodologies • Coverage ATDD Kanban • Do not duplicate tests during regression • Test specific BDD Scrum functionality TDD XP © 2010 Cognifide Limited. In commercial confidence only.
- 11. Continuous Integration • Coverage • Do not duplicate tests during regression • Test specific functionality Source: http://wiki.mxunit.org © 2010 Cognifide Limited. In commercial confidence only.
- 12. Reactive approach? • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 13. Scripting issues • Scriptedtesting report phase All Executed passed failed Test design phase 80 0 0 0 First day 90 (4 updated) 20 16 4 Second day 95 (10) 75 65 10 Third day 120 (14) 75 73 2 Fourth day 125 (16) 110 98 12 • Not all founded issues are against test case • Test case number means nothing (James Bach) • New test scripts added almost each day • Old onces are updated © 2010 Cognifide Limited. In commercial confidence only.
- 14. Test Planning © 2010 Cognifide Limited. In commercial confidence only.
- 15. What am Idoing here? Source: http://arborosa.org/tag/test-planning/ • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 16. Test Strategy /Test Plan Source: http://technet.microsoft.com • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 17. Control and Execution © 2010 Cognifide Limited. In commercial confidence only.
- 18. Coverage Requirements • Coverage Manaul Tests • Do not duplicate tests during regression • Test specific functionality Automated Tests © 2010 Cognifide Limited. In commercial confidence only.
- 19. Execution Test Suite • Coverage Test Run • Do not duplicate tests during regression • Test specific functionality Test Case status © 2010 Cognifide Limited. In commercial confidence only.
- 20. Traceability •Coverage • Do not duplicate tests during regression • Test specific functionality Source: http://www.tuleap.com © 2010 Cognifide Limited. In commercial confidence only.
- 21. Entry and ExitCriteria • Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 22. Reports •Coverage • Do not duplicate tests during regression • Test specific functionality © 2010 Cognifide Limited. In commercial confidence only.
- 23. Regression © 2010 Cognifide Limited. In commercial confidence only.
- 24. Retest or regression? Source: http://www.softwaretestinghelp.com © 2010 Cognifide Limited. In commercial confidence only.
- 25. Automation Source: http://blog.jugnoo.com © 2010 Cognifide Limited. In commercial confidence only.
- 26. Metrics Find what youneed © 2010 Cognifide Limited. In commercial confidence only.
- 27. Compare and improve © 2010 Cognifide Limited. In commercial confidence only.
- 28. Q&A © 2010 Cognifide Limited. In commercial confidence only.
- 29. PTaQ Poznań Testing andQuality Group © 2010 Cognifide Limited. In commercial confidence only.
- 30. Demo Test Case Management © 2010 Cognifide Limited. In commercial confidence only.