Overview
When we received the project for the AudiUSA website, our initial focus was on conducting regression testing across the entire site. This involved testing various aspects of the site, including the catalog of Audi models, model landing pages, model specification pages, and model booking pages.
Challenges
- Test Coverage: One major challenge while rewriting the test cases was to cover all the important aspects of the website. As the website had various features such as profile functionality, which allowed users to register accounts, manage their profiles, select favourite models, choose their favourite specs for their saved model, and add already purchased models to their accounts.
- Time Constraints: As it was an ongoing project we often had to GO LIVE right after completing all testing. Ensuring that all the necessary testing was done within a given time frame was a challenge.
- Communication and Coordination: As there were multiple QAs working on the project from different time zones, communication, and coordination were a challenge. It was important to ensure that all the QAs were on the same page and had a common understanding of the project requirements and timelines.
- Data Management: As the website includes user profiles and their saved models, it is important to ensure that the data is managed properly during testing.
- Regression Testing: As the website was live and undergoing updates, it was important to perform regression testing to ensure that the changes made to the website did not impact the existing functionality.
- To address the issue of redundant test scripts, we performed a thorough analysis of the existing test scripts and identified the ones that were no longer relevant. We then removed those test scripts and created new ones that covered the latest functionality of the website.
- We also made sure to ensure smooth collaboration between the QAs working in different time zones, we implemented the following strategy.
- Established a clear communication plan that includes the frequency and mode of communication, this was via comprehensive release notes and an hour-long meeting at the end of the day to triage bugs.
- Agreed on a common understanding of project scope, goals, timelines, and requirements.
- Established a shared repository of test scripts and results that could be accessed by all team members.
- Scheduled overlapping work hours to facilitate real-time collaboration and communication.
- Designated a point of contact who served as a liaison between the different teams.
We also created a brand new set of smoke tests that were executed instead of the Regression pack when the team was required to shift their focus on something specific.
Conclusion
The project achieved its goals by improving website quality and achieving efficient collaboration. The website updates resulted in a more engaged target audience and user retention.
We successfully addressed the issue of redundant test scripts and improved collaboration across time zones. It removed irrelevant scripts, established clear communication, shared a repository, scheduled overlapping work hours, designated a point of contact and introduced adaptive smoke tests.