Test Automation
Architecture Design Services

1 day to run regression testing

1 day to run smoke testing

60% increase in the number of regression tests and relevant test cases

90% test coverage

27 localizations supported by QA engineers

>1500 automated test scenarios created

Built smooth and well-working processes

Test automation : smoke, API, UI on all supported browsers

Full coverage of the application by test cases

Adjusted the Jira workflow, integrated TestRail with Jira to be able to see statisticls of the issues per release

Developed necessary test artifacts that adhere to industry standards and are easily maintainable

Added multithreading to run tests in parallel on 10 different threads, which reduced the time of the test run in 7 times

2 days to run regression testing

>1500 released features

>5k of the critical/blocker/major bugs detected

>7500 test cases written

>10 trained QA specialists on the client’s side

The product became stable and robust

Automated testing was introduced

Created and maintained all required test documentation

> 60% high priority bugs reported

1400+ E2E automation scripts created

90% of the delivered features are covered with autotests

10 mins to run the entire automated smoke testing suite

< 2 weeks to create the infrastructure for a new client

>1900 test cases added

>700 automated tests added

98% test coverage of the desktop agent

2 hours to run regression testing

80% test coverage

30 different machines for running autotests

10 threads for running tests on each machine

4-5 releases per day

~15 squads each with a straight and clear working plan

200+ e2e test cases for the whole app

2 weeks max to release a new feature

Clear and fast way to release any fix

Automation regression testing took 2 hours instead of 2 weeks of manual testing activities

We established a formal QA process by designing and presenting it to the rest of the team for familiarization and implementation

Designed the architecture of the test framework from scratch

Integrated auto tests with Jenkins, TestRail, and Jira to have a complete test ecosystem up and running

Built a test suite that ran auto-tests using 16 threads on multiple machines

We conducted a comprehensive review of the existing test suite, identified areas of improvement and implemented best testing practices

The number of issues reduced to 25 % after automation was properly implemented

SoftNAS experienced several benefits, including faster test results and the acquisition of stable automated tests, resulting in improved deployment capabilities

>90% of the application was covered with test cases

100% coverage was ensured for smoke and sanity testing

>300 blocker issues were detected

The number of customer support issues was reduced by more than 50%

Created and fully stabilized the testing process

The first release was completed three months after we started working on the project

Prevented huge number of blockers and crashes caused by the big amount of merging

18 hours to run regression testing

4 hours to run smoke testing

100% coverage of all existing sub-products

5 generations of OS for iOS and Android and different devices supported

6 hours to run regression testing

>2000+ automated scripts for API testing

Smoke testing taking 1 hour to run

A mini API test suite is executed after each PR, taking 10 minutes only

>4000+ automated UI + API tests

~30 minutes to execute automated smoke testing

100% test cases reviewed

>900 test cases are up to date and integrated into the workflow

>600 test cases updated

100% of the smoke tests automated

All existing autotests are up-to-date

~2800 autotests added

>90% of test cases are automated

~99% of smoke tests are automated

~95% decrease in post-release regression bugs, the implementation of test automation has proven to be highly effective

Fine-tuned QA process set up from scratch

Comprehensive automation testing process implemented from scratch

Transfer to a new CI/CD

4 hours to run a regression test suite

5 parallel threads

>400 reported bugs

>1200 reported defects

>50 reported improvements

>3 successful releases of a new mobile application

90% test coverage

4 localizations supported

>600 automated tests created

>10% of the translations are covered with automated tests

~3000 autotests

k6-based autotests were integrated into a release flow

~90% of test data is generated by API, resulting in 2.5 times reduction in execution time

The latest version of the Cypress framework is used

<10 mins to run automated smoke testing

<1 hour to run automated regression testing

~90% of the app is covered with test cases

>80% of the delivered features are covered with autotests

1.3k automated scenarios in total

1.5 hours to run automated regression testing

2 applications are covered with automated regression tests

1k+ test cases created

>90% of the software is covered with detailed and relevant test cases

>400 automated scripts were created in the first 6 months

3 days to run regression testing

2x faster task handling

An efficient and transparent QA process was set up from scratch

Well-structured test cases were created to cover the main scenarios

Following best practices, automation testing utilized independent tests, API-driven data creation, and the Page Object Pattern

6,000+ test cases have been created for the web apps

