Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building processes inside Quality Control

Building processes inside Quality Control

Мы расскажем вам, как настроить QA-процессы на проекте, а также совместно разберем кейсы из вашего опыта.

Avatar for Mariya

Mariya

June 26, 2019

More Decks by Mariya

Other Decks in Technology

Transcript

  1. “A team is a group of individuals (human or non-human)

    working together to achieve their goal.” “A group of people with a full set of complementary skills required to complete a task, job, or project.” “A team is a system of human relationships.” What is a team?
  2. What does the testing process include? •Activities: requirements and design

    review, test strategy and plan preparation •Deliverables: test plan, test estimations Test Planning •Activities: test design, preparing testing environment, test cases execution (manual/automated) •Deliverables: test cases or scripts, test environment, test results Test Execution •Activities: documenting the testing results •Deliverables: bug report, test result report, metrics Test Reporting
  3. Why is the right process so important? • It’s easy

    to define expectations when you have defined processes. • Everyone in the team knows the rules. • A stable process can reduce risks and speed up work. • A defined process will help you hold people accountable and work well with others.
  4. • Test Design • Test Execution • Bug Reporting •

    Automation • Integration with 3-d party systems • Control Agenda Coffee break
  5. • What tool should be used? • How to create

    effective test cases? • How to prove that the requirements are covered by existing test cases? • How to keep test cases up to date? Test Design: Questions
  6. • Choose a common test management tool that meets the

    expectations of most of the team • Setup process of requirements analysis – Definition of Ready – Product Backlog Grooming/Refinement – Walkthrough • Define tests format (check list, test cases, matrix…) • Define template for tests (attributes) Test Design: Suggestions
  7. Test Design: Suggestions • Track Requirements Coverage – Traceability Matrix

    • Define process of tests review – Self-review (by the tester himself who has written the test cases) – Peer review (by another tester who hasn’t written those test cases) – Review by a supervisor (by the person who has great knowledge about the requirements and system under test): 3 amigos sessions, approve by Customer/PO • Define process of tests updating (between versions)
  8. • How to build effective Test Strategy? • How to

    perform test execution in effective way? • How to manage a fairly long list of supported environments/browsers? • How not miss any important test? • How to understand that main parts of application were not broken by new features or fixes? • How to understand that the implemented feature meets PO expectation? Test Execution: Questions
  9. • Define Test Strategy – Testing types – Testing methods

    – Compatibility Matrix – Support Matrix • Obtain dedicated teams for Performance/Security testing • Define strategy for Regression testing – Pre-regression – Risk-based approach – Automation Coverage Test Execution: Suggestions
  10. • Prepare QA environment – Closed to real environment –

    Independent from DEV • Define how QA knows when and what should be tested – Notifications about new build • Define Smoke Test & Sanity Check – Automate Smoke Test – Integrate Smoke Test into CI/CD Test Execution: Suggestions
  11. • Define strategy for Acceptance functionality – UAT – Demo

    • Define and measure metrics for tracking tests execution and improving Test Strategy – Status of tests execution – Bugs per areas of product – Bugs per testing types – Declined Rate – Reopened Rate – Defect containment Test Execution: Suggestions
  12. • How to create useful Bug Report? • How to

    review bugs? • How not miss any important bug in a quite big product backlog? • How to understand the overall quality of the product? Bug Reporting: Questions
  13. • Define template for bug report – Attributes – Rules

    – Matrix of severity and priority • RCA (identify whether the defect was due to “testing miss”, “development miss” or was a “requirement or designs miss”) • Traceability: test cases are mapped with actual bug reports • Collect metrics and create JIRA dashboards for them • Define process of bugs prioritization – By QA team – Bug triage and prioritization sessions with Customers Bug Reporting: Suggestions
  14. • How to prove to the client that automation is

    necessary? • What should be automated first? • How to avoid duplication of effort on both sides (automation and manual)? • How to measure effectiveness of TA? Automation: Questions
  15. • Have ROI (Return On Investment) or immediately calculate it

    • Define points for Automation from following areas: - Smoke tests - Regression tests - Test data generation/preparation - Areas which are required big effort from Manual tester, but can be easily automated - Areas which are run every time • Have traceability between manual and automated testing to avoid test effort duplication Automation: Suggestions
  16. Automation: Suggestions • Integrate Test Automation project with some report

    tools (e.g. Report Portal) • Create a dashboard which reflects TA effectiveness: - Test Cases growth (the increment of automated test cases) - Product bugs (real bugs found during TA run) - Test Automation issues statistic (Passed, Failed, Skipped; Product Bug, System Issue, To Investigate, Automation Bugs) • Have a roadmap for Automation (based on priorities)
  17. • How to prevent leaks of bugs related to integration?

    • How to perform integration testing in time? Integration with 3rd party systems: Questions
  18. Integration with 3rd party systems: Suggestions • Define dependency matrix

    or Architectural scheme which includes 3rd party systems • Be in recipients list of Change logs related to 3rd party systems • Plan test activities based on their plans • E2E test which cover integration with 3rd party systems (it would be good if they are automated)
  19. • How to control testing process and team? • How

    to improve testing process? Control: Questions
  20. • Have sub-teams and sub-leads (for big teams) • Have

    clear reporting in sub-teams (for big teams) • Have RACI matrix • Define communication plan Control: Suggestions
  21. • Define JIRA dashboard to track progress of testing •

    Define QA metrics and regularly measure them • Demo • Collect feedbacks about the current process and improve it Control: Suggestions