ISTQB agile tester exam - Conclusions about Certification
Download as PPTX, PDF2 likes697 views
This document discusses the ISTQB Agile Tester certification. It provides an overview of agile software development practices like Scrum, Kanban, and user stories. It discusses the tester's role in agile projects, including automating tests, collaborating with developers, and responding quickly to changes. It recommends preparing for the certification by reading materials from ISTQB and other sources, and gaining experience with agile testing practices on the job. Earning the ISTQB Agile Tester certification validates knowledge of agile principles and how to effectively test in agile environments.
ISTQB agile tester exam - Conclusions about Certification
- 1. ISTQB Agile Tester Conclusions about Certification Michał Dudziak 11.2015
- 2. List of things • Introduction • Software Development in Agile • Practices and Process • Techniques and Tools • Tester in Agile • Highlight • Prepare & worth reading • What to do next?
- 3. Introduction
- 4. Software Development in Agile Fundamentals of Agile Software Development: The Whole-Team Approach Early and Frequent Feedback Aspects of Agile Approaches: A lot of Scrum and Agile things (release planning, iteration planning, metrics, Speed Boat, Scrum, Kanban, User Stories) and....
- 5. Continuous Integration Benefits: + Early defect detection + Feedback on quality + Daily test releases + Lower regression risk + No big-bang integration + Less repetitive testing Risks: - The introduction and ongoing use of CI tools may fail - The CI process may not be adopted by team - Test automation costs too much or takes too long
- 6. Testing – principles ISTQB Testing shows presence of defects Exhaustive testing in impossible Testing early Defect clustering Pesticide paradox Testing is context dependant Absence-of-errors fallacy Agile Testing (Lisa Crispin) Provide continuous feedback Deliver value to the customer Enable face-to-face communication Have courage Keep it simple Practice continuous improvement Respond to change Self-organize Focus on people Enjoy
- 7. Test automation Goals of automated tests: Confirm that the build is functioning and installable Help to manage the regression risk Save Time and Money Improve Accuracy Increse Test Coverage
- 8. Managing Regression Risk Regression Testing Automation of Tests Continuous Integration
- 9. Independent Testing Other Agile teams retain fully independent, separate test teams, and assign testers on- demand during the final days of each sprint. This can preserve independence, and these testers can provide an objective, unbiased evaluation of the software. However, time pressures, lack of understanding of the new features in the product, and relationship issues with business stakeholders and developers often lead to problems with this approach.
- 10. Agile testing methods • Testing Methods TDD BDD ATDD • Many others...
- 11. Test pyramid • Emphasizes lower-lewel tests over upper-level tests • Automate unit and integration tests through API • Automate system and acceptance tests through GUI • Test pyramid concept is early QA and testing principle in action Acceptance System Integration Unit From ISTQB
- 12. Test levels Testing quadrants align the test levels with the appropriate test types in Agile methodology. It is useful to examinate whether the test are: • Business-facing • Technology-facing
- 13. RBT Risk-Based Testing: Reduce product (quality) risk to an acceptable level Lightweight techniques can be used: Identify quality risks Assess level of risk Estimate test effort Mitigate risks through test desigm, implementation and execution Short iterations and fast change have implications.
- 14. Test basis User stories, but also: • Experience from previous projects • Existing functions, features, and quality characteristics of the system • Code, architecture, and design • User profiles (context, system configurations, and user behavior) • Information on defects from existing and previous projects • A categorization of defects in a defect taxonomy • Applicable standards • Quality risks
- 15. As a Tester in Agile • Be competent in test automation, TDD, ATDD, white-box, black-box, and experience-based testing • Be positive and solution-oriented • Display critical, quality-oriented, skeptical thinking about the product • Actively acquire information from stakeholders • Accurately evaluate and report test results, test progress, and product quality • Work effectively to define testable user stories, especially acceptance criteria, with customer representatives and stakeholders • Collaborate within the team, working in pairs with programmers and other team members • Respond to change quickly • Plan and organize their own work
- 16. As a Tester in Agile Measuring Configuring Coaching Collaborating Participating Commited Empowered Self-organized Cross-functional
- 17. Do it better • Mind-Mapping: www.mindmup.com • Questioning - But what if? • Show me! - Talk to dev: show me how you fixed it • Static program analysis • Exploratory testing • Pairing with DEV (TDD – as a Navigator)
- 18. Prepare & worth reading • Everything from ISTQB: – Syllabus – Sample exam (only one set of questions) • Books: – Agile tester 2015 http://www.amazon.co.uk/Agile-Tester-2015-One-all/dp/1506131859/ – Agile Testing and More Agile Testing http://agiletester.ca/ • Web pages: – http://www.testingexcellence.com/category/agile-testing/ – http://www.testingexcellence.com/risk-based-testing-test-matters/ – http://www.testingexcellence.com/exploratory-testing-tips-best-practices/ – https://en.wikipedia.org/wiki/Static_program_analysis • Training: – Official Agile Certification Training offered by an Accredited Training Provider (2 days, optional) • Work: – Good approach and practises in your company can teach you a lot!
- 19. What to do next?
- 21. ISTQB Agile Tester Conclusions about Certification Michał Dudziak 11.2015