Dedicated QA Team for Business Software
Industry
Country
Type of Service
Cooperation Type
Project Type
Test Coverage
Overview
The client* was developing a custom software solution intended for the management of any business processes and tasks. Their product allows the creation of unique custom sheets, tables, and forms for all kinds of documentation, bug and task tracking, time and salary calculations, vacation and sick leaves tracking. This software solution allows keeping all the company’s work in a single application.
* We recognize the importance of protecting our clients’ privacy and follow the policies to maintain their confidentiality and security. That is why the company name will not be disclosed.
Challenge
The client already had an in-house QA team, but they needed more specialists to handle the scope of tasks they had. Thus, the company requested two experienced QA Engineers to work on the project full-time.
Their problem and request were typical, but the project itself was unique. The main task was to figure out the details of an ongoing product, which had been under development for a year. In other words, the specialists needed to quickly study an unfamiliar custom non-typical project. It was crucial:
- to fully understand the existing functionality;
- to figure out at what stage the project was at that moment;
- to learn what quality issues and problems were present.
It was essential to start functioning as an integral part of the client’s team from the first days after joining the project.
Solution
We agreed that QA Madness would provide a Dedicated Team – the specialists working on a project full-time and as a full-fledged part of the client’s team. The company had been working on a large, complex, and fully custom solution. The project was under continuous intense development. The chosen collaboration model is the only effective means of cooperation on such projects.
The onboarding process took several days. The QA engineers managed to figure out the details of the complex project within the given time.
After the onboarding, the specialists got fully involved in the working process. The features and tasks were divided between the two of them. Each QA engineer had a specific area of responsibility, accompanied by:
- communication with developers;
- writing and maintenance of the test case suite;
- testing of new and existing features;
- presentation of their work in daily meetings;
- communication with an analyst and a PM about the potential problems in the documentation and implementation of new features;
- running regression tests before and after releases.
Also, the QA Engineers deployed new features in independent environments in GitLab for testing. After receiving the positive results, the specialists deployed those features in the general staging environment.
Results
The QA Engineers didn’t track the number of logged bugs. The product was new, and the testing was ongoing, so naturally, the number of defects found would be great.
Meanwhile, reporting those defects helped considerably enhance the quality of particular features and the product in general. Our specialists shared recommendations regarding the improvement of software functionality and the organization of their processes. The QA Engineers helped accelerate the testing and increase the quality of each new build.
The software solution went live, and the client received the investment for this project – for its MVP version our QA engineers were working with.
Let’s Start a New Project Together
QA Madness helps tech companies strengthen their in-house teams by staffing dedicated manual and automated testing experts.
Relevant Case Studies
Ready to speed up the testing process?