One of our users had a
webpage with a form. When it was submitted partially filled, the page
came back (after being processed on the backend) with some errors about
incomplete form. If the user tried to navigate away from this page via a
link (or close the page/browser tab) he was prompted with browser's
standard "Are you sure you want to leave this page?" dialog. He needed a way for Rapise to handle this popup when recording and playing back the web test.
On-premise / self-hosted customers who have Spira installed on older versions of Windows (eg Windows Server 2003) may be using an old version of Internet Information Services 6 (IIS 6). IIS 6 can restrict by default which API verbs it allows throwing a 403.1 error.
It
is a common situation that desktop applications written using Microsoft Windows Presentation Framework (WPF) will have complex layouts including tabs,
splitters and panels having custom grids and tables inside. This article provides help in dealing with such situations, including how to dynamically find items.
Sometimes when testing local/desktop applications you need to access the Windows registry to verify that keys exist or that keys have specific values. For example you may be testing that a DLL was successfully registered. This article provides information on the 'UsingRegistry' sample that comes with Rapise.
When you are using the global Rapise Spreadsheet object on a system running the 64-bit version of MS-Office, you may get an error attaching to the spreadsheet. This article describes the cause of the issue and provides a solution and workaround.
When you have a multi-select list in a web application, you may need to check which items are selected, or to check whether or not a particular item is selected. This article illustrates how to do that.
When you use a DoX command in Rapise to perform a specific command (e.g. DoDOMChildrenCount() to get a number of object's DOM children), in the report an extra step -- assert -- is created during test execution. Sometimes you want to be able to call a function 'quietly' without it affecting the report.
Sometimes when using our SOAP or REST APIs there are constants that are useful for some of the filters. In many cases they are included in the build-in API documentation, but sometimes they are not listed. This article details some of the release/requirement ones that may be useful:
This article describes the process and provides an example for accessing the Spira v4.2 REST API to get a filtered list of test cases in a release.
If you are running Rapise and you suddenly start to find that none of your recordings get saved and the reports are not displaying during execution it may be due to the fact that you have saved your Rapise test folder onto a Network Share.
By default Rapise records user actions with a line commented out for each action. This articles describes how you can disable this behavior if you just want the script lines recorded on their own.
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam 4.x SOAP web services using Java code. It assumes that you've generated the SOAP proxy classes using JAX-WS. If you need to download pre-compiled versions of the classes, they can be downloaded from this knowledge base article.
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam SOAP web services using Java code. It assumes that you've either generated the SOAP proxy classes using JAX-WS or are using the pre-compiled ones attached to this KB article.
When connecting RemoteLaunch to an instance of SpiraTest or SpiraTeam that is externally hosted you may have an issue where RemoteLaunch does not know to use a local proxy server. This articles describes an easy solution to modify RemoteLaunch to use your current Internet Explorer (IE) proxy settings.
When executing Rapise scripts from SpiraTest using RapiseLauncher there is a 10-minute inactivity timeout. If your scripts have periods of inactivity that last longer than 10 minutes, you may need to extend the default timeout. This article describes the steps for doing this.
This article describes the process for calling SpiraTest / SpiraTeam using its SOAP web service API
to query the system to retrieve a list of test cases that match a specific name so that you can obtain its test case id.
When using Rapise to record test scripts against Windows, Java, Flex, or other thick client applications that have windows or objects whose names may change in between test runs, you will usually need to make changes to either the test script or the learned objects so that they can match correctly. This article outlines some suggested techniques for recording/playing back scripts against such applications.