Rapise Mobile

If you are testing a native mobile application using  SeeTest you have an option to switch to NATIVE_APP_INSTRUMENTED context and record/playback tests in it.

Learn how to query AWS Secret from Rapise.

Requires Rapise 6.7+

If you use Microsoft Defender Antivirus to protect your system then you may need to perform certain steps to use Rapise effectively.

If you use Avast Antivirus to protect your system then you may need to perform certain steps to install and use Rapise.

By default Rapise reports an error when REST service request fails. With the negative test the request should fail, so we want the reporting to behave differently.

It is a 3 step process:

1. SaveAs or Clone the test with a new name

2. Save it to Spira

3. Delete old test copy from Documents module in Spira (optional)

It is possible to use Free Apple Developer account for iOS testing. But it requires some knowledge and time to setup.

Connecting to the mobile devices hosted by SeeTest is easy. Learn how from this article. Requires Rapise 6.5+.

When a test is executed by RapiseLauncher it may access key properties of the test run,  custom test set properties and test case parameters.

Requires Rapise 6.4.19.16+

Automatic screenshots on every test step may occupy too much space. Learn how to make  a screenshot on failure only.

Since version 6.3 Rapise has support for local browser and mobile profiles. Using it you may package browser profiles along with tests. What if you want to reuse browser profiles between different projects? Or have sets of profiles for different situations? You may now set path to profile directory using a special global variable.  Supported in Rapise 6.4+

Learn how to connect to a support session and how to enable Rapise Expert to remotely control your Rapise instance.

To compare images in JavaScript you may use Tester.AssertImage.

Windows may reboot because of various reasons. If you use a machine to run Rapise tests on regular basis than you want Rapise Launcher to be started automatically after system reboot.

The most reliable method that works with any Windows edition is to use Task Scheduler.

Every test has a User.js file and it is a place to put custom code and functions. This code must follow a few rules.

When Rapise starts execution of a test it sets working directory. If a test refers to a file using a relative path then the absolute path is calculated using the working directory.

There are different techniques one can use to close the application being tested from Rapise. The method to choose may depend on the application type.

In this article we describe how to write data to an external Excel spreadsheet during test playback. Both RVL and JavaScript examples are given.

Sometimes object location is unstable. The same object may be identified by different location path or XPath depending on application version or state.

If an object can not be found at playback and it is obvious that object location has changed because of application update (differs from the case when location is dynamic!) then the best way to fix the test is simply relearn the object.

Yes, in general, Rapise can automate most web applications using mobile Safari running on iOS (either on a real or simulated device). However there are some limitations.

We often get asked this question: "We have Rapise and want to automate a native iOS app that is available on the application store", can we do it?

Sometimes when you first install and open Rapise, the Start Page does not display correctly. This article explains the cause and solution to fix the issue.

When Appium installs an application at the beginning of a test session - Android may ask for permissions (e.g. access to media files, camera, etc.). Until such prompt is dismissed - Main activity is not launched. It prevents the test from proceeding.  Learn how to configure the Mobile Profile to automatically grant required permissions on install.

In Mobile Spy of Rapise when switching from NATIVE_APP to WEBVIEW context you may see an error message:

Chrome version must be >= 55.0.2883.0

From this article you will learn how to fix this.

Sometimes when you are using Rapise, you have to use external ActiveX or .NET objects to perform specific actions. You can get Rapise to display intellisense for those objects.

Most complex part in Mobile testing is connecting to a simulator or device. In this article we describe steps necessary to configure the testing environment.

Note: In brackets we specify versions of software components we used at the time of writing this article.

Sometimes it makes sense to automate certain steps of a Manual Test. If you prefer to implement automatic steps in RVL then include the AUTO  helper function into your test.

A test may contain a lot of objects. If you want to locate an object in the object tree you may use the filter box.

Many test automation scenarios require performing same steps with different data. For example, login into application with different user credentials, or enter several lines of a sales order into a table. This is data-driven testing. From this article you will learn how to do this in Rapise Visual Language (RVL) and JavaScript modes.  You will also learn how to define data within a test and in external spreadsheet.

If you don't have some of the standard Window fonts installed (e.g. Courier New), when you try and launch Rapise, it will fail to open correctly. This article provides information on the problem and solution.

You have recorded some basic test scripts in Rapise, and now you want to easily extract the steps into a reusable function that can be called from the main test script. This article explains how you can do this for both RVL and JavaScript based tests.

