Skip to content

Syndicate content
Updated: 3 hours 4 min ago

Integrate Automated Testing into Any Continuous Integration Process

Wed, 07/20/2016 - 09:24

Long gone is the time of waterfall’s strictly separated development & testing phases. Today, it’s all about fast feedback, quick iterations and frequent releases at a previously unseen velocity. It requires an agile methodology to keep up with the high demands. Your team’s success depends on a supporting infrastructure with the right tooling. Without any doubt, automation plays an essential role here. Our tip: Integrate test automation into your continuous integration (CI) process.

We wouldn’t want you to waste precious time if you’ve your development environment already set up. That’s why you can integrate Ranorex into any continuous integration process. Let’s have a closer look at the benefits of integrating test automation into your CI system, and how you can do it:

continuous integration automated testing overview

Automated testing and continuous integration

The idea of continuous integration is to frequently promote code changes and rapidly get feedback about the impact these changes have on the application or system. Including test automation in the development cycle enables you to automatically test each incremental code change.

So basically every time a developer commits code changes to the version control system (VCS) such as Git or TFVC, a build of the application under test as well as the Ranorex test automation project is triggered in the CI system. The resulting test automation executable then runs against the application under test.

To evaluate the outcome of the automated test, the continuous integration tool examines the return value of the executable or its output text (e.g. “TEST FAILED” for failure). With Ranorex, the return value ‘0′ signals the successful execution of the test script, while the return value ‘-1′ signals a failure. Each team member automatically receives a notification about a finished build. This notification includes build logs as well as a test execution report.

Advantages of integrating Ranorex into your CI system:
  • As each code change is immediately tested, potentially introduced bugs are found faster, which ultimately makes it easier to fix them.
  • The test automation report enhances transparency, as each team member will receive instant feedback about the state of code.
  • There’re no integration problems, as Ranorex can be integrated into any CI tool.
Setting up Ranorex test automation in your CI system

Note: You have to install Ranorex on each machine you’d like to execute Ranorex tests on. You’ll need a valid license to do so. Please find more information about Ranorex licenses on our dedicated Pricing page.

Each committed change in the application under test and the test automation project should be automatically tested. In other words, every change should trigger these 3 steps:

  • building the application under test
  • building the Ranorex test suite
  • executing the Ranorex test suite

continuous integration automation testing in detail

First, you need to manually set up these steps in your CI system.

1. Build the application under test

The first build step should generate an executable of your application under test. This executable should later be triggered from the Ranorex test suite project.
Thus, add a build step which will build your application under test (e.g. MSBuild build step, Ant build step, …).

2. Build the Ranorex test suite

In this second step, you’ll need to generate an executable to automate your application under test. To do so, add a build step (MSBuild or Visual Studio) and choose the project file (*.csproj) of your Ranorex project which should be built.

3. Execute the Ranorex test suite

The third step should execute the previously created executables. Simply add an execution step triggering the *.exe file of the test automation project and define the command line arguments if needed.

The test execution should now be triggered on the same system the projects were built on. If you want to trigger the execution on another system, you need to deploy the built executables and all connected files to that system. Please make sure to execute the application under test and the Ranorex test suite in a desktop and not in a console session.

Automated testing of frequent code changes

If the code of your application under test or your test automation project changes frequently, it doesn’t make sense to run the entire test suite including all test cases with every build. Instead, you should run only those test cases that are affected by the changes. How? Run configurations!
You can add and edit run configurations directly in the test suite (see user guide section ‘Running a Test Suite’).

You can trigger a run configuration using a command line argument. The following command line, for example, will run the test suite executable ‘TestCIProject’ with the run configuration (/rc) ‘SmokeTest’ and generate a zipped report file (/zr /zrf) ‘Report.rxzlog’ in the folder ‘/Reports/’.

TestCIProject.exe /rc:SmokeTest /zr /zrf:Reports/Report.rxzlog

Interested in more command line arguments? You find more in the user guide section ‘Running Tests without Ranorex Studio‘.

Test automation report – the importance of feedback

“No news is good news” is definitely not true for agile teams. It’s important that everyone in a team – whether it is a developer or tester – knows about the state of the code and, thus, the outcome of the automated test run. It really couldn’t be any easier: Simply add a post build action which sends a mail to your team members with the build log and the generated zipped report attached.

Integrate Ranorex into a specific CI system:

You’re using a specific CI tool? Whether it’s Bamboo, Jenkins, HP Quality Center, TeamCity or Microsoft Test Manager – check out the section below to find a detailed instruction on how to integrate Ranorex into your CI tool!

