A Practical Guide for QA Engineers - What Tests Should Be Automated
QA Automation Engineers and SDETs constantly face requests to automate various tests. Deciding which tests to automate is a core daily task, and being able to prioritize the right tests helps to deliver quick results to other teams and demonstrates sound decision making.
๐—–๐—ฟ๐—ถ๐˜๐—ฒ๐—ฟ๐—ถ๐—ฎ ๐—ณ๐—ผ๐—ฟ ๐—–๐—ต๐—ผ๐—ผ๐˜€๐—ถ๐—ป๐—ด ๐—ง๐—ฒ๐˜€๐˜๐˜€ ๐˜๐—ผ ๐—”๐˜‚๐˜๐—ผ๐—บ๐—ฎ๐˜๐—ฒ
๐Ÿ” ๐—ฅ๐—ฒ๐—ฝ๐—ฒ๐—ฎ๐˜๐—ฎ๐—ฏ๐—ถ๐—น๐—ถ๐˜๐˜†
Tests that run frequently, like regression and sanity tests, are ideal automation candidates. Daily smoke tests that check basic functionality should be automated to provide quick feedback on application stability.
๐Ÿ”ฅ ๐—›๐—ถ๐—ด๐—ต ๐—ฅ๐—ถ๐˜€๐—ธ ๐—”๐—ฟ๐—ฒ๐—ฎ๐˜€
Critical functionalities like authentication, security, data integrity, and financial transactions should be automated. These features must work flawlessly under all circumstances.
๐Ÿ”’ ๐—ฆ๐˜๐—ฎ๐—ฏ๐—น๐—ฒ ๐—™๐—ฒ๐—ฎ๐˜๐˜‚๐—ฟ๐—ฒ๐˜€
Features that rarely change require minimal test maintenance, making them valuable long term automation investments. Main user scenarios that have remained stable across several releases are perfect candidates.
โฐ ๐—ง๐—ถ๐—บ๐—ฒ ๐—–๐—ผ๐—ป๐˜€๐˜‚๐—บ๐—ถ๐—ป๐—ด ๐—ง๐—ฎ๐˜€๐—ธ๐˜€
Multi step tests or large test suites with hundreds of cases consume significant manual effort. Scenarios requiring repeated user interactions (like multiple login/logout cycles) are tedious and error prone when done manually but execute in seconds when automated.
๐Ÿ’ ๐—Ÿ๐—ผ๐˜„ ๐—›๐—ฎ๐—ป๐—ด๐—ถ๐—ป๐—ด ๐—™๐—ฟ๐˜‚๐—ถ๐˜
Tests that can be automated easily and quickly offer immediate returns. Basic login/logout functionality can be automated fast and shows immediate value by reducing manual testing time.
๐Ÿ“Š ๐——๐—ฎ๐˜๐—ฎ ๐——๐—ฟ๐—ถ๐˜ƒ๐—ฒ๐—ป ๐—ง๐—ฒ๐˜€๐˜๐—ถ๐—ป๐—ด
Tests involving multiple datasets or input combinations benefit significantly from automation. Form validation with various input combinations ensures all edge cases are handled efficiently.
๐—ง๐—ต๐—ฒ ๐—–๐—ผ๐˜€๐˜ ๐—•๐—ฒ๐—ป๐—ฒ๐—ณ๐—ถ๐˜ ๐—”๐—ป๐—ฎ๐—น๐˜†๐˜€๐—ถ๐˜€
Balance the effort required to automate against the time it will save. Prioritize automation where long term benefits justify the initial investment.
Automating complex but frequently executed tests saves significant time. However, a manual test that takes 10 minutes and runs once a month isn't worth 40 hours of automation effort.
๐.๐’. ๐Ÿšฉ ๐ˆ๐Ÿ ๐ฒ๐จ๐ฎ ๐ก๐š๐ฏ๐ž๐งโ€™๐ญ ๐ฐ๐š๐ญ๐œ๐ก๐ž๐ ๐ข๐ญ ๐ฒ๐ž๐ญ, ๐ฒ๐จ๐ฎ๐ซ ๐ง๐ž๐ฑ๐ญ ๐ฌ๐ญ๐ž๐ฉ ๐ข๐ฌ ๐ญ๐ก๐ž ๐…๐‘๐„๐„ ๐Ÿ‘-๐ฉ๐š๐ซ๐ญ โ€œ๐Œ๐š๐ง๐ฎ๐š๐ฅ ๐๐€ โ†’ ๐’๐ƒ๐„๐“โ€ ๐ฐ๐จ๐ซ๐ค๐ฌ๐ก๐จ๐ฉ,ย ๐š ๐ฌ๐ก๐จ๐ซ๐ญ ๐ฆ๐ข๐ง๐ข-๐œ๐จ๐ฎ๐ซ๐ฌ๐ž ๐ญ๐ก๐š๐ญ ๐ ๐ข๐ฏ๐ž๐ฌ ๐ฒ๐จ๐ฎ ๐ญ๐ก๐ž ๐Ÿ๐ฎ๐ฅ๐ฅ ๐ซ๐จ๐š๐๐ฆ๐š๐ฉ ๐ญ๐จ ๐›๐ž๐œ๐จ๐ฆ๐ข๐ง๐  ๐š ๐ฆ๐ข๐-๐ฅ๐ž๐ฏ๐ž๐ฅ ๐’๐ƒ๐„๐“ ๐š๐ง๐ ๐ฉ๐š๐ฌ๐ฌ๐ข๐ง๐  ๐ข๐ง๐ญ๐ž๐ซ๐ฏ๐ข๐ž๐ฐ๐ฌ.
5
0 comments
Matviy Cherniavski
6
A Practical Guide for QA Engineers - What Tests Should Be Automated
QA Automation Accelerator
skool.com/qa-automation-career-hub
Become a job-ready QA Automation Engineer/SDET in 3โ€“4 months. AI-powered prep, real SaaS project, Certificate of Completion, and live support. ๐Ÿš€
Powered by