Rapise's cross-browser capabilities are world-class with support for multiple versions of Microsoft Internet Explorer, Mozilla Firefox and Google Chrome. Choose Rapise to test web applications in all of the most used browsers. Create one test script and execute the same script without modification across the major browsers.
When developing and testing a web application you naturally need to test it with different web browsers and of course (based on bitter experience) multiple version of each web browser.
With Rapise you can record a test script using one browser and then play it back using Mozilla Firefox, Google Chrome, Apple Safari, Internet Explorer, Microsoft Edge, and Opera:
Rapise supports cross-browser testing. It uses the web browser Document Object Model (DOM) to interact with the current web page. The browser DOM is standardized by the W3C.
The various web browsers on the market have various differences in DOM implementation. In many cases these differences are not significant. But sometimes they require special handling. Rapise has an abstraction layer in place to overcome these differences and make the recorded scripts as universal as possible, reducing the work of the testers.
With Rapise, you can run your recording in a different browser than the one in which it was recorded simply by changing the specified browser in the playback settings:
In addition, it is possible to have more control over the cross browser execution using the available APIs and configuration variables. You can also run the recording in multiple browsers in succession using either a Rapise sub-test or simply executing the test from our SpiraTest test management system and passing through different parameter values.
Rapise has an integrated Web DOM Browser (called the Web Spy) that lets you inspect the objects in a web page and Learn them for testing. This is useful in cases where you have more complex applications to test and you need to pick specific objects.
For the ultimate in power and flexibility, Rapise has an XPATH and CSS selector engine that lets you try our different XPATH and/or CSS queries and see which objects are matched. You can then “Learn” the successful queries as new objects that can be used in your test scripts.
This allows you to have your web developers create the testing objects that your QA team can then use for testing against. This makes the interface between testing and development more natural and efficient.
Web applications can be singularly hard to test because of the wide variety of standards and frameworks used to created pages. Each web application is unique in terms of assigning attributes to elements and this complicates the process of generating XPath locators.
Some applications assign dynamic IDs to elements, some use ARIA attributes and some use neither. Sometimes the values of the class attribute have meaning related to the element position and sometimes it is just used for styling. There are also cases when an application contains hidden DOM layers which stack on top of each other.
So, using the same methodology for generating XPath locations for all applications is not efficient and will lead to unreliable “flaky tests” that break after each application reload or slight UI modifications.
To cope with these problems Rapise introduces the concept of the Web Application Profile. It is a simple JSON file of a defined structure that instructs Rapise how to build XPath for elements in a particular application. This lets Rapise understand each application and create reliable tests the first time.
With Rapise natively you can record a test script using one browser and then play it back using Mozilla Firefox, Google Chrome or Microsoft Internet Explorer.
In addition, you can use Rapise with the open-source Selenium WebDriver framework to play back the same tests against other browsers such as Apple Safari, Microsoft Edge and Opera (as well as IE, Firefox and Chome). You can also use Rapise to write native Selenium code for cases where you want to use existing Selenium WebDriver logic.