For Manual Testing, we launched and optimized the regression process from scratch and created a regression checklist. The checklist includes all the tests that should be executed in the scope of the regression session. We assigned a team of manual testers to go through the checklist quickly to get faster results, which overall optimized the regression process.

Since only some tests are currently covered by automation, regression testing is a great way to give our client confidence that what they put out in production is stable, clear, and will work for their users.

For their CI/CD needs, we were able to recommend and implement great monitoring tools quickly, and also suggested and implemented a CI/CD platform.

We created a high-level automation strategy, which included lists of tests prioritized by what needs to be optimized first for the client to gain the most value. Our key engineers prepared the prioritized tests and created clear instructions for the automation engineers.

Our objective was to provide a QA lead to help the client manage automated tests and assign tasks to the team. We also brought dedicated QAs who focused on collaborating with our automation engineer and writing materials to be automated.

In the end, our teams wrote and added multiple automated tests and fully implemented CI/CD on their environments for Tribal Credit’s 1.0 and 2.0 systems. We also set up testing environments and tools according to the project needs for each of the QA engineer’s workstations.

Testing ensures that user flow –such as sign-in– will be smooth and free of errors.

Testing ensures that user flow –such as sign-in– will be smooth and free of errors.

The Benefits

The QA processes we established greatly helped Tribal Credit transition from their 1.0 to 2.0 system.

The QA teams have a high level of communication with each other, and each team is able to work independently. The teams are able to drive the process even when there is a lack of information or other blockers since they were taught troubleshooting skills to get the job done.

Our lead QA created and implemented many QA processes the client still uses, as she drove many parts of the process and knew how to best prepare the client. Several of the recommendations she proposed, the client accepted and is now using, including:

Ways for the client’s flow of development/validation to be better communicated between developers, PMs, and QAs, to resolve issues quickly and improve the QA process.
A better system to divide the testers into teams.
Our lead QA brought specific troubleshooting skills so both our team and the client’s team would be more and achieve a higher performance level.
We proposed a basic flow on how the client can use automated testing on their project (the system, the approach, and the ground rules)
We requested for the tasks to be examined in advance while developers are working on them, so testers can enter test cases fully prepared

The CI/CD platform we recommended to the client, TeamCity, has been highly regarded by the client, and they like how user-friendly their interface is, and that their QA team can monitor reports of autotests running on a daily basis to see the status of their system.

Automated-Testing-Proves-Value-Over-Time