Download as PDF, PPTX
Uploaded byR. Gesit Prasasti Alam, PSM®
Please don't test your product - Agile Testing
The document discusses the importance of being agile over creating perfect documentation upfront. It emphasizes that planning, development, and testing should be iterative processes. Automation, quality, and having fun with testing are important parts of an agile approach. The document promotes delivering working software in short cycles over attempting to make perfect documentation before starting work.
More Related Content
Similar to Please don't test your product - Agile Testing
Please don't test your product - Agile Testing
- 1.
- 2.
- 3. How many ofyou who thinks being Agile is important ?
- 5.
- 7. We want tomake the Awesome and perfect software bytryingtomakeperfect documentationupfront
- 8.
- 9. But those people who gavesign- offs rarely read those perfect documentat ions thoroughly
- 10. Good documentation (upfront) willnot guarantee you will get a good software
- 11.
- 12.
- 13. Design Development Testing Design Development Testing Planning Review Planning Review Design Dev Test Planning Review Design Dev Test Planning Review Delivering workingsoftware in short cycle Ever worse problem that Waterfall
- 15. How many ofyou who thinks being Agile is important ?
- 16. AUTomation. The heart ofagility
- 17. We still LOVEtheTesters !
- 18.
- 19.
- 20. Innovation or Die facingthe failure and create innovation
- 21. QUALITYQUALITY IS EVERYONE’SRESPONSIBILITY
- 22. AUTOMATEAUTOMATE THE ROUTINEVERY HELPFUL
- 23. TESTINGTESTING SHOULD BEFUN :)
- 24.
- 25.
- 26.
- 27. Go High Quality Agileis not just about Delivery Fast/Often, but its about Sustainbility of Quality
- 29. TESTED • Click Testing •Functional Test (A) • Unit Test / TDD (A) • Integration Test (A) • Stress Test (A) • Security Test (A) • Penetration Test • A/B Test (A) • Smoke Test (A) • Device Test (A) • BDD (A) DOCUMENTED • User Manual • Use Case • API Documentation ENGINEERING PRACTICES • Pair Programming • Code Review • Refactoring (Clean Code) • Continous Integration • Continous Learning KEY OBJECTIVES • Meet Acceptance Criteria • Performance … m/s definitionofdone
- 30. Every Journey begins witha Small Step. It’s About Investment
- 31.
- 32. Approaches Comparison Parameters ATDD TDD BDD UserInvolved and Scope Communication mechanism between Business user, Developer, Tester to ensure requirements are well documented Developer approach between developer and tester to create well written unit of code (module, class, function) Combination of ATDD andTDD
- 34.
- 35.
- 36.
- 37.
- 40.
- 42. Reverse proxy swapsinactive with active
- 43. How many ofyou who thinks being Agile is important ?