This was our first-ever testing experience for this product, and working with an unfamiliar solution can often be challenging. Moreover, there was already a large number of test cases created by the previous team working on the project, and because these test cases were written for a different environment, it took us time and effort to incorporate the cases into our work.
The first part of the challenge — working with an unfamiliar product — was resolved thanks to the existing experience our team members had with the product as a test management solution. As for the second part, the expertise of our Automation QAs helped us manage the existing test cases with maximum efficiency in a limited time period.
To deliver the required scope of testing, we performed functional testing to verify the core functionality of the product, and then we used regression testing to make sure that the recent changes did not have any negative impact on the product. Other types of testing we employed in this project were:
- Acceptance testing
- Security testing
- Performance testing
- Edge case testing
This was also a project where we used both manual and automated testing. We employed automated testing with the help of Selenium to check the consistency and integrity of the test cases created by the previous team working on the project.
Our team consisted of five QA engineers, including two Automation QAs and a QA Team Lead.
- Selenium WebDriver
- Chrome DevTools
- email Zoom
- Updated test cases
- A change log
- A detailed bug list
This was a short-term project, but our relationship with this client has been long and fruitful, so we are always looking for a chance to collaborate with them again and further contribute to the impeccable quality of their solutions.