logo logo

Tester’s Month Story – Test Automation Myth Busters

Tester’s Month Story – Test Automation Myth Busters

For tester’s month, I wanted to make an article on common test automation myths.

Here are my top 6 myth busters ✨ Enjoy:

1️⃣ You can automate everything and anything 

Actually no, we can’t. Test automation needs a great level of planning, for example:

  • What do we want to cover?
  • Why do we want to automate it?
  • Is it possible to automate a particular feature?
  • Is there any frontend technology barrier?
Brainstorming meetings will help in identifying what we can automate. Most of the test management tools nowadays have a field to mark whether a test case is an automation candidate or not.

As most of the organizations today are following the Scrum framework, it’s always better to do this kind of meeting at least once a month to understand what’s in the plan for the future.

2️⃣ Automation requires a great level of coding experience 

 If you follow the KISS  principle & philosophy (keep it simple stupid), you know it’s better not to make it too complex. A test automation framework design is the core part of automation. The more it adapts simplicity, it will be better to maintain and incorporate existing test engineers to contribute to automation tasks.

📌 I personally recommend the TestProject platform for an easy, simple & codeless test automation to your team.

3️⃣ Testing & testing related jobs are getting redundant

That’s a big NO. In fact, the more we are going towards the rapid and systematic modularized way of application development, the demand to test the product continuously is increasing. As the integration is happening in a faster way, It requires continuous testing as well in sync with continuous development.

Other jobs related to testing have also increased if we compare them to past years. Security testing, accessibility testing & performance testing have become a specialized domain, and it has a great learning curve as well as great job opportunities 💪

4️⃣ Codeless automation requires no coding knowledge

That’s not true. The name is codeless, but that doesn’t mean all the tests can be automated without any code/script change. Logically in the background, compatible code is generated, and customization is required at different levels of complexity in test automation.

so, it’s always better to learn at least one programming knowledge to support a codeless automation process. The most loved and preferable ones are Javascript, Java, Python, or C#.

5️⃣ Make big test cases to cover more features in one shot

Test cases should be atomic. Checking one or two things will be a better idea than checking multiple things in a test, as your test report should show what exact test case failed and which functionality needs a recheck.

6️⃣ Automation kills the job for others

Also a big NO. In fact, companies/projects can take more and more tasks from the roadmap if the automation is supporting faster solutions.

Organizations can concentrate more on different types of testing than just API and UI testing once it is automated. Automation, day by day, is creating new jobs and hence creating opportunities for software professionals.

 I hope you learned something new, and I’d love to see your comments on other misconceptions & myths I may have missed 🙏

About the author

Nitesh Jain

Tester for all the seasons & reasons.

  • 12+ years in Software Industry which includes Manual Testing (5+year) and Automation (5+year)
  • Works as SDET, Test Automation Engineer at Avalara technologies Pvt Ltd, Pune, India.
  • ISTQB-Advance level Test Manager +Test Analyst +Technical Test Analyst certified.
  • Significant experience in Manual Testing, Automated Testing, Quality Assurance & Control,
  • Test Management, Release Coordination, Process Implementation & Improvement.
  • Experience in Leading Test teams for various Projects of off shore – on shore model.
  • Sound Knowledge of Testing Concept & Methodology, Defect life cycle & Defect Prevention.
  • Test Automation Framework design Using Selenium Java TestNG, Cucumber, Maven.
  • Ability to adapt to new environment quickly, strong team player, enthusiastic leader and always keen to meet project target. Excellent Technical, Analytical and Problem Solving skills and ability to get on well with people including cross-cultural backgrounds.


4 1 comment
  • John Erwin Chan October 26, 2021, 2:06 pm

    totally agree with this especially #4 and #5…for #5 some wants to cover it in one shot but I really disagree…simple is better and it makes debugging more east

Leave a Reply