• Save
Shirly Ronen - User story testing activities
Upcoming SlideShare
Loading in...5
×
 

Shirly Ronen - User story testing activities

on

  • 34,021 views

 

Statistics

Views

Total Views
34,021
Views on SlideShare
5,182
Embed Views
28,839

Actions

Likes
1
Downloads
0
Comments
0

12 Embeds 28,839

http://www.agilesparks.com 28699
http://agilesparks.com 116
http://ubuntu.samity.org 7
http://www.agilesparks.co.il 5
url_unknown 4
http://translate.googleusercontent.com 2
http://agilesparks.co.il 1
http://131.253.14.250 1
https://twitter.com 1
http://131.253.14.66 1
http://agilesparks.in 1
https://translate.googleusercontent.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Shirly Ronen - User story testing activities Shirly Ronen - User story testing activities Presentation Transcript

  • User story as working software : testing activities Shirly Ronen-Harel Sep 2010
  • 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
  • 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
  • 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 software
  • Test early! Task Task User storyAcceptancecriteria Working software
  • Test early!Acceptance Taskcriteria Task User story ATDD Working software
  • Test early!Acceptance Taskcriteria Task ATDD User story Working software
  • Test early!Acceptance Taskcriteria Task ATDD User story Team Working software
  • Test early!Acceptance Taskcriteria Task ATDD User storyPlanning functional tests ,regression , integration,customer ?tests? other tests Working software
  • Test early!Acceptance Taskcriteria Task ATDD User story Planning functional tests , regression , integration ,customer ?tests? other tests Automating tests Working software
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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.
  • Workingsoftware Working software US US US US US US Perform Perform exploratory exploratory , related , related regression regression Sprint
  • 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
  • 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