Overview
Tareenity collaborated with AKQA Berlin on the Dr, Oetker project, a German multinational company that produces a wide range of food products. The QA team was responsible for testing the entire site from scratch to ensure all features were working properly and to identify any hidden bugs. They performed backend and frontend testing, used JIRA and Confluence for bug tracking and management, wrote and executed test cases, performed load and usability testing, identifying potential security vulnerabilities and performance issues, and ensured cross-browser compatibility. The project involved multiple platforms, including desktop, mobile, and tablet, and was primarily targeted towards the European market.
Challenges
The main challenge for the Dr. Oetker project was to test each and every component of the website and ensure that there were no hidden bugs. This involved performing both back-end and front-end testing, using tools such as GraphQL CMS, JIRA, Jmeter, Pagespeed insight, and Confluence to track and manage bugs and gather project-related data. Additionally, the team had to execute test cases using the test pad tool, based on the Figma designs and stories provided, and perform testing on various environments, including DEV, QA, and Staging. Other challenges included identifying potential security vulnerabilities and performance issues, checking cross-browser compatibility, and performing database testing inherited from the product CMS. Finally, the team had to migrate the database to the new build site using CMS.
Solution & Strategy
To address the challenges faced in the Dr. Oetker project, the QA team implemented the following solutions and strategies:
- Backend and front-end testing: Performed rigorous testing on both the backend using GraphQL CMS and front-end components to ensure optimal functionality and no hidden bugs.
- JIRA for bug tracking and ticket management: Used JIRA, a bug tracking and ticket management tool, to keep track of all the bugs and issues identified during the testing process.
- Confluence for project data: Used Confluence, a collaboration and documentation tool, to gather and store all the data related to the project.
- Testing according to designs and stories: Each ticket (story or task) was tested according to the Figma designs provided, with test cases written and executed using the test pad tool.
- During our testing on this project, We performed regression testing and smoke testing to ensure the stability and reliability of the system.
- Multiple environment testing: Performed front-end testing on various environments such as DEV, QA, and Staging to ensure that the site was functional and consistent across all platforms.
- Security, performance, and usability testing: Conducted security, performance, and usability testing to ensure that the site met all the necessary requirements and was safe for use.
- Cross-browser compatibility testing: Tested the site across multiple browsers to ensure that it was functional and displayed correctly on all platforms.
- Database testing: Performed database testing on the inherited product CMS and migrated it to a new build site using CMS.
By implementing these solutions and strategies, the QA team was able to overcome the challenges faced during the Dr Oetker project and deliver a high-quality, functional website for the client.
Conclusion
Tareenity was responsible for testing Dr. Oetker’s website from scratch, ensuring that all features worked properly, and identifying potential bugs, security vulnerabilities, cross-browser compatibility issues, and performance issues. They performed backend and front-end testing, used JIRA for bug tracking and Confluence to gather project data, executed test cases using TestPad, and conducted load and usability testing. Their efforts contributed to the successful migration of the site to a new build using CMS, ensuring a smooth user experience for customers.