Junior E2E Test Automation Engineers, Make Your Tests Useful to the Team from Day 1 and Every Day Onwards

Avoid over-test-design. Day 1 here, I mean, the first day that one has all the resources to start hands-on writing test scripts.

Image credit: https://pixabay.com/photos/reed-stepping-stone-stone-bridge-1666746/

First of all, it is very feasible to a limit (test counts, see explanations later) by the capability. Within the limit, even just a handful of simple tests, if run daily, it is useful to the team.

How do I Start Test Automation on Day 1 of Onboarding a Software Project?

After reading the above article, some junior automated testers might think, “It might appear easy because you are very experienced”. OK, read this article by my daughter, “Set up, Develop Automated UI tests and Run them in a CT server on your First day at work”, written at her first intern job (freshly out of Uni).

Table of Contents:
· How?
∘ 1. Spend little time designing tests
∘ 2. Don’t care about the stats/test count. Merge some scenarios together
∘ 3. Test Engineers: You need good feedback too!
∘ FAQ