Geeks logo

Test Automation and Continuous Testing Competition Week. Part 2: Assessment

A Practical and Fun Way to Create a Successful Test Automation and Continuous Testing Formula in Your Company

By Zhimin ZhanPublished 2 years ago Updated 2 years ago 3 min read

Continue from Part 1.

6. Judge objectively and solely based on the results.

The judgment criteria:

  • Completion of the target test suite.
  • Correctness.
  • Execution speed.
  • Detection rate for the known effects
  • Execution reliability in CI/CT server. The overall pass/fail rate is not a good criterion. A better way is to check whether a green build can be obtained (pass all tests) at the end of the day.
  • The quality of test scripts. A simple way to judge is to check whether the business analyst or manual tester understands the test scripts.
  • The finishing time. On the comparable results, the team that finishes the test suite earlier wins.

Reward the winner!

The company surely needs to put into some investments for this competition. The cost, relative to the company’s gains or the money it would save, is minor.

Two outcomes resulted from the competition are:

1. A successful formula for test automation and CT have been found

A big win for the company is that the success will boost the confidence and grow the capability on this ‘proven’ track. I can share some experiences from the companies that do not have these open exercises.

  • The tech leads and test manager decided on Cypress but found Cypress did not support iFrame a week later. (Cypress and some other JS-based automation frameworks have limitations, check out this article: Why Cypress Sucks for Real Test Automation? Part 2: Limitations)
  • Cucumber was sold by ‘fake agile coaches’ to be used in testing. An agile coach boasted that he had done over 200 Cucumber end-to-end tests in several of his past projects. In reality, this test automation team (with the involvement of this ‘agile coach’) has never been able to deliver a successful test report over 12 Cucumber tests. The team was struggling with maintenance from Week 2 and onwards until these tests were aborted.

As we all know, after a decision was made, the management who made this decision (no matter right or wrong) often chose to defend it. That’s why so many companies tend to renew the licenses of testing tools though the companies do not actually use for real work.

Besides, the company gets a regression suite of 25 automated tests which are useful now.

2. No single team delivered satisfactory results

This is probably the likely outcome for most software companies.

Though it means the company does not have the capability, still a valuable finding for the company.

Then review and act based on the feedback:

  • identify what approaches definitely won’t work, such as record-n-playback and the use of Gherkin syntax.
  • identify the limitations of certain technologies, such as Cypress does not support two browser windows/tabs, …, etc.
  • prevent many unnecessary (and costly) attempts from individual teams.
  • improved awareness of infrastructure support for real Continuous Testing.
  • improved awareness of test automation beyond QA. For example, Business analysts may want to run automated tests but are uncomfortable with the complexity of the tools.
  • improved respect for CT engineers’ hard work
  • help some engineers to give up fixation on the wrong framework/tools. Meetings won’t help, I tried. Once, most of the team members acknowledged I was a better Java programmer, but I couldn’t convince them to use Ruby to write automated tests after numerous discussions.

If necessary, the company might do another competition event in a month's time. If it is still no luck, engage a real test automation and CT coach to help. Now the executive’s decision to seek external help from a real test automation coach might face much less obstruction.

Of course, the company can use the same competition process (with a shorter timeframe) to test whether a test automation coach candidate is fake or not.

---

        Relative readings:

      • AgileWay Test Automation Formula

review

About the Creator

Zhimin Zhan

Test automation & CT coach, author, speaker and award-winning software developer.

A top writer on Test Automation, with 150+ articles featured in leading software testing newsletters.

My Most Viewed Articles on Vocal.

Reader insights

Be the first to share your insights about this piece.

How does it work?

Add your insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment

    Find us on social media

    Miscellaneous links

    • Explore
    • Contact
    • Privacy Policy
    • Terms of Use
    • Support

    © 2026 Creatd, Inc. All Rights Reserved.