E2E Test Automation Learners’ Common Mistake in Coaching: Too Keen on Completing Work Test Cases

Should focus on learning, instead, at least initially.

By Zhimin ZhanPublished 2 years ago • 4 min read

Image credit: https://pixabay.com/vectors/training-course-business-session-5822607/

The original article was published on Medium, 2023-09-08

Yesterday, I had a 30-minute Test Automation Coaching session (for $1, limited to one per month, once per user) with one motivated automated tester, from Africa. It is my first time talking to an African automated tester, via Zoom. (I had one thank-you message from an Ethiopia tester, for creating TestWise IDE and making it freely useable.)

I firmly believe that the AgileWay Test Automation Formula (raw Selenium WebDriver + RSpec, with TestWise & BuildWise) can help motivated IT professionals in developing countries and maybe transform their lives. There are US companies, such as 37signals, that pay remote workers with US engineers’ rates. Imagine a Vietnam automated tester landed such a job with a US$100+K annual salary. (Remember, real test automation engineers are rare.)

Extracted from Wired Article: “The Software Revolution Behind LinkedIn’s Gushing Profits”; Even LinkedIn cannot hire, need to lure (seem directly order from the top executive)

As expected, during the coaching session, this tester was eager to get my help in implementing test cases for his app. This is very common and understandable, but it is not advisable.

At night time, my best friend’s nephew (a young IT Uni student) also started the coaching session for the first time. Compared to the morning’s one, this young Uni student learned much more. The reason: he was in a pure learning mode and followed my instructions.

The morning’s tester, as I could tell from the past interaction via messaging, is motivated and with some level of skills. However, he forgot the criteria for 30-min $1 session: “(limited to web apps using Selenium WebDriver)”. He started with asking me how to do X in Playwright?
Anyway, I answered a few his questions on test design, live creating a couple of simple tests in raw Selenium (using TestWise) to showcase some efficient testing-authoring techniques. I sent him the test project after the session.
Frankly, I think he has potential to be a good test automation engineer. However, he already started with Playwright in JS, pity (check out the article, Why JavaScript Is Not a Suitable Language for Real Web Test Automation?). I only can wish him luck.

1. For implementing automated tests, there is a much cheaper alternative than one-on-one coaching.

The daily rate for a test automation coach typically hovers around US$ 2000. While larger corporations may not face financial constraints, the true challenge lies in the scarcity of available test automation engineers, making them precious. For many mid-sized software companies, engaging such professionals for extended periods is often financially out of reach and even more daunting for individual clients.

If your primary need is to have test cases created, you may consider utilizing a specialized test script authoring service like AgileWay’s Web Test Automation Creation Service, which offers a cost-effective option, starting from $1 per test step.

2. Mentees are tense

These mentees are like doing an exam under pressure. “oh, there is another one…”. They are not in a good learning mode, with a “just get it done” mindset, which doesn’t really understand E2E Test Automation.

3. If the coach helped implement all test cases, so what?

Your app will change (in Agile: constantly and frequently), meaning a fair percentage of automated E2E tests will start to fail, without ongoing maintenance. The testers would soon give up without good test automation maintenance skills and mindset. (That’s common, right?)

4. A fair percentage are duplication, with little/no learning value

Lose the meaning of coaching.

The Better Way: Switch to learning mode

A wise way to follow the mentor exactly is by doing guided exercises. In fact, that’s how we learn from schooling. Remember, the content of the textbooks is organized with purpose. “Follow the book”.

To put it in simple words, during test automation coaching, you shall get the most from the coach as quickly and much as possible. So, explaining the business logic and navigating your app is a poor use of the coach’s time, i.e. wasting money.

Before you master a skill to a certain level, it is better to learn: by following the instructor. Of course, not blindly. You will assess (which is quite easy in E2E Test automation) the usefulness of newly learned knowledge/skills/practice, not how many test cases the coach did.

Practice and Practice, then take the learning back to work

The web hasn’t changed much for over two decades. In other words, the skills and techniques you learned from the coach will be applicable to your work. Be patient and learn as the coach (if you trust him/her) told you so.

After practising and reaching a ready stage (trust me, you will know), then use newly learned skills to develop work tests.

Of course, there will still be challenges. You can contact the coach with specific help, that will be focused. For example, “How to automate Shadow DOM?”, the solution may or may not be related to our work app. See, that’s learning.