Logo

Sprinklr

Automated Testing, Mobile Testing, Web Testing, Dedicated QA Team

Project Overview

What Sprinklr had in the testing processes when they came to us and what they got after they started working with us.

Before improvement

Tests were unstable
Each run had a different number of randomly failed tests
The team was not able to rely on the original tests to make the release
The architecture of the test suite could not be scaled and was difficult to maintain for a large number of tests
Tests took many hours to be completed
Tests couldn’t be integrated with other testing and DevOps tools

After improvement

Designed the architecture of the test framework from scratch
Built a test suite which ran auto-tests using 16 threads on multiple machines.
Results to be received much more quickly
Improved test speeds by adding the prerequisite testing data directly to the database
Integrated auto tests with Jenkins, TestRail, and Jira to have a complete test ecosystem up and running
More than 90% of the app was covered by automation tests
2,000
tests developed
16
parallel threads run for auto-tests
70%
more maintainable test suite vs. competitors
45%
defects reported with status "major"
12,000
bugs reported
10,000+
test cases designed
QA Team:
7 Test Engineers
Project length:
5 years
Technologies & Tools
Java
Selenium WebDriver
Selenide
Cucumber
Rest-assured
JMeter
TestNG
Jenkins
Multithreading
DevOps

The Challenge

Sprinklr offers a tech platform aimed at helping large brands create and manage social campaigns.

The moment when we joined the project, there was a test suite designed and developed by another company from India. Tests were unstable because each one that ran had a different number of randomly failed tests. As a result, the team was not able to rely on the original tests to make the release. Also, they took many hours to be completed. The architecture of the test suite could not be scaled and was difficult to maintain for a large number of tests, and they couldn’t be integrated with other testing and DevOps tools.

The task was to build a formal QA process, stabilize automated tests, and increase their speed. We also learned that we should have redesigned the architecture to support integration with 3rd parties and designed and kept test documentation up to date.

Achievements

DeviQA designed the architecture of the test framework from scratch and developed more than 2,000 auto-tests. We built a test suite which ran auto-tests using 16 threads on multiple machines. This enabled the results to be received much more quickly. Also, we improved test speeds by adding the prerequisite testing data directly to the database.

A team of seven people performed full cycle testing of the project. Our expertise and solutions enabled us to significantly improve the quality of the product. The designed and developed automated tests allows the product team to rely on and increase the efficiency of development and testing processes. We integrated auto tests with Jenkins, TestRail, and Jira to have a complete test ecosystem up and running.

Performance testing was also a part of the QA strategy designed by DeviQA and was implemented using JMeter. The suite and all scenarios were created from scratch. Remote monitors were setup on the server side and configured to catch the metrics.

Automated and performance tests were integrated into a Continuous Integration process, which enabled the team to detect and solve issues ASAP.

Services Provided

4 automated QA engineers were responsible for automated test suite architecture design, scripts development, scenarios design, and code maintenance. We worked closely with the client’s in-house development team for a smooth integration into existing development process.

Automated Testing

Part of our team worked on the mobile version of the application. More than 90% of the app was covered by test cases and 12,000 mobile bugs were found and reported. 100+ devices were used during the testing process.

Mobile Testing

Most of the manual and automation testing was focused on Web application. We used such services like BrowserStack and SauceLabs to run tests in cloud. 10 virtual machines used during our QA work.

Web Testing

A team of 7 engineers worked on the project as a dedicated team. All specialists were smoothly integrated into the client’s team and worked together as a single efficient mechanism. They participated on daily standup, planning, demo, retrospective sessions, and all client’s meetings. They were an integral part of the team.

Dedicated QA Team