Test Automation

Test Automation

Why Test Automation?

In conditions of fast IT development and consumer markets growth, the requirements to software quality become higher and the speed of software production - faster. In order to make our customers meet the market demands by continuously releasing and maintaining new products without spending much time and money on quality evaluation, QATestLab performs test automation for software projects of all sizes.

Often, quality assessment includes check of the same and similar test cases. The automation is aimed to speed up testing process without losing its effectiveness and providing wider test coverage, especially if the functionality is large and complex. Being run unattended, automated tests need less human work and can be launch even at night which saves time and accelerates the release.

Despite rather high initial cost, test automation provides the increase of ROI (Return on Investments), also, implemented automation tools can be used several times for different projects. Besides, in comparison with manual testing, test automation requires less time and human resources. Also, it leads to increase of the QA team productivity as they should not execute each casemanually, one by one.

How we test

When selecting the automation tool, we analyze the industry specifics, take into account business goals and customer’s requirements and expectations, and define the scope of automation.

For every project in financial, banking, healthcare and e-commerce spheres, we not only choose the ready tool individually but also write our own test scripts.

test automation tools grey

Tools we use

We perform test automation for web, mobile and desktop applications. Possessing high programming skills, we design test scripts in Java and C# for web browser automation. To optimize the procedure, we use the frameworks JUnit, TestNG and NUnit, which are unable to run scripts in parallel.

Reporting is essential for the success of every project. We use the following solutions for results reporting:
  • ReportNG or Allure by running them together with TestNG for Java projects

We generate our reports in HTML format that can be easily converted and sent by email.

We support all our developed scripts with detailed step-by-step instructions to ensure their easy usage. We provide documented set up procedure, description of the software to be installed, possible troubles and ways to avoid them. We also maintain our scripts if the application was modified.

Testing PurposeTools we use
Web Applications
Programming languagesJava, C#
FrameworksSelenium, JUnit, TestNG, NUnit
ReportingReportNG, Allure, NUnit add-ins
Cross browser and cross platform testing- 3rd party services (BrowserStack, SauceLabs, Testdroid…)
- Local infrastructure using Selenium Grid
Desktop Applications
ToolsRanorex Studio, TestCompete, RIATest
FrameworksTestStack.White, Appium
Mobile Applications
Multi-platform applicationsAppium, Ranorex
For multi-platform applications, we develop scripts using Appium. Being on a tight schedule, we apply such universal automation tool as Ranorex. But such scripts cannot be easily updated so we try to avoid their usage.

When you do NOT need test automation

Before taking a project, we always check whether automation is really required in order to save our customer expenses.

When you do NOT need test automation

We never automate tests cases:

  • that are newly designed and do not pass manual testing at least once,
  • for projects, where requirements are changing very fast,
  • to check user interface,
  • if they are launched on ad hoc basis,
  • when time is limited, in this case automation is not effective,
  • if automation is required for a single test run before release,
  • when automation takes more time and money, than manual testing,
  • for mobile games and other containers, e.g. online maps, Flash / Silverlight, while they cannot be checked automatically