Your SlideShare is downloading. ×
AutomatedQA
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

AutomatedQA

243
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
243
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
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. 1
  • 2. The presenters today are:  Steve Miller – 25 years of experience with software development / testing and Software Planner expert.  Gregg Sporar – 25 years of experience with software development / code reviews and Code Collaborator expert. 2
  • 3.  Stick around at the end of the webinar -- we will provide a link for you to fill out a survey. If you fill that out, you will be entered into a drawing for a FREE Flip Video Camcorder – to be mailed on Friday March 26. 3
  • 4.  We will be recording the session and will distribute the recorded session via email  Feel free to ask any questions using the Q&A panel 4
  • 5. 8 Best Practices 1. Identify the major causes of Project Slippage 2. Create great requirements 3. Create better estimates 4. Implement Requirements / Test Case Traceability 5. Implement Testing Best Practices 6. Reduce defects using Peer Code Reviews 7. Implement best practices for managing defects 8. Drive lifecycle management from key metrics 5
  • 6. Keys to Success:  Process Improvement  Intelligent Use of Tools Tools we will show Today:  Software Planner – for Application Lifecycle Management  Code Collaborator – for Peer Code Review  TestComplete – for test automation  Jing – for recording screen actions for defect management 6
  • 7.  For today’s webinar, we will use an Orders Application for our examples.  This sample application is used to illustrate how to manage software releases. Hands On – Review the Orders Application and how this project was set up in Software Planner 7
  • 8. 8
  • 9. Best Practice 1 Before we can improve releases, we must understand what causes slippages. Major contributors are:  Poorly defined requirements resulting in poor estimates  Too many defects discovered during the QA phase  Lack of best practice techniques for managing all phases of the software lifecycle 9
  • 10. Best Practice 2 A great requirement has these elements:  Succinct yet descriptive narrative  Explicit list of business rules  Prototype 10
  • 11. Requirement: OA-0002 Add New Order Description: Allow adding of a customer order. Orders can come from many places. They can come from downloads from the website, Google searches, trade shows, etc. Regardless of how the order comes in, process it the same way. Invalid orders should not be processed. Business Rules: Allow entry of these fields: Customer Name, Product, Quantity, Price Per Unit, Discount, Total, Date, Address, Credit Card Info. 11
  • 12. Hands On – Review the revised (good) requirement in Software Planner  Succinct yet descriptive narrative  Explicit list of business rules  Prototype 12
  • 13. 13
  • 14. 14
  • 15. Best Practice 3 To define better estimates, you must:  Start with a good requirement  Decompose the requirement into tasks  Build in buffers based on past experiences  Identify tasks for testing, documentation, and other tasks that are often forgotten 15
  • 16. Hands On – View how we decomposed the requirement into tasks using Software Planner – providing a much better estimate 16
  • 17. 17
  • 18. Best Practice 4 A few simple best practices will dramatically increase quality:  Create test cases directly from the requirement (linking them) to ensure good traceability and test coverage  Create both positive and negative test cases  Automate as many of the regression tests as possible – this allows you to run them more often and without tying up testing resources 18
  • 19. 19
  • 20. Hands On – View how we used Software Planner to create positive and negative test cases for the Order Entry requirement (OA- 0002) and how we used Traceability to ensure we had good test coverage 20
  • 21. Best Practice 5  Want the best kept secret in regards to improving the quality of code received for QA testing? Publish your test cases to the developers early during their coding process!  Automate your Regression Test Cases  Implement Testing Best Practices: http://www.softwareplanner.com/TestBestPractices.pdf 21
  • 22. Hands On – View the Testing Best Practice Document. Illustrate how to automate test cases using TestComplete. 22
  • 23. 23
  • 24. The Earlier You Find the Bug, The Easier and Less Expensive It Is to Fix 24
  • 25. Before Code Review 500 Bugs Remaining What if we had Peer Review? 463 Bugs Remaining in the Application 400 Bugs Remaining 321 300 Bugs Remaining 194 200 ? 100 ? ? 0 After After After Development QA/Test Customer ($200/fix) ($1000/fix) Cost of fixing bugs: $174k + Cost of 194 latent bugs: $194k Total Cost: $368k 25
  • 26. After Code Review Bugs Remaining 500 Bugs Remaining in the Application 463 400 300 Bugs Remaining 200 180 32, Bugs Remaining 100 113 down Bugs Remaining 32 from 194 0 After After After After Development Code Review QA/Test Customer ($25/fix) ($200/fix) ($1000/fix) Cost of fixing bugs: $120k + Cost of 32 latent bugs: $ 32k Total Cost: $152k $152k, down from $368k 26
  • 27. 27
  • 28. To See More, Sign Up for a Code Collaborator Webinar: http://smartbear.com/webinar-schedule.php 28
  • 29. The key is to reduce rework of defects  Ensure defects can be reproduced - Use Jing (www.jingproject.com) to record your screen actions  Automatically create defects from failed test cases  Use threaded discussions on the defect to discuss what has been fixed  Keep track of defect rework analytics 29
  • 30. 30
  • 31. 31
  • 32. 32
  • 33. 33
  • 34. 34
  • 35. 35
  • 36. 1. Identified the major causes of Project Slippage 2. Demonstrated how to create great requirements 3. Identified how to create better estimates 4. Explained Requirements / Test Case Traceability 5. Discussed Other Testing Best Practices 6. Discussed reducing defects using Peer Code Reviews 7. Discussed best practices for managing defects 8. Illustrated important metrics for managing lifecycle 36
  • 37.  We will send out the recorded session later this week.  Please fill out the survey (Free Flip Camcorder Drawing) http://www.SoftwarePlanner.com/Survey23  Sign up for a free trial of Software Planner at http://www.SoftwarePlanner.com  Sign up for a free trial of Code Collaborator at http://www.CodeCollaborator.com  Sign up for a free trial of TestComplete at http://www.TestComplete.com  Questions? 37
  • 38. Thanks again for your time today! Contact Information (Request Personalized Demos or ask questions) +1 (978) 236-7900 sales@automatedqa.com 38