As you can see, it’s easy to integrate Ranorex test automation in your continuous integration system. Each code change in your application under test and your test automation project will be automatically tested, which enhances transparency and enables you to find bugs faster.

You want to know about the benefits of integrating Ranorex into your development environment? Try it out! Download the full-featured 30-day Ranorex trial and see the benefits for yourself! Have fun integrating!

Download Free Trial

The post Integrate Automated Testing into Any Continuous Integration Process appeared first on Ranorex Blog.

Categories: Companies

Keyword-Driven Test Automation with Ranorex

Thu, 07/14/2016 - 11:15

Multiple releases, limited resources, time pressure and a team with mixed skillsets. And it’s your task to create flexible, maintainable automated tests, which every team member can understand and work with. The solution: get a test automation tool that supports keyword-driven testing.

What is keyword-driven testing?

The keyword-driven testing approach separates the test automation implementation from the test case design. A keyword is defined for each action in the test case. Once the keyword is set, you don’t need any programming knowledge to easily design and maintain the automated tests.

What are the benefits of keyword-driven testing?
  • Tests are easily readable.
    As keyword-driven tests are technology-independent, they’re easily readable for non-technical testers. While technically experienced team members can prepare the automation process and define keywords, you don’t need any technical knowledge to design test cases with these keywords.
  • You can create flexible, easily maintainable tests faster.
    In keyword-driven testing, each action is automated only once and the corresponding keyword can be reused throughout several test cases.
How can I create keyword-driven tests with Ranorex?

There are two ways of creating keyword-driven tests with Ranorex:

1. Keyword-driven framework with automation modules

You can use both your recording and code modules in Ranorex Studio as a basis for keyword-driven testing. Simply split your automation modules and give them each a clearly understandable name. For example, you can define a set of actions, which start the system under test, as a module with the name “StartSUT”. You can find detailed information on how to do so in this user guide section.

Drag keyword from module browser for keyword driven test automation

These modules now function as keywords. Once the keywords are defined, you can drag and drop the keywords needed for your test directly from the module browser into your test suite.

Reuse keywords in multiple projects

Start by creating your keywords directly in a Ranorex test suite module library. You then use these keywords in multiple Ranorex projects by referencing back to this library. You can do so in two different ways:

  • Reference the Ranorex test suite module library. This enables you to still edit the keywords when needed.
  • Reference the DLL file of the Ranorex test suite module library. Please note that this approach doesn’t allow you to modify your keywords.

This approach completely separates the keyword implementation from the test case design and the keyword usage.

Separation in several projects for keyword-driven approach

If you want to learn more about organizing test automation projects, please read this blog post: “Organize a Test Automation Project with Ranorex“.

Use external data in keyword-driven tests

You can make your tests even more flexible by using variables. Variables enable you to automatically retrieve external data, which you’ve saved in an Excel or CVS sheet, in your tests – such as passwords for login actions. You can find detailed information on how to implement this type of testing in our user guide section “Data-Driven Testing“.

2. Keyword-driven testing using the action table

We bet you’re familiar with the good old Excel-spreadsheet. So why not use something you already know well in your automated tests? When using the action table in the Ranorex Recorder, you can create keyword-driven tests in a table-like workspace. It just takes a little trick to access your predefined keywords within this view: Inheritance.

Technically experienced team members can provide code-based keywords in a code module. You find detailed information on how to do so in this user guide section or this blog post.

Keyword Implementation

A recording module, which is inherited from a code module, automatically derives all functionalities from its parent module. This is also true for parameters – you can read more about this topic in the user guide section “User Code Actions and Parameters”.

This can be achieved with inheritance in the recording modules “UserCode.cs” file:

Inheritance From KeywordLibrary Module

Now, you can simply add a user code action in the action table (Add New Action -> User Code) and choose a predefined keyword. Once you’ve defined it, you can set the argument.

Keyword Driven Action Table

You can also use data-driven testing within the recording module by simply making the keyword parameters variable as explained in the user guide section “Data-Driven Testing“.


Keyword-driven test automation is a fantastic way to create flexible test cases. It enables teams with different technical background to work on test automation projects together, while keeping test clearly structured and easily maintainable.

Download Trial

The post Keyword-Driven Test Automation with Ranorex appeared first on Ranorex Blog.

Categories: Companies

Test Automation Day 2016 – Insights

Tue, 07/05/2016 - 12:52

