Agile testing approach in Testing Fundamentals - Build an Automation Script

Verify Agile Testing Cycle for User Story Completion

Preconditions (3)

Step 1: Review the user story acceptance criteria

Step 2: Write test cases based on acceptance criteria

Step 3: Execute test cases after development completes the user story

Step 4: Log any defects found during testing

Step 5: Verify defects are fixed and retest

Step 6: Confirm all acceptance criteria are met

Step 7: Demonstrate working feature in sprint review

✅ Expected Result: All acceptance criteria are verified as met with no open defects, and the feature is accepted in the sprint review

Automation Requirements - None (Manual process validation)

Assertions Needed:

Test cases cover all acceptance criteria

Defects are logged and resolved

Sprint review confirms feature completion

Best Practices:

Collaborate closely with developers and product owners

Use continuous feedback and quick iterations

Automate regression tests for repeated validation

Keep tests small and focused on user value

Automated Solution

The Agile testing approach is a collaborative and iterative process that integrates testing activities throughout the sprint. Since it involves manual collaboration and continuous feedback, automation scripts are not directly applicable to the entire process. Instead, testers write and automate test cases for user stories as they are developed, ensuring acceptance criteria are met. Defects are tracked and fixed quickly, and the team demonstrates the working feature in sprint review meetings. This approach emphasizes communication, quick feedback, and continuous improvement rather than a single automated script.

Common Mistakes - 3 Pitfalls

Waiting until the end of the sprint to start testing

Not involving testers in sprint planning

Ignoring automation of regression tests

Bonus Challenge

Now add automation scripts for regression tests that run after each sprint build

Show Hint