Agile testing

1,863 views

Published on

this is how we do our testing in scrum and some suggestions that help us to improve

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,863
On SlideShare
0
From Embeds
0
Number of Embeds
513
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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.
  • Agile testing

    1. 1. Testing is fun when you play it well Tanvir Afzal
    2. 2. Agile Testing Quadrants http://onestepbacktwostepsforward.blogspot.com
    3. 3. Principles of Agile testers: <ul><li>Provide continuous feedback. </li></ul><ul><li>Deliver value to the customer. </li></ul><ul><li>Enable face-to-face communication. </li></ul><ul><li>Have courage. </li></ul><ul><li>Keep it simple. </li></ul><ul><li>Practice continuous improvement. </li></ul><ul><li>Respond to change. </li></ul><ul><li>Self-organize. </li></ul><ul><li>Focus on people. </li></ul><ul><li>Enjoy. </li></ul>
    4. 4. Testers role in Agile: <ul><li>Enjoy learning new skills, taking on new challenges, and they don't limit themselves to solving only testing issues. </li></ul><ul><li>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. </li></ul>
    5. 5. woWsome SCRUM !! <ul><li>In SCRUM all the team members are transparent to each other and each member knows about the progress of the project. </li></ul>
    6. 6. Sprint planning ? <ul><li>Test team is a part of development team </li></ul><ul><li>Get design mockup in planning for writing test case. </li></ul><ul><li>Testers also estimate for each tasks so that they can stick and have a clear overview on what they are going to do and how long it will take. </li></ul>
    7. 7. Sprint planning ? (cont) <ul><li>If the test time is overloaded take the most priority works first. </li></ul><ul><li>Create manual test cases after planning meeting </li></ul><ul><li>Create feature files for test automation according to what is written in manual test case. </li></ul>
    8. 8. What’s in sprint ? <ul><li>Testers do their automation (feature file) and then do manual testing. </li></ul><ul><li>Regression test (using automation or manual) of those fixed issues that was reported to Jira. </li></ul><ul><li>Discuess with owner about any </li></ul>
    9. 9. The final touch <ul><li>Check all the acceptance criteria (COS) for the sprint. </li></ul><ul><li>Do regression all the tasks in the sprint. (Manual) </li></ul><ul><li>Run automated test scripts (including all the previous sprint scripts). </li></ul><ul><li>Keep note of those failed test case or COS. </li></ul>
    10. 10. Pair testing <ul><li>With testers </li></ul><ul><ul><li>Distribute knowledge between testers </li></ul></ul><ul><li>With developers </li></ul><ul><ul><li>Testers learn about the technology used and about </li></ul></ul><ul><li>automation </li></ul><ul><ul><li>Developers learn about testing </li></ul></ul><ul><li>With customers </li></ul><ul><ul><li>Testers learn about the domain </li></ul></ul><ul><ul><li>Customers learn about testing </li></ul></ul>
    11. 11. When to stop testing? <ul><li>The Time's Up! Heuristic : </li></ul><ul><ul><li>This, for many testers, is the most common one: we stop testing when the time allocated for testing has expired. </li></ul></ul><ul><li>The Dead Horse Heuristic : </li></ul><ul><ul><li>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. </li></ul></ul>
    12. 12. When to stop testing? <ul><li>The Mission Accomplished Heuristic : </li></ul><ul><ul><li>We stop testing when we have answered all of the questions that we set out to answer. </li></ul></ul><ul><li>The Mission Revoked Heuristic: </li></ul><ul><ul><li>Our client has told us, &quot;Please stop testing now.&quot; That might be because we've run out of budget, or because the project has been cancelled, or any number of other things. </li></ul></ul>
    13. 13. When to stop testing? <ul><li>The Pause That Refreshes Heuristic: </li></ul><ul><ul><li>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. </li></ul></ul>
    14. 14. Release? <ul><li>Live deployment should not be committed before testing or green signal. </li></ul><ul><li>All deployment needs to go to staging then test then to production. </li></ul><ul><li>“ NO DEPLOYMENT” to production before GREEN SIGNAL from QA. </li></ul>
    15. 15. Reference: <ul><li>http://www.developsense.com </li></ul><ul><li>http://www.testway.se/download/Seminar9/Agile%20Testing.pdf </li></ul>

    ×