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.

SQA Best Practices: A Practical Example

1,046 views

Published on

データをどのように作って管理しているか

Published in: Technology
  • Be the first to comment

  • Be the first to like this

SQA Best Practices: A Practical Example

  1. 1. SQA Best Practices: A Practical Example Rosana Sanchis June/30th/2020 Leisure Product Section Leisure Product Department Life & Leisure Technology Supervisory Department Rakuten, Inc.
  2. 2. My career goal Become a Specialist in Test Process Improvement Following definition of ISTQB Expert Level Improving theTesting Process To achieve this goal ImproveSoftwareTest Life Cycle Procedures Test Design Test Implementation Test Execution Reporting
  3. 3. 3 1.Testing challenges: How to test efficiently 2.Our solution: Procedures and tool Integration 3.How this works? Our Best Practices in Action Agenda
  4. 4. 4 How to test efficiently a site like this? Basically, we need: Functional Knowledge of the Product A Testing Procedure adapted to our knowledge of the Product A tool adapted to our Procedure Rakuten Beauty, 30/05, https://beauty.rakuten.co.jp/
  5. 5. 5 How to test efficiently a site like this? The product will evolve, the team will change.We need a way of preserving, sharing and modifying this knowledge Functional Knowledge of the Product A Testing Procedure adapted to our knowledge of the Product A tool adapted to our Procedure Testing Procedure need to be standardized: the process are then objective, measurable and understandable for all stakeholders The tool must allow us to follow our Procedures in the most efficient way.To achieve this, the tool must be chosen because of its suitability to the Procedure
  6. 6. 6 1.Testing challenges: How to test efficiently 2.Our solution: Procedures and tool Integration 3.How this works? Our Best Practices in Action Agenda
  7. 7. Test Design Test Implementati on Test Execution Requirements (Functional Needs) Requirement Traceability Matrix (Ensures Scope) Reporting (Output data analysis) SQA Procedures:A functional approach WHAT to test (Defines Scope) PDM Functional Specs Test Cases (input=> condition=> output) Project Start Project End HOW to test (Defines Test Conditions) Compares Actual VS Expected Results Final Report First Input Last Output
  8. 8. 8 Our tool was chosen because it allowed us to create a Master Data (library of our Functional Knowledge) and to reuse it efficiently Functional Specifications (provided by PDM) Requirements Test Manager identifies the Functional Needs in the Specifications Test Plan Test Design Test Implementation Requirements are already mapped to Scenarios andTest Cases in PractiTest so once we identify Requirements, SQA testware is ready to share
  9. 9. 9 1.Testing challenges: How to test efficiently 2.Our solution: Procedures and tool Integration 3.How this works? Our Best Practices in Action Agenda
  10. 10. 10 How to test efficiently a site like this? The product will evolve, the team will change.We need a way of preserving, sharing and modifying this knowledge Functional Knowledge of the Product A Testing Procedure adapted to our knowledge of the Product A tool adapted to our Procedure Testing Procedure need to be standardized: the process are then objective, measurable and understandable for all stakeholders The tool must allow us to follow our Procedures in the most efficient way.To achieve this, the tool must be chosen because of its suitability to the Procedure
  11. 11. 11 Sharing and modifying this knowledge STEP 1: CHECK SPECIFICATIONS STEP 2: IDENTIFY REQUIREMENTS FUNCTIONAL SPECIFICATIONS PROJECT: HAIR STYLE RANKING ON RAKUTEN BEAUTY IMPACT ANALYSIS: PLEASE CHECK FAVORITES AND EXECUTE SOME OPERATIVE SYSTEM REGRESSION REQUIREMENTS FAVORITES FUNCTIONALITY OPERATIVE SYSTEM SANITY CHECK
  12. 12. 12 On the tool: FAVORITES contains Scenarios: Add, Check and Delete Operative System contains: Android and iOS Sharing and modifying this knowledge
  13. 13. 13 How to test efficiently a site like this? The product will evolve, the team will change.We need a way of preserving, sharing and modifying this knowledge Functional Knowledge of the Product A Testing Procedure adapted to our knowledge of the Product A tool adapted to our Procedure Testing Procedure need to be standardized: the process are then objective, measurable and understandable for all stakeholders The tool must allow us to follow our Procedures in the most efficient way.To achieve this, the tool must be chosen because of its suitability to the Procedure
  14. 14. 14 objective, measurable and understandable STEP 4: CREATE REQUIREMENTS TRACEABILITY MATRIX TEST SCENARIOS REQ1 SCE 1 REQ2 SCE 2 REQ3 STEP 5 : CHECK IF REQUIREMENTSARE COVERED BY SCENARIOS TEST SCENARIOS REQ1 SCE 1 REQ2 SCE 2 REQ3 ? TEST SCENARIOS REQ1 SCE 1 REQ2 SCE 2 REQ3 SCE 3 STEP 6 : ADD REQUIREMENTOR SCENARIO IF NEEDED
  15. 15. 15 Issues found on last execution Scenarios of the Requirement TestCases Last Execution status objective, measurable and understandable
  16. 16. 16 How to test efficiently a site like this? The product will evolve, the team will change.We need a way of preserving, sharing and modifying this knowledge Functional Knowledge of the Product A Testing Procedure adapted to our knowledge of the Product A tool adapted to our Procedure Testing Procedure need to be standardized: the process are then objective, measurable and understandable for all stakeholders The tool must allow us to follow our Procedures in the most efficient way.To achieve this, the tool must be chosen because of its suitability to the Procedure
  17. 17. 17 most efficient way REQUIREMENTS FAVORITES FUNCTIONALITY OPERATIVE SYSTEM SANITY CHECK STEP 5 : CHECK IF REQUIREMENTSARECOVERED BY SCENARIOS REQUIREMENTS FAVORITES FUNCTIONALITY SCENARIOS: ADD, DELETE AND CHECK OPERATIVE SYSTEM SANITY CHECK SCENARIOS: ANDROID AND IOS X X STEP 6 : ADD REQUIREMENTOR SCENARIO IF NEEDED FORTHIS EXAMPLE, NOTHINGTOADD
  18. 18. 18 most efficient way STEP 7: CREATE TESTSETUSING REQUIREMENT TESTCASES TEST SET REQ1 TEST 1.1 TEST 1.2 TEST 1.3 REQ2 TEST 2.1 TEST 2.2 REQ3 TEST 3.1 STEP 8 : REUSE TESTCASES IF POSSIBLE STEP 9: ADD TESTCASES IF NEEDED TEST SET REQ1 TEST 1.1 TEST 1.2 TEST 1.3 REQ2 TEST 2.1 TEST 2.2 REQ3 TEST 3.1 TEST 1.2 TEST SET REQ1 TEST 1.1 TEST 1.2 TEST 1.3 REQ2 TEST 2.1 TEST 2.2 REQ3 TEST 3.1 TEST 1.2 TEST 3.3
  19. 19. 19 TEST IMPLEMENTATION EXAMPLE New Project Requirement TestCases Of the Requirement STEP 7: CREATE TESTSETUSING REQUIREMENTTESTCASES
  20. 20. 20 TEST IMPLEMENTATION EXAMPLE STEP 8 : REUSE TESTCASES IF POSSIBLE AndroidScenario has no test cases But iOS hasTESTCases we can reuse
  21. 21. 21 TEST IMPLEMENTATION EXAMPLE STEP 8 : REUSE TESTCASES IF POSSIBLE So we can clone iOS test cases NowAndroid is also covered
  22. 22. 22 TEST IMPLEMENTATION EXAMPLE STEP 9: ADD TESTCASES IF NEEDED For this example we don’t need to add any test case to the test set So this project is ready for execution!
  23. 23. 23 Anyone at anytime can manage a QA project, even without functional knowledge ATool that generates RTM and allows Masterdata storage Creation of reusable Testware Easy to understand Procedures and Outputs Conclusion: With QA Best Practices in action, SQA becomes more efficient

×