Automation testing could be a technique uses an application to implement entire life cycle of the software system in less time and provides potency and effectiveness to the testing software system.


When a software system has new unharness it have bug fix, but however can you guarantee or make sure that there’s no a lot of bugs owing to the fixes. So it’s necessary to check with recent practicality.

What to Automate? 

Repetitive / Important – check cases those are repetitive unchanging. Check if the action goes to be tested all the time / most of the time? – This additionally offers a sign of the importance of the action. Don’t change a check if you’re solely getting to run it once and dump it. Whereas you choose to change a check, take a step back and suppose however usually you’re possible to execute this test? Is it very definitely worth the effort to change the test?

  • Stability – Check if the practicalityto be machine-controlled is stable. If the module of the applying isn’t stable enough, the trouble in automation is wasted to AN
  • Simplicity & Relevancy – In severalcases your ROI are going to be higher by implementing tons easy of straight forward of easy tests instead of few sophisticated tests therefore begin by doing a gaggle of connected simple tests and their connected Opt for a gaggle that has a lot of in common with others. It additionally includes situations that take tons of effort and time once performing arts manual testing however ar fast to change and execute.
  • Regression tests – usuallythese are the perfect candidates for automation and out there once the practicality has ‘matured’ a secure level of confidence within the For such candidates, automation is less complicated to develop & tests are a lot of reliable (false failures are less probable).
  • Deterministic – situations that may yield pass/fail while not false results, or – situations that have normal results wherever you recognize that X input might solely lead to Y output. opt for the check cases with extremely sure conditions and results give an honest live of confidence in stability and quality
  • Data driven scenarios
  • wherever same perform must be valid with millions of totally different completely different completely different} knowledge appreciate victimisation different user accounts or victimisation different privileges and roles (e.g. login)
  • Complexity – Tests that tend to cause human error, for e.g. a TC that has advancedsteps or calculations.
    High Risk – oftentimes used practicality that introduces high risk conditions.
  • Manual Execution Not Possible – situationsthat are not possible to perform appreciate load testing situations
    Heterogeneous Configuration – Tests that run on many totally different hardware or software system platforms and configurations.
  • Risk based mostly Approach – Use risk based approach. To forman automatic script, it needs time and energy, and if aim for “Automating each Test”, we are going to need heap of resource and time, that in several cases isn’t doable. Instead use a Risk primarily based approach to see that tests ought to be machine-controlled. To urge the foremost price out of automation, solely change the foremost necessary business cases and situations.

What to not Automate?

Test cases that has to be valid subjectively by humans appreciate Usability.

Complex practicality wherever check automation is also a significant challenge in terms of your time

Don’t change check cases whose actions are distributed across multiple (third party) systems wherever validation is troublesome to attain whereas manual execution is quicker and reliable to perform.

Check if state of affairs needs human to observe and observe once the check is being run? Is human intervention necessary or optional? If it needs human intervention then it’s not a perfect candidate.

It is higher to not change verification of presence/state/location/etc. of controls and static text.

Look & Feel situations – It’s terribly long and unreliable to do and “digitize” look-and-feel for verification. Scripts might check existing controls and text however what if one thing new seems looking on knowledge condition? You can’t code for one thing you don’t realize nevertheless.

Another note in grips in mind is that not all tests will be machine-controlled. Some tests are terribly advanced in nature and need several downstream system checking and might be inconsistent. In these cases, it’s best to depart these checks for manual testing.


Leave a Reply

Your email address will not be published. Required fields are marked *