Уроки, полученные при проведении автоматизированного приемочного тестирования
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Уроки, полученные при проведении автоматизированного приемочного тестирования

  • 818 views
Uploaded on

Ран Найман - доклад на SQA Days, 2-3 декабря 2011, Москва

Ран Найман - доклад на SQA Days, 2-3 декабря 2011, Москва

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
818
On Slideshare
818
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
30
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Lessons Learned from Automated Acceptance Testing Rannicon
  • 2. Rannicon
  • 3. Common to All CasesScrumPerformanceBig products 100 – 1000 people involved Rannicon
  • 4. Case 1: Browsing Gateway 2004Weekly manual build and manual testing Rannicon
  • 5. Case 1: Process Change Analysis Design Code Test Deliver Analysis Test Design Code Deliver Rannicon
  • 6. Case 1: Automation Approach Offshore subcontractor Rannicon
  • 7. Case 1: Results100% test automationIn version 2.0 we learned the new methodVersion 2.1 of product launched on schedulefirst time in products historyAutomated tests keep the product in releaseshape during the development Rannicon
  • 8. Case 1: LearningsAutomated acceptance testing deliversSell to managers to avoid double workPerformance and stability tests; EssentialDo not outsource automating test casesDo not write your own testing frameworkTeam level workshops work wellTest help troubleshoot customer problems Rannicon
  • 9. Case 2: Flexi Network GatewayGreenfield productFrom Day 1  Unit testing  Continuous Integration  Automated Acceptance Tests Rannicon
  • 10. Case 2: Automation Approach RobotFramework.org Rannicon
  • 11. Case 2: Some Statistics Rannicon
  • 12. Case 2: Results100 % test automation from day oneRelease capability after every sprintClose customer collaborationOnly running tests as test documentation Rannicon
  • 13. Case 2: LearningsAvoid making acceptance test too low levelCommercial driver lock inResistance to new tools and techniquesshould not be underestimatedAutomated tests helps distributing work  Still distribution slows down work Rannicon
  • 14. Case 3: Big UX project 2010UX centric greenfield projectNo common rules on test automationMany tries to find right UX Rannicon
  • 15. Case 3: Automation ApproachBuilding own test library to interact withapplications UITest scripts written in scripting languageCucumber integration possible but not usedSeparate TA tools, Integration and Buildorganizations Rannicon
  • 16. Complex Integration Developer / Release Team Tester Commit Integration Pre-release Build Source Build Code PrereleaseRepository Integration Build / Test Code Build / Test Built Component Built Component Pre-built Code Components Release Repository Automatic Build / Test Development Repository Pre-built Components Rannicon
  • 17. Case 3: ResultsWorkshops with specification by example payoffDaily product buildsLots of manual testingLong feedback cycles Rannicon
  • 18. Case 3: LearningsAutomates tests with scripting languagebecome unmaintainableCommon approach to test automation essentialInvestment to simple CIDo not underestimate organizationalchallengesAutomated as much as possible below UI Rannicon
  • 19. Summary of LearningsAutomated testing enables agilityAutomated testing speeds learningAutomated testing is for whole productInvest to automated CI systemBuilding automation tools is time wastedCommercial tools lock you inAutomated testing is not all you need Rannicon
  • 20. Thank You Ran Nyman email: ran@rannicon.com web: http://rannicon.com twitter: @ran_nyman Rannicon