1 / 14

An Effective Agile Testing Framework

An Effective Agile Testing Framework. Anko Tijman. AN AGILE TESTING FRAMEWORK. 1. 2. 3. 4. 5. ACCEPTANCE TEST DRIVEN DEVELOPMENT. ATDD. Add test cases to requirements User stories Team Product owner + designer + developers + end user To ‘mould’ the thinking about requirements

jess
Télécharger la présentation

An Effective Agile Testing Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Effective Agile Testing Framework AnkoTijman

  2. AN AGILE TESTING FRAMEWORK 1 2 3 4 5

  3. ACCEPTANCE TEST DRIVEN DEVELOPMENT ATDD Add test cases to requirements • User stories • Team • Product owner + designer + developers + end user • To ‘mould’ the thinking about requirements • Start of sprint

  4. ACCEPTANCE TEST DRIVEN DEVELOPMENT ATDD www.testobsessed.com

  5. ATDD APPROACHES • Behaviour Driven Development • Dan North(dannorth.net) • GWT-format: • GIVEN <a situation> • WHEN <something happens> • THEN <I get a result> Specification by example • Gojko Adzic • Collaborative method for specifying requirements and tests specificationbyexample.com • ELSE <error message>

  6. UNIT AND INTEGRATION TESTING • (Regression) test automation • Helps refactoring • Developers and testers work together • Discuss requirements • Developer writes some unit tests • Discuss unit test cases • Code will pass tests  • Decide with your team who executes the Integration tests • “Any” user input can be validated at UT/IT level  Huge performance improvement for the team!

  7. UNIT AND INTEGRATION TESTING • Unit testing, regression testing and automated testing are not the same • Discuss what to (not) automate – as a team • Do more than automated checking!

  8. NON FUNCTIONAL TESTING • Feedback on the whole system • Potentially (!) shippable product • Quality attributes • Feedback within the iteration • If not possible: Pareto principle • ‘simple’ test techniques that manage the risks involved • Security: OWASP checklist (www.owasp.org) • Usability testing • Heuristic Evaluation (Jakob Nielsen) • Add this to your Sprint Definition of Done

  9. QUICK REFERENCE CARDS • Sharing information based on the Pareto principle • Condensed information about a topic • The essential parts of information • Any topic worth sharing  • Share the QRC’s!

  10. EXPLORATORY TESTING • Checking ≠ Testing • Checks look for ‘expected’ bugs • Find unexpected (!) bugs • Test cases that need human intelligence • Difficult to automate • Charters • Sharing and gaining knowledge • Risk based • Focus

  11. CONTINUOUS ACCEPTANCE • Agile: customer is near • Acceptance sessions in sync with demo • User representatives • IT-Support • Automated scripts & manual scenario • ‘Emotional acceptance’

  12. AN AGILE TESTING FRAMEWORK

  13. YOUR ROLE CHANGES

  14. I’m available on chat for Q&A. Come and join in! www.ordina.nl/blogswww.ordina.nl/agiletesten @agiletesternl paper.li/AgileOrdina

More Related