Conferences are always a fantastic way to meet people and exchange ideas with other test automation experts. The Test Automation Day is a major software testing conferences that is dedicated to test automation. This year, it took place in Rotterdam, the Netherlands, on June 23rd. This inspiring conference was packed with test automation experts, software testing professionals and leading IT organizations. Not only did we get to listen to thought-provoking keynotes, but also had interesting talks at our Ranorex booth. Here are some of the most frequently asked questions at our booth:

Is Ranorex just a Capture & Replay tool?

Ranorex is more than a just simple Capture & Replay tool. It is a versatile test automation software that offers a range of tools suitable for every skill level. While you don’t need any programming skills to create and maintain your tests with the Ranorex Recorder, you can also create you automated tests manually.

How can I create my automated tests without using the Ranorex Recorder?

Test automation engineers will especially love the Ranorex Spy. It is a powerful tool that enables you to obtain UI elements from your application under test. Simply open the Ranorex Spy in Ranorex Studio and track the UI elements you want to automate. You can drag these elements directly from the Ranorex Spy into the central Ranorex Object Repository. From there, you can then further drag them either into the action table, or the code editor. Here’s where it gets interesting: usually, UI elements are used more than once in each test case. When adapting an element in the central repository, this change will be true for all occurrences of this element – both in code and in the action table. The benefit? You don’t have to adapt each element manually, which will save you a lot of time. How does Ranorex support the collaboration between developers and domain testers?

The Ranorex Object Repository is the central point of collaboration between developers and domain testers. This central repository is used to manage UI elements. When you record a UI element with the Ranorex Recorder, or track an element with the Ranorex Spy, Ranorex will automatically create a repository element in this central repository. Thus, when changing a repository element in the Ranorex Object Repository, the changes are automatically applied both in the code and the recording module. This does not only ease team collaboration, but also test maintenance.

How does Ranorex support creating and editing test automation projects in code?

If you’re into coding, you’ll benefit from the Microsoft .NET framework and can write code in C# and VB.Net. You’ll also love the new code editor enhancements, which have just been released with our latest major software release: Ranorex 6.0. You can find further information on the new code editor features in this blog post.

Does Ranorex support automated testing of mobile applications?

Ranorex enables automated testing of mobile Android and iOS applications. You can test hybrid, native and mobile web applications. The benefit? You can connect your mobile device to Ranorex Studio using either a USB or Wi-Fi connection. For more information on mobile test automation with Ranorex, please visit our dedicated Ranorex User Guide section.

At the end of this blog post, we just couldn’t resist letting you in on this hilarious incident that occurred at the Test Automation Day this year. Unaware of what was about to happen, we’re busy talking to prospective clients at our Ranorex booth, when a woman came up to us and asked: “May I touch your balls?”. :-) We’ll leave it up to you to imagine the look on our faces!


TAD Rotterdam Ranorex


Download Trial

The post Test Automation Day 2016 – Insights appeared first on Ranorex Blog.

Categories: Companies

7 New Time-Saving Code Editor Features

Tue, 06/28/2016 - 16:40

Writing code is tricky enough. You shouldn’t have to spend hours improving its readability or worry about unnecessary typos causing build errors. Ranorex 6.0 now makes a ton new code editor enhancements available, which will help you quickly write clean and easily maintainable test scripts. Here’re 7 of the most fantastic time-saving features:

1. Code templates

We all love the custom code templates in Ranorex Studio. Using the tab key, you can now access multiple predefined templates, such as the for/for each loop. Icing on the cake for all us coders! 2. Context specific actions

Improve your code structure with these amazing new context specific actions. Simply move newly created classes into specific files, or right click on the edit pencil to check for null or undefined variables. These are just a few examples – give it a try! 3. Refactoring

Wouldn’t it be great if you could replace complex code fragments with small, easily readable methods? The extract method enables you to group your fragments to methods. You can further give them a clear name that explains their purpose. 4. CamelCase search functionality

Find what you’re looking for faster with the CamelCase search functionality! CamelCase identifies the segments of compound words and uses the capital letters to list potential search results.

5. Auto insertion of using

Start saving time when using namespaces! Type in a class using the auto-complete functionality. Ranorex will then automatically add the specific using directive of the needed namespace.

6. Introduction of new methods

And yet another feature that will save you time: When calling an unknown method in code, you can now easily implement it with the context specific action ‘introduce method…’.

7. Switch on enum

This little feature comes in quite handy and enables you to write code faster. When typing a “switch” statement where the condition is an enum the cases are automatically prefilled.


