АЛЛА ПЕНАЛЬБА «QA automation, the secret weapon that need (a) manual»
0 likes39 views
Online QADay 2024 #2 АЛЛА ПЕНАЛЬБА «QA automation, the secret weapon that need (a) manual» https://linktr.ee/qadayua
![[Webinar] Test First, Fail Fast - Simplifying the Tester's Transition to DevOps](https://cdn.slidesharecdn.com/ss_thumbnails/testfirstfailfastfinal-170323164615-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
Similar to АЛЛА ПЕНАЛЬБА «QA automation, the secret weapon that need (a) manual» (20)
More from QADay (20)
Ad
Recently uploaded (20)
Ad
АЛЛА ПЕНАЛЬБА «QA automation, the secret weapon that need (a) manual»
- 1. QA automation, the secret weapon that need (a) manual Alla Penalba, Sr Manager, QA Engineering
- 2. Who am I ? ★ 15+ years in Quality Assurance in product companies ★ 9 years in QA Management including manual and automated testing ★ Mentor & trainer on QA courses for 3 years in total ★ Currently - Sr Manager, QA Engineering for Retail product in DraftKings ★ Favourite words: efficiency, optimization, flexibility :)
- 3. What your boss is asking ➔ How much faster can we release ? ➔ How much money are we saving ? ➔ Can we fire all manual QAs now that we have automation?
- 4. An automation story ➔ 500 test cases automated ➔ “Run” once a week (crash twice a week) ➔ Unclear coverage ➔ Slower to run than to test by hand
- 5. Key Reasons for Failure Reason: unclear strategy & misalignment in expectations ➔ Why do we want to automate? ➔ What do we want to achieve? ➔ How do we measure success?
- 6. Key Reasons for Failure Reason: inconsistent test maintenance & stability of automation ➔ How to support constantly changing product functionality? ➔ Ensure automation stability
- 7. Key Reasons for Failure Reason: separation of manual and automated testing ➔ The Automation bubble ➔ Manual QA Engineers not using Automation in their daily routine
- 9. How not to fail? Step 1: Define clear goal and success measure For example, ➔ we would like to cover by automation all Sanity verification as well as main flows for all features product has and by this decrease time we spent on Regression/HFs verification by X% ➔ we would like to cover by API tests all our microservices and API and decrease time required for compatibility/new version/production verification by X%
- 10. How not to fail? Step 2: Evaluate team skills and readiness ➔ Do we have people with enough technical capabilities? Step 3: Tool selection ➔ Ensure tools align with your tech stack and business needs ➔ Evaluate tool integration with existing CI/CD pipelines
- 11. How not to fail? Step 4: Review your Test coverage and define roadmap for Automation ➔ Check that your manual test cases are ready to be automated: ◆ up to date ◆ modular ◆ have good detalization of verification points ◆ easy to maintain ➔ Define the roadmap for automation ◆ critical flows ◆ repetitive verifications ◆ high-risks test
- 12. How not to fail? Step 5: Define approach for tests maintenance and scalability ➔ Think about how automated tests will support changes in the product ➔ Plan the process on how to ensure 1-1 match between manual and automated tests ➔ Ensure availability of resources dedicated to keeping AT tests up-to-date and stable
- 13. How not to fail? Step 6: Build collaboration with all involved teams ➔ Facilitate strong collaboration between developers, manual QAs, DevOps and Automation team ➔ Make sure everyone is aligned on automation goals and progress “Communication is a key to success”
- 14. How to evaluate ROI? What does ROI means for your project? ➔ Time savings ➔ Cost reduction ➔ Higher quality release
- 16. How automation helped to my project ★ Regression duration cut by 50% ★ # of Bugs reported on the early stage (during the development) based on automation runs increased by 20% ★ Significant decrease in production deployment verification ★ Post-RnD verification has been decreased by 75%
- 17. Q&A 😊