Quality Assurance Case Study
Usually, startups are less concerned about quality, and in many cases, developers are doing the QA part of the work. We understand that it saves cost and gives a chance to release the product quickly. On the other hand, clients will get a poor quality product. This is precisely the situation we saw happen with our Client in Vancouver — a financial technology company was looking for a way to improve their quality and decided to find a partner to set up a QA team from scratch. After the RFP process, GeeksForLess was chosen as a strategic partner to start manual testing and then move towards automation testing.
Benefits Achieved
We received:
- No processes
- Developers were doing tests instead of QA
- No documentation
What we have achieved in 6 weeks:
- Created test strategy and agreed with the Client on the next steps
- Created a complete test plan and executed it
- Test reports
- Setup a process in the Client’s tracking system
- Defined the most critical steps and automated them using Codecept JS
- Documented main processes
What we did next:
- Decreased the cost of the QA department in comparison to the local market
- Enhanced the customer experience
- Improved overall product quality
- Used the best QA practices
- Saved time on testing by using automation tools such as Codecept JS
As a result, we achieved the following:
- Separated test cases per applications and projects
- Covering 99% of all requirements and already existing functionalities with test cases
- Adding basic test plans
- Automating all test cases which are stable and could be covered by the JS tool
- Established process – no more releases to production without QA confirmation
- Daily calls setup with progress updates
- Moving towards continuous integration by using special tools
- Autotests running automatically after production releases
- Setting up the QA environment
- Integrating the QA team into all project aspects so they became a part of the Client’s ecosystem customers