Some thoughts on E2E automation

Recently, as part of my job as Senior QA Automation Engineer, I worked on writting the guidelines for the e2e automation of Red Hat Developer Hub that you can see here, and I wanted to share some thoughts on the subject.

Architecting and implementing a e2e automation project is a really easy task. In general terms, all you have to do is follow three simple rules at all times:

1. Check the preconditions. If tests are running in parallel, try to create the preconditions you need to avoid race conditions.

2. Each test has to test one and only one thing. Check this article from the Cypress webpage.

3. All tests have to contain preconditions, actions, and assertions (with a reliable source of truth), like you whould do in Gherkin; think in those terms.

If you follow those rules, it would be really difficult to mess with your automation project. Just having this in mind at all times will make your project more likely to succeed. Of course, this is not all that you have to do, but it’s the perfect starting point.

I want to start a serie of posts about automation and QA. I realize that I have a lot of knowledge to share and I want to put them on paper, also for my future self.

Stay tuned!🤖