









Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An in-depth exploration of agile testing methodologies, focusing on test-driven development (tdd), acceptance test-driven development (atdd), behavior-driven development (bdd), and the agile testing lifecycle. It delves into the skills required for a tester in an agile team, the agile tester's role, test planning, sprint zero, integration, and agile testing practices. The document also discusses test progress tracking methods such as scrum boards, burndown charts, and automated test results.
Typology: Slides
1 / 15
This page cannot be seen from the preview
Don't miss anything!










- Test-Driven Development (TDD) − Test-Driven Development (TDD) is based on coding guided by tests. - Acceptance Test-Driven Development (ATDD) − Acceptance Test-Driven Development (ATDD) is based on communication between the customers, developers and testers and driven by pre-defined Acceptance Criteria and Acceptance Test Cases. - Behavior-Driven Development (BDD) − In Behavior-Driven Development (BDD) testing is based on the expected behavior of the software being developed.
In the Agile Lifecycle, a tester plays a significant Role in −
- Commitment − Committing to understanding and evaluating the product’s behavior and characteristics as required by the customers and stakeholders. - Transparent − Open, Communicating and Accountable. - Credibility − Ensuring the credibility of the test strategy, its implementation, and execution. Keeping the customers and stakeholders informed on the test strategy. - Open to Feedback − Participating in sprint retrospectives to learn from both successes and failures. Seeking customer feedback and acting quickly and appropriately to ensure quality deliverables. - Resilient − Responding to changes.
In Agile, a quality working product should be ready for release at any point of time in the development lifecycle. This implies continuous integration as a part of development. An Agile tester needs to support continuous integration with continuous testing. To accomplish this, a tester needs to −
An Agile tester needs to adapt Agile practices for testing in an agile project.
- Pairing − Two team members work together at the same keyboard. As one of them tests, the other reviews/analyzes testing. The two team members can be - One tester and one developer - One tester and one business analyst - Two testers - Incremental Test Design − Test cases are built from user stories, starting with simple tests and moving to more complex tests. - Mind Mapping − A mind map is a diagram to organize the information visually. Mind mapping can be used as an effective tool in Agile testing, using which information regarding the necessary test sessions, test strategies and test data can be organized.