These and many more fantastic features are available with Ranorex 6.0. Update your Ranorex Studio now (yes, it’s free!) and start coding!


Learn more about Ranorex 6.0

The post 7 New Time-Saving Code Editor Features appeared first on Ranorex Blog.

Categories: Companies

Save 30% on Ranorex Runtime Floating Licenses

Tue, 06/21/2016 - 14:24

Don’t miss out on this fantastic offer: Only until June 30, 2016 you can save 30% on Ranorex Runtime Floating Licenses! This offer celebrates our much requested and long awaited feature Ranorex Remote, which is available with our latest major software release Ranorex 6.0.

A Ranorex Runtime Floating License enables you to run tests on additional physical or virtual machines. Now, Ranorex Remote takes remote test execution a step further. Using this new feature, you can:

  • deploy tests to Ranorex Agents for remote test execution directly out of Ranorex Studio with just a few clicks. This makes it easier to simultaneously run multiple automated tests in different test environments and configurations.
  • continue using your local machine during remote test execution, as remote testing won’t block your machine. You’ll receive an automatic notification once the report is ready.
  • share Ranorex Agents with your team.

Remote test execution has never been this easy! All you need is a Ranorex Runtime Floating License to set up a Ranorex Agent and use Ranorex Remote. So don’t just let this offer pass by, and order your Ranorex Runtime Floating License today!

Order a Ranorex Runtime Floating License

The post Save 30% on Ranorex Runtime Floating Licenses appeared first on Ranorex Blog.

Categories: Companies

Speed up Your Test Run by 200% with Ranorex 6.0

Thu, 06/16/2016 - 15:02

You don’t want your automated test to take longer than it has to. Fact is, the debugger directly affects the test execution time. That’s why in Ranorex 6.0 tests run without debugger by default in Ranorex Studio. Simply press the ‘Run’ button – no administrator privileges are required – and start saving time.

We know, only hard facts count. That’s why we’ve conducted a comparison, running a test with and without debugger, so you can see the benefits of the new default setting for yourself.

Up to twice as fast test run in Ranorex 6.0

Test environment and data
We’ve used the Ranorex KeePass sample, one of our sample test solutions delivered with Ranorex Studio, so you can easily reproduce these tests. All test cases were enabled. To omit static delays which could influence the test results, we further activated the Turbo Mode for all recording modules. We ran the tests in two setups. In the first, the computer was in an idle state. As in everyday work life, however, a machine usually has to juggle multiple processes, we simulated a 100% CPU load with a CPU Burn-in in the second setup.

State Debugger enabled Debugger disabled Execution time reduction Idle 2 min 1.9 min 5% 100% CPU Load 11.3 min 5.4 min 52%

The results clearly show that when your computer is in an idle state, the new default settings merely reduce the test execution time by 5%. However, when you’re using your computer to the full capacity, your test will be twice as fast now. These two scenarios represent two extremes, with a realistic CPU usage being somewhere in the middle. One way or another, one thing is clear: this new default setting will definitely save you time. Especially if you’re using an older system, you’ll see significant improvements in execution time.

When to use the debugger

Debugging is important. You just don’t want the debugger to be part of your test execution by default, but use it legitimately, and only when it really does make sense. So when you do need it, you now simply have to press one button to enable the debug mode. Using the debugger, you can set breakpoints directly in the Ranorex code editor to intercept the test run at predefined positions. This allows you to look at specific steps more closely and perform manual interactions. An important note on the side: Please don’t forget that previously set breakpoints will be ignored in the new default run mode.

System specifications
We’ve conducted our tests using a virtual machine setup on a host machine with the following specifications:

Host Machine
Win7 64 Bit
Intel i5-3570 CPU @3.4 GHz (4 Cores)
Samsung EVO 840 SSD
Seagate ST3320620AS HDD
NVidia GT640 2GB

Virtual Machine
VirtualBox 5.0.16 (+ Extention Pack)
Win7 32bit VM – installed on HDD
1 CPU (ICH9; I/O APIC enabled; 100% Execution Cap; PAE/NX enabled; Paravirtualization: default; VT-x + nested paging enabled)
3072 MB RAM
Display: 128 MB memory; 2D + 3D acceleration enabled
AHCI SATA controlled using host I/O cache

Learn more about Ranorex 6.0 Download Free Trial

The post Speed up Your Test Run by 200% with Ranorex 6.0 appeared first on Ranorex Blog.

Categories: Companies

