User story as working software :        testing activities       Shirly Ronen-Harel            Sep 2010
User story related testing                                                           Task                                 ...
User story related testing                                                                            Task                ...
Goal :Find defects
Goal :Find defects
Preventing Defects!
Userstory
Task             TaskUser story
Test early!                     Task                     Task        User story
Test early!                       Task                       Task          User story                       Working softw...
Test early!                           Task                            Task              User storyAcceptancecriteria      ...
Test early!Acceptance                 Taskcriteria                    Task              User story    ATDD                ...
Test early!Acceptance                             Taskcriteria                      Task     ATDD       User story        ...
Test early!Acceptance                           Taskcriteria                    Task      ATDD    User story       Team   ...
Test early!Acceptance                             Taskcriteria                      Task     ATDD       User storyPlanning...
Test early!Acceptance                                  Taskcriteria                           Task     ATDD            Use...
Test early!Acceptance                                         Taskcriteria                                  Task     ATDD ...
Test early!Acceptance                                            Taskcriteria                                     Task    ...
Test early!Acceptance                                          Taskcriteria                                   Task     ATD...
Test early!Acceptancecriteria               User             Task                                         Task     ATDD   ...
Test early!Acceptance                                             Taskcriteria                                      Task  ...
Test early!Acceptance                                            Taskcriteria                                     Task    ...
Test early!Acceptance                                          Taskcriteria                                   Task     ATD...
Test early!Acceptance                                            Taskcriteria                                     Task    ...
Test early!Acceptance                                            Taskcriteria                                     Task    ...
Unit tests pass                                 Functional,                                  (exploratory)User story User ...
Mini hardening phase  • Making sure a functional area is stable – working    software  • Few hours to 1-2 days - top  • Ta...
Workingsoftware         Working                 software   US                US    US                US      US           ...
Functional Automated Test TypesUnit Test          Every piece of code              Continuous on every                    ...
Type                MeasurementsSanity        Integration         After each build creation ,                             ...
Shirly Ronen - User story testing activities
Upcoming SlideShare
Loading in...5
×

Shirly Ronen - User story testing activities

38,298

Published on

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

No Downloads
Views
Total Views
38,298
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Shirly Ronen - User story testing activities

  1. 1. User story as working software : testing activities Shirly Ronen-Harel Sep 2010
  2. 2. User story related testing Task User story Task User story Task User story Task Task Release Task Task Task Task Product High level planning Detailed planningPlanning : Product –> Release -> Iteration –> User stories - > Tasks testing
  3. 3. User story related testing Task User story Release Unit tests Peering Planning /performing : Product [Development environment Acceptance test tests] Functional tests Regression High level planning : Mini hardening!? Sprint 0 Approach Scope Functional tractability to tests r a n n o t t g e i iPlanning : Product –> release -> iteration –> user stories - > Tasks testing
  4. 4. Goal :Find defects
  5. 5. Goal :Find defects
  6. 6. Preventing Defects!
  7. 7. Userstory
  8. 8. Task TaskUser story
  9. 9. Test early! Task Task User story
  10. 10. Test early! Task Task User story Working software
  11. 11. Test early! Task Task User storyAcceptancecriteria Working software
  12. 12. Test early!Acceptance Taskcriteria Task User story ATDD Working software
  13. 13. Test early!Acceptance Taskcriteria Task ATDD User story Working software
  14. 14. Test early!Acceptance Taskcriteria Task ATDD User story Team Working software
  15. 15. Test early!Acceptance Taskcriteria Task ATDD User storyPlanning functional tests ,regression , integration,customer ?tests? other tests Working software
  16. 16. Test early!Acceptance Taskcriteria Task ATDD User story Planning functional tests , regression , integration ,customer ?tests? other tests Automating tests Working software
  17. 17. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with Planning functional developer (per task/s)– tests , regression , Automating integration ,customer tests understanding the ?tests? other tests development approach Working software
  18. 18. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with developer (per task/s)– understanding Planning functional the development tests , regression , approach Automating integration ,customer tests ?tests? other tests Coding (with tdd) Working software
  19. 19. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with developer (per task/s)– understanding the development approach Planning functional tests , regression , Automating coding integration ,customer tests ?tests? other tests Unit testing execution Working software
  20. 20. Test early!Acceptancecriteria User Task Task ATDD story Testers are Peering with developer (per task/s)– understanding the development Planning approach functional tests , Automating regression , tests coding integration Unit testing ,customer ?tests? execution other tests Peering – Testing on development environment (automation or manual) Working software
  21. 21. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with developer (per task/s)– understanding the development Planning functional approach tests , regression , Automating coding integration ,customer tests ?tests? other tests Unit testing execution Peering – Testing on development environment Working software
  22. 22. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with developer (per task/s)– Unit tests pass understanding the Planning functional development approach tests , regression , Automating coding integration ,customer tests ?tests? other tests Unit testing execution Peering – Testing on development environment Working software
  23. 23. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with Unit tests pass developer (per task/s)– understanding the Planning functional development approach Functional, tests , regression , Automating coding (exploratory) integration ,customer tests ?tests? other tests Performing/ automation Unit testing Acceptance (and with PO). execution Regression Peering – Testing on Defining mini hardening development environment Working software
  24. 24. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with Unit tests pass developer (per task/s)– understanding the Functional, Planning functional development approach (exploratory) tests , regression , Automating coding Performing/ automation integration ,customer tests Acceptance (and with ?tests? other tests PO). Unit testing Regression execution Defining mini hardening Peering – Testing on development environment Working software
  25. 25. Test early!Acceptance Taskcriteria Task ATDD User story Testers are Peering with Unit tests pass developer (per task/s)– understanding the Functional, Planning functional development approach (exploratory) tests , regression , Automating coding Performing/ automation integration ,customer tests Acceptance (and with ?tests? other tests PO). Unit testing Regression execution Defining mini hardening Peering – Testing on development environment Working software
  26. 26. Unit tests pass Functional, (exploratory)User story User story Performing/ automation User story Acceptance (and with PO). Regression Defining mini hardening Team [end game testing if needed ] r a n n o t t g e i iWorking software
  27. 27. Mini hardening phase • Making sure a functional area is stable – working software • Few hours to 1-2 days - top • Taking a group of user stories (keep it small and simple) • Stop • Perform related regression • Perform short exploratory • Automation regression reduce the need of mini hardenings.
  28. 28. Workingsoftware Working software US US US US US US Perform Perform exploratory exploratory , related , related regression regression Sprint
  29. 29. Functional Automated Test TypesUnit Test Every piece of code Continuous on every peace of codeAcceptance tests Business related Every user story , and on every BuildIntegration Test Continuous Integrated system| Daily (Server, DB etc). execute automation regression , End to end flow for each functional unit.End 2 End Integrated system against live Nightly / Weekly/Build product
  30. 30. Type MeasurementsSanity Integration After each build creation , to have 100% passed sanity End 2 End scenariosRegression Integration End 2 End Measure Success rate. ManualProgression Acceptance Integration End 2 End Measure Success rate. ManualLoad Integrated system List of end to end flows and covered scenariosStress Integrated system results

×