AUTO1 Group

The journey of a QA engineer in AUTO1 Tech

By Dhivya Venugopal

Dhivya is a Junior QA Engineer in the AUTO1 Berlin office.

< Back to list


Hi there! My name is Dhivya and I started my career as a Software Engineer in Tech Support and Testing. After a brief sabbatical, in the mid of 2021, I decided to get back into the workforce. I was searching for the right opportunity to kickstart my career and I was very excited to land a job at AUTO1 as a Junior QA Engineer.

Onboarding experience

Having previous experience in manual testing, I was greatly looking forward to this opportunity to deep dive into the world of automation testing. Onboarding happened seamlessly thanks to the onboarding handbooks and Confluence resources specially curated for a new joiner in the AUTO1 QA team. It briefed the step-by-step process on how to set up and get ready for the automation testing at AUTO1.

The CAT (Core Automation Team) people were readily available to guide me in each step, right from setting up the environment, software, and configurations. This was a first-time experience for me, seeing such a dedicated team exclusively being there to support the entire QA team.

CAT (Core Automation Team)

I found myself doing extensive testing of SHIFT, our internal test case management software developed and used by AUTO1. This gave me some in-depth knowledge of the software itself and also the processes and automation structure set in the company.

In the months that followed, I was excited to take up some solid training from my amazing mentor, who introduced me to the project and the automation tests we had in place. He was very resourceful and immensely patient and carefully introduced me to each element of the role, gradually allowing me to explore the various tasks I would eventually take up. This gave me ample opportunity to get a deep understanding of the project and build a good rapport with my team members and also established a clear goal for me. I was soon writing my first automation test and found the experience thoroughly organic and gratifying.

Automation Testing at AUTO1

Firstly, I understood why Automation Testing has become a quintessential part of current testing standards and how it helped our teams achieve great speed, efficiency, and quality. The automation tests and resources were brilliantly abstracted in several repositories and accessed by the various QA teams.

With 600+ microservices, automation testing is the best way to ensure that the entire platform works efficiently. We use a variety of test automation tools including Selenium and Playwright to drive the automation. The entire framework has been abstracted into a common module in repositories that has helper methods pertaining to our domain. Each team has their dedicated repositories that carry out regular automation test runs, generating regular test reports and this structure helped us keep track of the health and sanity of the systems we worked with.

The Automation Testing process at AUTO1 looks just like this:


Test data management using SHIFT

The test cases, scenarios, and strategies are maintained in SHIFT, our internal (and soon to be open-sourced) test case management system. Our QAs make use of a test data tool which is integrated to SHIFT. The 100+ types of test data required by the teams are generated using automation suites that run in Jenkins. This test data is then queued in SHIFT and as a result increased the productivity of our QA team by reducing the effort for manual test data creation. Our director of QA has briefed this here

Seamless Integrations

Our CI system, Jenkins, is wired to run these tests against our various QA environments. The integration of SHIFT with Slack, Jenkins, and Jira has helped the teams immensely. The status of Jenkins jobs/sanity suites is notified in Slack. The time taken to debug the issue is hugely reduced since SHIFT displays a precise list of failed tests including the screenshot reference, which helps me to quickly understand the exact point of failure. Once I have identified the issue, I fix it and test it locally, then push the branch to our repository. The process is set in such a way that merge can be done only after review, which gives me more confidence and validation for the proposed solution. This helps me address the issues faster and get the system up and running. This is indeed why the QA team at AUTO1 is one of the key pillars of the Engineering team.

My automation testing journey at AUTO1 could not have been this impactful if not for this perfect blend of the best tech stacks and resources, and most importantly, my amazing team. My learning on the job has been very effective and hands-on, and it makes each day filled with new challenges and new learning opportunities that help my work create a real impact.

From the very many opportunities that came my way and the deep learning curve it has presented me with, I now realize that - the journey has just begun!

Stories you might like:
By Joanna Tyka

Early bird gets the worm - or how preparing in time can reduce the effort needed in manual testing.

By Michal Chytroszek

The first article in a series of articles focusing on efficient testing.

By Eliza Korab

A quick look at various libraries and tools that could make your life easier and open up new...