Remote Testing – Make the Most of Your Resources

Tue, 06/14/2016 - 13:20

The idea of automating tests is that you can optimize quality, speed and efficiency in testing. But what good’s that, if you can’t do any work during test execution instead, have to run one test after the other, and there is no fluid workflow when working in teams? We’ve taken test automation to the next level and offer a sublime feature that will save you time and supports a team approach: Ranorex Remote.

How does Ranorex Remote work?

Directly out of Ranorex Studio, you can deploy your tests to Ranorex Agents to execute them remotely. Using a Ranorex Runtime Floating License, you can install a Ranorex Agent on a physical or virtual machine. You can set up multiple agents within a network and configure the test environment according to your needs. This enables you to simultaneously execute multiple tests in various different test environments, in the same time it took to execute a single test before. Your application has to work no matter which technology or operating system your customers are using! Now you can test desktop, web or mobile applications using different operating systems, system configurations, browsers, etc. at the same time – there are no limitations. You can continue using your local machine during remote test execution. Once the test has been executed remotely, you’ll get immediate feedback on the test performance. The report itself is stored on the Ranorex Agent the test has been executed on.

Remote Testing

The ideal tool for working in teams

Just take agile testing, where immediate feedback and team collaboration are key success factors. Ranorex Remote now supports just that with a sublimely fluid workflow. Each team member can send tests to the same Ranorex Agents in a network and has full access to all information on these agents. As an agent can only execute one test at a time, the agent will queue the tests and execute them in order of arrival. Each team member can view the number of tests in the job queue of a specific agent, filter test reports according to test execution time and status, as well as delete or download reports directly from an agent. Thus, everyone in a team is equally informed about remote test execution. Just imagine a test run has failed, and you need immediate help or feedback from one of your colleagues: Simply pass on the information which agent the test has been executed on and when. Directly from the Remote Pad within Ranorex Studio, your colleague can now easily access the Run History of the Ranorex Agent, filter the report, download it locally and continue working with it. As each team member has full access to all remotely executed tests and their reports, it is easy to keep track of the testing progress.

30off Limited offer!

Ranorex Runtime Floating License now 30% off!
Buy now! Valid until June 30, 2016

.lo-left, .lo-right { margin: 10px 20px; float: left; } .lo-wrapper { overflow: hidden; width: 85%; margin: 10px auto; } @media screen and (max-width: 853px){ .lo-left, .lo-right { float: none; text-align: center; } .lo-right p{ text-align: center!important; } }

Think that sounds fantastic? This feature is part of Ranorex 6.0. And as always: all major software updates are included in our maintenance services at no additional costs. Stop wasting time, get a Runtime Floating License and check out our User Guide for detailed instructions on how to set up your Ranorex Agents today!

Ranorex Remote Instructions Limited Runtime License Offer

The post Remote Testing – Make the Most of Your Resources appeared first on Ranorex Blog.

Categories: Companies

Git Integration in Ranorex

Tue, 06/07/2016 - 13:23
Version control your automated tests with Git

Many have requested it, it’s been truly long awaited and finally it’s here: the Ranorex Studio Git integration. Ranorex 6.0 gives you full access to all Git functionalities within Ranorex Studio. Git is the most commonly used open source version control system and plays a major role in many development environments. So far, Ranorex has only supported the centralized version control systems SVN and TFS. Ranorex now responds to the ever increasing demand for a distributed version control system.

Benefits of the Ranorex Git integration

With the release date looming around the corner, it’s always a race of developing and testing new features. If you’re already using Git, you shouldn’t have to invest much needed time and resources to set up an additional version control system. You can now version control your Ranorex projects with Git. Directly from Ranorex Studio, you can commit and push changes to the repository as well as pull them from there. For those of you using Git in the development environment, this update thus not only save you time, but also enhances collaboration between development and testing teams.

This update gives you full access to all Git functionalities within Ranorex Studio, including:

  • Easy branching, merging and switching between branches
  • Working fast and offline
  • Clear file management and access to full file history even when a file has been moved
  • Easy debugging
  • Data assurance

This and more features are available with Ranorex 6.0. And in case you forgot: This major software update is already included in Ranorex software maintenance at no additional costs or hidden fees. Update to Ranorex 6.0 now, check out our Git User Guide section and get started! All there is left for us to say is: Enjoy and have fun testing!

Use Git within Ranorex Download Free 6.0 Trial

The post Git Integration in Ranorex appeared first on Ranorex Blog.

Categories: Companies