In most cases "Auto" is the best choice. Manual selection of libraries may be needed in more advanced scenarios and is intended for experienced users.
If you are trying to run a test case or test set and you receive the following error:
Database constraint violation occurred [APPLICATION.Business.EntityConstraintViolationException]
An error occurred while updating the entries. See the inner exception for details. [System.Data.UpdateException]
Violation of PRIMARY KEY constraint 'XPKTST_ARTIFACT_CUSTOM_PROPERTY'. Cannot insert duplicate key in object 'dbo.TST_ARTIFACT_CUSTOM_PROPERTY'.
The statement has been terminated. [System.Data.SqlClient.SqlException]
Then this article provides the solution for you.
SpiraTeam has been designed to work with a variety of different software development methodologies, including several different flavors of agile, waterfall and hybrid. This articles describes one of the more popular waterfall methods called the V-Model and gives best practices for how to use SpiraTeam on such projects.
Outstanding support is the foundation of our company, and we want your experience with our products to be exceptional from the start. We dedicate more than half our technical resources to support, and we make support a priority over all other work.
To ensure your satisfaction, we provide one year of product support FREE with every on-premise software purchase and unlimited support with every cloud subscription, which guarantees you access to our knowledge base, helpdesk and phone support.
- When new recording is started Rapise always opens new IE window
- Spy does not show DOM tree
- During playback no object is found
In the standard reports that come with SpiraTeam, we have the 'Detailed' reports that are designed to include a primary artifact (e.g. requirements) and then include tables that display lists of related items (e.g. Tasks, Incidents, etc.). By default, we only show some of the fields in these tables. This article explains how to display the value of specific custom fields in the tables when you customize the standard reports.
We have found an occasional situation where Rapise is not able to click on hyperlinks (<A> tags) when you playback a test on IE. The same test works fine on other computers and on other browsers on the same computer.
We had a customer with a problem related to having <div> elements with complex display styles applied inside an HTML anchor tag <a>. The anchor tag was reporting back as having zero size (0px) in IE, so when Rapise tried to locate it to click on it, the browser was not able to find it.
When you are testing a web application that has popup windows (where the popup is a whole new browser window) you will need to make a slight change to the test script to enable it to playback successfully in Internet Explorer (no change is needed for Chrome or Firefox).
When recording or playing back a test script on a new PC you may get an
error message that Rapise cannot find the path to "AllLibraries.json".This article provides instructions on how to fix the issue.
A couple of our customers have run into a situation where the new font-based glyph icons that we're using in Spira 5.0 don't display. This is usually due to a configuration issue within IE itself, this article provides the recommended solution.
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.1 includes the ability to write custom reports against various reportable entities. This article provides a list of the available entities:
Sometimes when you record a test script using IE and then play it back, some of the clicks on hyperlinks will not playback correctly. Rapise will list them as Passed, but the click won't actually be performed.
Suppose we have a situation that a thick-client (desktop) application under test (AUT) is based on a technology
that is too old or not completely supported by Rapise. Rapise has a number of
libraries for different types of apps. Usually Rapise finds the correct libraries using its auto-detection, but sometimes an application is unusual and
the auto-detection fails.
During the course of investigating a technical support issue for SpiraTest, SpiraPlan, SpiraTeam or KronoDesk , the need may arise to run a query against your Microsoft
SQL database. To do so, you will use Microsoft SQL Server Management
Studio. If you did not install this when you installed SQL, you can
install it from the original source.
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.
Ask the user to clear out their browser's cache of cookies and stored internet pages/content. After they do this and then close and reopen their browser, the issue should be resolved.
An old (December 9th, 2014) security update for Microsoft Windows and Internet Explorer (KB3025390) broke the support in IE for 'out-of-process' code execution. This effectively prevented an automated testing application such as Rapise from automating Internet Explorer (IE) applications. This was subsequently fixed by Microsoft on February 10th, 2015 with the KB 3021952 update.
If you face performance issues with Spira or KronoDesk when the users use Internet Explorer 9.0, there is a known issue in ASP.NET 4.5 that can cause the client to disconnect and all subsequent AJAX calls do not get processed. This article describes the symptoms and the solution.
When you use our SOAP or REST web service APIs
you will often times want to retrieve a filtered list of data. This is done by using the RemoteFilter that
lets you query the list of requirements, test cases, tasks, incidents, etc. and pass in the field to be filtered. This article includes the list of standard fields that you can use in the RemoteFilter.
The custom reporting functionality in SpiraTest, SpiraPlan and SpiraTeam v4.1 (or later) includes the ability to write complex reports, joining various tables, using SQL aggregation (COUNT, SUM, etc.) functions and other advanced reporting features. A common needs is to display a list of artifacts (requirements, test cases, etc.) and join against the custom property definitions so that you get the custom fields displayed with the names of the value not just the IDs. This articles explains how to do this.
Sometimes when you are running Rapise tests you need to run direct database queries to prepare the data in the test application, or you need to make queries against the database to verify that some user interactions left the data in a specific state.
The sample script below illustrates how you can call database queries directly from the Rapise scripting editor:
This article describes how to playback a test in a different browser from the one it was recorded in.
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.0 includes the ability to write custom reports against various reportable entities. This articles provides a list of the available entities:
It is often useful to have a common set of code libraries and objects that can be reused amongst multiple tests. With Rapise this can be done by creating a common test and then including it into the other actual tests. This article describes the process
In SpiraTest, when you create a new custom property in the incidents section, they are disabled by default. Unlike other parts of the system, the incident tracker has a customizable workflow. This article describes the steps necessary to enable the new custom properties in the workflow (which will make the custom property enabled).
If you try and record a test script in Rapise using just the 'Infragistics' library you will get the following error message:
C:\Program Files (x86)\Inflectra\Rapise\Engine\Recorder.js(285, 3) Microsoft JScript runtime error: 'ManagedObjectSelectableBehavior_OnMouseEvent' is undefined