Agile testing
•
1 like•1,068 views
this is how we do our testing in scrum and some suggestions that help us to improve
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Agile testing
Similar to Agile testing (20)
Recently uploaded
Recently uploaded (20)
Agile testing
- 1. Testing is fun when you play it well Tanvir Afzal
- 2. Agile Testing Quadrants http://onestepbacktwostepsforward.blogspot.com
Editor's Notes
- Enjoy learning new skills, taking on new challenges, and they don't limit themselves to solving only testing issues. This isn't just a trait of testers; we see it in all agile team members. Agile testers help the developer and customer teams address any kind of issue that might arise. Testers can provide information that helps the team look back and learn what's working and what isn't.
- Check all the acceptance criteria (COS) for the sprint. Do regression all the tasks in the sprint. (Manual excluding those scenarios that is in automation) Run automated test scripts (including all the previous sprint scripts). We all know that last day of the sprint is always hard time because there is lot of tasks coming form dev. So take the most priority tasks. If needed take whole team in the game and enjoy the testing.
- The Time's Up! Heuristic : This, for many testers, is the most common one: we stop testing when the time allocated for testing has expired. The Dead Horse Heuristic : The program is too buggy to make further testing worthwhile. We know that things are going to be modified so much that any more testing will be invalidated by the changes.
- The Mission Accomplished Heuristic : We stop testing when we have answered all of the questions that we set out to answer. The Mission Revoked Heuristic: Our client has told us, "Please stop testing now." That might be because we've run out of budget, or because the project has been cancelled, or any number of other things.
- The Pause That Refreshes Heuristic: Instead of stopping testing, we suspend it for a while. We might stop testing and take a break when we're tired, or bored, or uninspired to test. There's another kind of pause, too: We might stop testing some feature because another has higher priority for the moment.