Why do we need to automate tests

Test automation - why, why, what for?

The following points represent the advantages and disadvantages of test automation and manual testing:

Manual testing is very time-consuming and therefore cost-intensive, but in contrast to test automation, it has one lower entry barrier. In contrast, the Test automation the greatest effort at the beginning: in the familiarization with the appropriate tools and frameworks and through the creation of the appropriate test cases.

Manual tests

Automated tests

Carelessness

Always identical design

Reaction to changes is possible at any time

Limited response options

Time and cost intensive

Significantly less time to carry out a test case

Ad hoc tests possible at any time

No testing or adjustment without human intervention

Every step has to be done by people
and be checked.

Does not need human assistance; Tests can start automatically.

Reaction to the unexpected is possible.

No spontaneous / exploratory testing, requires a clear test case


Ranorex - Because?

At netzkern, Ranorex Studio is the tool of choice for test automation.

The reason for this is, among other things, the very good compatibility with the most common browser versions, which guarantees that created in Ranorex Test cases always with the latest browser versions can be tested.

During tests with other automation frameworks (Selenium / Protractor) we sometimes had to work with browser versions that were more than 3 months old, because the automation software was not compatible with newer browser versions and the test cases could not be executed.

In addition, Ranorex Studio also brings one large amount of functions that would first have to be developed with other automation tools.

An example of this: the Reporting function from Ranorex. After each test case carried out, Ranorex automatically creates a report.

This contains all the important information about the test case carried out: total time of the test, actions carried out, failed or successful validations, etc.

In this way, the results of every test case carried out are automatically documented.

Getting started with Ranorex Studio is easy for experienced and inexperienced test engineers alike.

The user has two options for generating test cases - regardless of whether it is a test for a web app / website, a "native" desktop software or a mobile app (iOS, Android):

The first option is to create one Test cases based on a recordingsFor this purpose, Ranorex offers the possibility to record all actions carried out (e.g. clicks on a website or calling up certain functions). This recording can be edited and customized afterwards.

The second option is to create a Test cases based on a so-called. Code modules. The test engineer can choose between the programming languages ​​C # and VB.Net. In a code module, the test engineer then has to define the actions to be carried out in the test case in the code.



The advantage of code modules is the possibility of better customization. In contrast to recordings, it is possible in code modules (through the use of "loops" and conditions) to carry out certain actions repeatedly or to make certain decisions based on predefined conditions.


More time for test creation

We decided on Ranorex Studio to invest more time in creating test cases and not in programming supporting features. Ranorex gives us the opportunity to create test cases with any type of software (desktop / mobile / web) and to adapt them to new circumstances at any time without having to create the test case from scratch.