Rapise provides a powerful and flexible test playback engine. It will step through the test script and replay the actions against the application under test. It will pause between the steps to give the application enough time to respond and also retry a step multiple times in case the application is not ready. At the end of the test, Rapise will provide detailed reports and metrics to aid in the remediation of any failures.
When you execute a test in Rapise, there is no need to have the application under test open. Rapise will open the application if necessary before it begins execution of the test.
When Rapise is done executing the test, results will be displayed in a table. The rows with green text are steps that passed; the rows with red text are steps that failed. Any failure can be drilled down to get more specific diagnostics.
Rapise tests can be stored, scheduled and executed from the SpiraTest test management system using the RapiseLauncher add-on for Rapise.
Using RapiseLauncher and SpiraTest you can manage and orchestrate the testing of applications using Rapise automated web, desktop and mobile scripts against a plethora of environments, with the test results reported back in real-time to SpiraTest.
Rapise supports execution of tests from the Windows command-line. This is often useful when you want to run Rapise regression tests as part of an automated build environment and/or continuous integration process. The command line API allows you to pass parameter values to the test script that will set values on global variables used in your Rapise script:
This lets you write a single test that can be used to test with different web browsers or to use different test data for each execution of the test.
You can execute your saved Rapise tests using your choice of DevOps CI tool as another option. For example, you can playback tests using Jenkins CI:
You can also use our integration with Microsoft Azure DevOps (formerly known as Team Foundation Server) to execute Rapise tests seamlessly from Azure:
Object locators are created during Recording/Learning and used during Playback to identify learned objects and simulated objects. You can over-ride the information used to locate your object at runtime so that you can dynamically locate elements that may change depending on the data in the test application.
For the ultimate extensibility, you can extend Rapise with custom locators so that you can customize the testing engine to meet the unique needs of your application.
Questions? email or call us at +1 (202) 558-6885