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.

Agile Qa Framework Jacky Wu

6,770 views

Published on

Brief how to run QA in Agile development process

Published in: Technology, Education
  • There is a useful site for you that will help you to write a perfect and valuable essay and so on. Check out, please ⇒ www.WritePaper.info ⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating direct: ❶❶❶ http://bit.ly/2Q98JRS ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Sex in your area is here: ❶❶❶ http://bit.ly/2Q98JRS ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile Qa Framework Jacky Wu

  1. 1. Agile QA Framework<br />Jacky Wu<br />jackywxd@gmail.com<br />
  2. 2. Agile Manifesto<br />We Value the items on the left more !<br />
  3. 3. Agenda<br />Goal of QA Framework<br />Roles and Role Interchangeability in Scrum<br />Key success factor: Whole Team Approach<br />QA Framework and Execution Guideline<br />Infrastructure<br />Process<br />Automation in Agile<br />Whole team and Incremental Approach Automation<br />Defects Derivative Model<br />BPT Automation Framework<br />What’s Next<br />Recap and Q&A<br />
  4. 4. Goal of QA Framework<br />
  5. 5. Roles in Scrum<br />DEV<br />Model system design<br />Knowledge of product internals<br />Focus on how it can work<br />QA<br />Model user behavior<br />Domain knowledge<br />Focus on how it can go wrong<br />AQA<br />Mixed both DEV/QA<br />
  6. 6. Role Interchangeability in Scrum<br />Sprint planning<br />Sprint Review<br />Design, Coding, Debug<br />Unit testing, code review<br />Test cases execution<br />Translate User Stories into Test Cases<br />Automation feasible analysis<br />Automation testing<br />
  7. 7. Whole Team Approach<br />Whole team is responsible for quality<br />Testers are not quality Police<br />
  8. 8. Agile <br />Development<br />Framework<br />QA Framework<br />QA Framework<br />
  9. 9. Execution Guideline: Balance and Adaptive <br />Process Guidance above Process Absolute<br />Prevention above detection<br />Automation above manual<br />Reusable lists above detailed test plans<br />Exploratory testing above detailed test scripts<br />The Key: Balance and Adaptive<br />
  10. 10. QA Framework: Infrastructure<br />Quality Center<br />Built-in Agile support<br />Defect <br />Defect model in QC<br />Testing bed<br />Real World<br />Performance/stress testing bed<br />
  11. 11. QA Framework: Process<br />Test plan management (Quality Center)<br />Iterations and Requirements<br />Mapping user story to test plan<br />Test data management<br />Efficient Test Data Management process benefits manual and automated testing and it directly impacts testing effectiveness<br />Obtaining/creating test data could be time consuming<br />Defect management<br />Continuous Integration<br />Data collection and reporting<br />Defect trending/Test progress/Automation coverage<br />
  12. 12. QA Process in Sprint (Sample)<br />
  13. 13. QA Framework: Automation in Agile<br />Automation is MUST in Agile<br />Purpose of Automation<br />Improve testing effectiveness and efficiency<br />Ultimate goal: Improve Quality<br />Automation v.s. Manual<br />Maximize ROI<br />Balance: what can automated, what cannot or should not<br />Whole team approach<br />Incremental approach<br />
  14. 14. Whole Team Approach Automation in Scrum<br />End User<br />Code<br />
  15. 15. Incremental Approach Automation in Sprint<br />C<br />C<br />C<br />C<br />G<br />G<br />G<br />B<br />B<br />C: Component automation<br />G: GUI automation<br />B: BPT automation<br />I: Integration<br />I<br />Development<br />Stable<br />
  16. 16. Automation Measurement<br />Define Automation Coverage<br />Code coverage = UT<br />Test case coverage<br />Unique case (with or without iteration)= Automated test cases/Total test cases<br />Run coverage= Automated test runs/Total test runs<br />Requirement coverage<br />Automation can find more bugs?<br />
  17. 17. Defects Derivative Model<br />Cost<br />Requirements<br />Wrong requirements<br />$<br />Plan<br />Correct Design<br />Correct Design<br />Wrong Design<br />$$<br />Design<br />Correct implementation<br />Correct implementation<br />Correct implementation<br />Wrong implementation<br />Correct implementation<br />Wrong implementation<br />$$$<br />Coding<br />Correct behaviors<br />Unexpected behavior<br />Limitations<br />Known bugs<br />Unknown bug<br />Testing<br />$$$$<br />
  18. 18. Business Process Testing Process<br />Separate automation script from test data and business logic<br />Less test cases, many iterations (testing data)<br />Central management: testing plan, testing data, testing result<br />QC<br />Application<br />Being Tested<br />QTP<br />Login<br />Data-Driver<br />BPT Test Cases<br />BPT<br />Backup<br />BPT<br />Testing data<br />Job Status<br />BPT<br />
  19. 19. BPT Automation Framework<br />Automation<br />Define components<br />Create Function Libraries<br />Create Object Repositories<br />Create Business Components<br />Create Business Components<br />Design user scenarios<br />SME<br />Drag Components to create test plan <br />Configure Input/Output parameters<br />Add cases to test set in Test Lab and Execute<br />
  20. 20. Recap and Q&A<br />Q&A<br />
  21. 21. Thank you!<br />
  22. 22. References<br />http://en.wikipedia.org/wiki/Test_automation<br />http://testingeducation.org/BBST/<br />http://www.ncpmi.org/userfiles/File/NCPMI_AE2010_Lawson.pdf<br />http://c-spin.net/2010/cspin201001eMids_QA_in_Agile.pdf<br />http://www.cigital.com/presentations/Agile%20Automation%20Testing.pdf<br />http://www.benchmarkqa.com/pdf/papers_automation_myths.pdf<br />http://www.methodsandtools.com/archive/archive.php?id=94<br />Case in point: Microsoft Vista<br />http://www.joelonsoftware.com/items/2007/12/03.html<br />

×