2,500+ automation tests have been created

~200 automation mobile tests have been created

Allure reporter has been introduced

<1 hour is needed to execute manual smoke testing

100% of the test cases were reviewed

150+ Postman test cases were created and integrated into the workflow

~2 hours were needed to run regression testing

5 various devices with different operating systems, screen resolutions, and browsers were used to run regression testing

>1000 automated tests were developed

4 browsers were supported

Manual story testing and verification was built from scratch

99% of the application was covered with test cases and the smoke and regression checklists

A well-structured test plan enabling thorough validation was created

A fully autonomous QA process was set up where QA engineers were fully responsible for testing

1 working day was needed to complete regression testing

<60 minutes were needed to finish smoke testing

5+ platforms were supported

5 localizations were supported

>75% of the Shops functionality was covered with regression tests

500+ E2EE test cases were created

<1 week is needed to run regression testing

>6 various devices with the latest OS versions are used to run regression testing

>150 automated tests have been created

>100 bugs have been reported

3 browsers are supported

2x faster task handling

3 hours were needed to complete regression testing

>300 functional and non-functional bugs were reported

350+ automation scenarios were created

>85% of the product was covered with automated tests

350+ test cases were created from scratch

A QA team participates in creating ticket scope for upcoming releases

All the required test documentation has been rewritten

>6,000 test cases have been written for a regression test suite for client applications

The DeviQA engineers have reduced the number of bugs reported by clients/therapists

280+ regression E2EE cases have been created, which let a team reduce the time of regression testing to 1.5 days

~40% of tests have been automated, and this value is growing

100% of the core flow is covered with documentation

5+ performance suites have been created

0-1 failure is in a regression test run due to the solid test logic

All test data is generated on the fly

Mechanisms for data cleaning have been created

Dynamic test users are used

1 day to run regression testing

1 day to run smoke testing

60% increase in the number of regression tests and relevant test cases

90% test coverage

27 localizations supported by QA engineers

>1500 automated test scenarios created

Built smooth and well-working processes

Test automation : smoke, API, UI on all supported browsers

Full coverage of the application by test cases

Adjusted the Jira workflow, integrated TestRail with Jira to be able to see statisticls of the issues per release

Developed necessary test artifacts that adhere to industry standards and are easily maintainable

Added multithreading to run tests in parallel on 10 different threads, which reduced the time of the test run in 7 times

2 days to run regression testing

>1500 released features

>5k of the critical/blocker/major bugs detected

>7500 test cases written

>10 trained QA specialists on the client’s side

The product became stable and robust

Automated testing was introduced

Created and maintained all required test documentation

> 60% high priority bugs reported

1400+ E2E automation scripts created

90% of the delivered features are covered with autotests

10 mins to run the entire automated smoke testing suite

< 2 weeks to create the infrastructure for a new client

>1900 test cases added

>700 automated tests added

98% test coverage of the desktop agent

2 hours to run regression testing

80% test coverage

30 different machines for running autotests

10 threads for running tests on each machine

4-5 releases per day

~15 squads each with a straight and clear working plan

200+ e2e test cases for the whole app

2 weeks max to release a new feature

Clear and fast way to release any fix

Automation regression testing took 2 hours instead of 2 weeks of manual testing activities

We established a formal QA process by designing and presenting it to the rest of the team for familiarization and implementation

Designed the architecture of the test framework from scratch

Integrated auto tests with Jenkins, TestRail, and Jira to have a complete test ecosystem up and running

Built a test suite that ran auto-tests using 16 threads on multiple machines

We conducted a comprehensive review of the existing test suite, identified areas of improvement and implemented best testing practices

The number of issues reduced to 25 % after automation was properly implemented

SoftNAS experienced several benefits, including faster test results and the acquisition of stable automated tests, resulting in improved deployment capabilities

>90% of the application was covered with test cases

100% coverage was ensured for smoke and sanity testing

>300 blocker issues were detected

The number of customer support issues was reduced by more than 50%

Created and fully stabilized the testing process

The first release was completed three months after we started working on the project

Prevented huge number of blockers and crashes caused by the big amount of merging

18 hours to run regression testing

4 hours to run smoke testing

100% coverage of all existing sub-products

5 generations of OS for iOS and Android and different devices supported

6 hours to run regression testing

>2000+ automated scripts for API testing