I recently embarked on writing some new automated end-to-end tests for an existing product that has been around for some time but has never had e2e automated tests written for it.
There’s two ways to use that existing product: there’s the most commonly used and comprehensive user interface for that product, and a less common but new user interface that isn’t yet as fully featured.
I decided to automate the older user interface as it was more comprehensive and has lots more users, so it has to be better right? Wrong. What I didn’t take into account was our company’s strategy of getting everyone onto the new user interface, even though it’s not fully comprehensive yet.
End-to-end automated tests are a long term investment and investing against something the company is actively moving away from is a mistake.
Fortunately I was able to see my mistake early enough to ‘correct course’ and start using the new user interface. The development of the automated end-to-end tests against the new user interface has the added benefit of identifying the gaps in functionality so that we can make sure these are known and addressed.
Have you ever been in a similar situation and what did you do?