Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题：getting to done by testing at the same time as coding（李平 王珂）

Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题：getting to done by testing at the same time as coding（李平 王珂）

• 1.
  Getting to doneby testing at the same time as coding 李平 王珂
• 2.
  GAIN GLOBAL VISIBILITY OF FOSTER CASH & RISK CONNECTIVITY UNLOCK HIDDEN CASH DRIVE EFFICIENCIES & PRODUCTIVITY AVANTGARD GETTING TO DONE BY TESTING AT THE SAME TIME AS CODING 李平(Jessica)；王珂(James) Manager of Product Development (Scrum Master) SunGard
• 3.
  BACKGROUND Team & Projects SunGard Treasury Product Team
• 4.
  CHALLENGES Not delivering onschedule  Testing not finished  Testers 1 or 2 sprints behind devs  Low automation coverage  Regression not being run regularly
• 5.
  DEFINITION OF DONE What’sDONE? Done means released.
• 6.
  DEFINITION OF DONE Finishcomplete story What do you think from different perspective?
• 7.
  CHANGES THE WAYPEOPLE WORK Changing from working as individuals to working as a team Developers Testers Team
• 8.
  WORK AS ATEAM Proper story size Work with PO to break down stories into proper size.
• 9.
  TEST AUTOMATION Writing testsbefore a screen exists • Automate as much as possible. • Test tool to choose • What to do beforehand
• 10.
  TEST AUTOMATION SCREEN DESIGN
• 11.
  TEST AUTOMATION-EXAMPLE Example: ObjectID
• 12.
  AUTOMATION TESTING Automate allthe stories One Example, pervious our testing is like this …
• 13.
  AUTOMATION TESTING Automation scriptstrategy One Example, currently our testing is like this …
• 14.
  UT/IT Find issue ASAP What to test? How it should work? When to finish?
• 15.
  UNIT TESTING PROCESS/EXAMPLE Once failed, take action immediately Example:
• 16.
  RESULT Deliver functionality ona regular schedule Percentage Stories Done 120% 100% 80% Example: 60% 40% 20% 0% Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
• 17.
  RESULT-DONE ORDER Improved doneorder based on story prority Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Example:
• 18.
  CONTINUOUS INTEGRATION Continuous DeliveryProcess Every code change leads to a potential release. It’s a continual process.
• 19.
  CONTINUOUS INTEGRATION Use ofVMs for testing environments • Team daily build/testing • Regression Testing • IT/UT
• 20.
  WORKING AS ATEAM Process to ensure all work fine • Don’t comment out failing tests! • You broke it you fix it!
• 21.
  CONTINUOUS IMPROVEMENT More practices Continuous Improvement.