Sometimes when you are using Rapise, you see an error on the screen, or something doesn't work as expected. In that case, our support team will need a copy of the log file that is likely to contain the error message. This article explains how to get that log file.

When you do UI test automation and create a big enough test coverage the probability of having curtain portion of flaky tests increases. In many cases there is no reasonable way in terms of time and resources to mitigate all flakiness from the test coverage. In some cases even a flaky test may still be useful.

BrowserStack supports automated browser testing via Selenium and Appium on real iOS and Android devices.  Learn how to configure Rapise to connect to Browserstack via Appium.

Sometimes when recording a test against a mobile responsive web site, it is useful to be able to record on the local browser (before playing it back against a cloud service such as SauceLabs, Browserstack, etc.). However you want to always record using a specific browser window size.

BrowserStack enables testing of your website for cross browser compatibility on real browsers. Instant access to multiple desktop and mobile browsers.  Learn how to configure Selenium  profiles in Rapise to enable connection to BrowserStack services.

Requires Rapise 5.3+

Sometimes when you try and install Rapise, you will see the error message "The Pipe is Being Closed", this article provides some solutions for this message.

This article contains of overview of object recognition by UI automation tools in general and its implementation in Rapise in particular.

From this article you will learn how to pass additional parameters to Selenium or Appium target, even if they can not be specified in a profile.  This recipe can be also used to override parameters of a profile right from a test code.

Requires Rapise 5.3+

Sauce Labs allows users to run tests in the cloud on different combinations of browser and OS versions as well as mobile devices and emulators. Learn how to configure Selenium and Mobile profiles in Rapise to enable connection to Sauce Labs services.

Requires Rapise 5.3+

Let's assume you have a cross-browser test which was created on desktop and can be successfully executed on any desktop browser (Chrome, Firefox, Internet Explorer, Safari). You want to execute this test on your mobile devices or emulators. Learn how from this article.

Requires Rapise 5.3+

Appium requires certain version of Chrome to work with. Even Android 7.0 is shipped with Chrome 51 and this is too old version. From this article you will learn how to upgrade Chrome on your Android emulator.

Rapise connects to mobile devices (iOS and Android) using the standard Appium mobile device testing API (similar to Selenium WebDriver for web browsers). This articles describes how you can use Rapise to connect to a mobile device farm using the Appium mobile device profiles inside Rapise. We use Kobiton as an example.

We often get requests for ways to slow down the playback speed of Rapise so that the application under test (AUT) has time to respond. This article describes the different ways and provides suggestions as to when you should use each one.

One of the most popular programming languages in the world is JavaScript. Initially conceived by Netscape as a web page scripting language, christened JavaScript to leverage the popularity of Java (which was fairly new and sexy at the time) and now used for servers (NodeJS), desktop apps (ReactNative) and for us at Inflectra, the core technology at the heart of our Rapise test automation system. This article provides some useful resources for those first learning the language.

If you receive the following error message when performing Mobile device testing with Rapise, this article provides the necessary solution:

Method not found:
'OpenQA.Selenium.RemoteCommandInfoRepository
OpenQA.Selenium.RemoteCommandInfoRepository.get_Instance()'.
 

One of the challenges using an automated testing tool is to organize things in a way that it is logical enough to find something quickly, structured enough to avoid duplication and simple enough to maintain and upgrade.

This statement is also true for Rapise objects. A common requirement is to deal with the same objects within a flow of different test cases. For instance, if an application has “Log In” functionality then many, many tests will require logging-in and logging-out. Each test will have this object in its own object tree. However this causes trouble if a change in the application affects the recognition of the Log In object. All of the test cases will need to be updated. In such situations it is much more convenient to have the “Log In” objects placed into their own file and re-used by other tests.

The most commonly used synchronization option to make Rapise wait until the application under test (AUT) is ready is the Global.DoSleep action. However having just a sleep may cause an unnecessary delay because we have to consider the maximum wait interval and it may be much less on average. Rapise includes some additional synchronization options for more fine grained control of the test case flow.

The Tester.EndTest() function in Rapise is described as: Marks end of a currently executed test. Calculates test results and performs finalization of test execution. We have found that some of our customers have been confused as what the purpose of this function is.

By default, the reports displayed within Rapise report back each test activity and assert statement as a line in the report with all of the activities and events being displayed in a single flat list regardless of whether they happen inside the main Test() function or a sub-function. This articles explains how you can extend the reporting.

The context menu control is not natively supported by Rapise, but one can use a simple workaround.