Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

User story testing activities 3

1,056 views

Published on

Published in: Business, Technology, Education
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1url.pw/zzIke ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

User story testing activities 3

  1. 1. Shirly Ronen-Harel Sep 2010
  2. 2. Product Release User story Task Planning : Product –> Release -> Iteration –> User stories - > Tasks testing User story User story Task Task Task Task Task Task Task Task Detailed planningHigh level planning
  3. 3. Product Release User story Task High level planning : Sprint 0 Approach Scope Functional tractability to tests Planning /performing : Acceptance test Functional tests Regression Mini hardening!? i n t e g r a t i o n Unit tests Peering [Development environment tests] Planning : Product –> release -> iteration –> user stories - > Tasks testing
  4. 4. Goal : Find defects
  5. 5. Goal : Find defects
  6. 6. Preventing !Defects
  7. 7. User story
  8. 8. User story Task Task
  9. 9. User story Task Task Test early!
  10. 10. User story Task Task Working software Test early!
  11. 11. User story Task Task Working software Test early! Acceptance criteria
  12. 12. User story Task ATDD Task Working software Test early! Acceptance criteria
  13. 13. User story Task ATDD Task Working software Test early! Acceptance criteria
  14. 14. User story Task Task Working software Test early! Acceptance criteria Team ATDD
  15. 15. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Task Working software Test early! Acceptance criteria
  16. 16. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Task Automating tests Working software Test early! Acceptance criteria
  17. 17. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task Automating tests Working software Test early! Acceptance criteria
  18. 18. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task Coding (with tdd) Automating tests Working software Test early! Acceptance criteria
  19. 19. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Automating tests Working software Test early! Acceptance criteria
  20. 20. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment (automation or manual) Automating tests Working software Test early! Acceptance criteria
  21. 21. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment Automating tests Working software Test early! Acceptance criteria
  22. 22. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment Automating tests Unit tests pass Working software Test early! Acceptance criteria
  23. 23. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment Functional, (exploratory) Performing/ automation Acceptance (and with PO). Regression Defining mini hardening Automating tests Unit tests pass Working software Test early! Acceptance criteria
  24. 24. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment Functional, (exploratory) Performing/ automation Acceptance (and with PO). Regression Defining mini hardening Automating tests Unit tests pass Working software Test early! Acceptance criteria
  25. 25. User story Task ATDD Planning functional tests , regression , integration ,customer ?tests? other tests Testers are Peering with developer (per task/s)– understanding the development approach Task coding Unit testing execution Peering – Testing on development environment Functional, (exploratory) Performing/ automation Acceptance (and with PO). Regression Defining mini hardening Automating tests Unit tests pass Working software Test early! Acceptance criteria
  26. 26. User story i n t e g r a t i o n Functional, (exploratory) Performing/ automation Acceptance (and with PO). Regression Defining mini hardening [end game testing if needed ] Unit tests pass Working software User story User story Team
  27. 27. » 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. US Working software US US Perform exploratory , related regression US Working software US US Perform exploratory , related regression Sprint
  29. 29. Unit Test Every piece of code Continuous on every peace of code Acceptance tests Business related Every user story , and on every Build Integration Test Continuous Integrated system| (Server, DB etc). execute automation regression , End to end flow for each functional unit. Daily End 2 End Integrated system against live product Nightly / Weekly/Build
  30. 30. Type Measurements Sanity Integration After each build creation , to have 100% passed sanity scenarios End 2 End Regression Integration Measure Success rate. End 2 End Manual Progression Acceptance Measure Success rate. Integration End 2 End Manual Load Integrated system List of end to end flows and covered scenarios results Stress Integrated system

×