Recommended approach is to use SpiraTest and RapiseLauncher designed for this task. In some cases it is not an option and we need to execute a test directly.
In order to synchronize SpiraTest, SpiraTeam, or SpiraPlan with Microsoft Azure DevOps (ADO) formerly known as Microsoft Team Foundation Services (TFS) you may need the IDs of the Areas inside ADO. This article describes how you can get this from cloud instances of ADO where you do not have access to the database.
We have been asked several times by customers - how do they migrate an existing Git repository to TaraVault (either self-hosted or hosted by another provider)? This article explains the process.
Sometimes when you use Spira or KronoDesk and perform actions (e.g. assigning bugs, test cases, etc.) email notifications are not received correctly. This article provides some common reasons and solutions
This document contains an overview of how to setup and configure SpiraTest, SpiraTeam or SpiraPlan in a load balanced web farm scenario. It contains links to additional information from Microsoft, and community resources related to the scenario.
Sometimes when you have very large pages of data in the administration screens inside Spira you may receive an error due to exceeding the default number of allowed form elements posting back data. This article provides a fixed for the issue.
Sometimes you will want to get an idea how fast your manual and automated tests are taking. You can use the custom graphing feature to create a custom graph for this.
This article describes some basic troubleshooting steps that you should take when the data-synchronization service between SpiraTest and another bug tracker (in this example Jira, but it could be Bugzilla, Axosoft, Microsoft TFS, etc.) does not appear to work correctly.
By default, when you want to use Rapise to record and playback web tests using either Chrome or Firefox, you simply go to the appropriate web browser "store" and install the extension directly from the store. However sometimes you are testing web applications on a machine with no Internet Connectivity.
It is common to use UI tests with RDP connected to remote VM. By default this works only while RDP window is open and client is connected. On disconnect remote session gets locked and UI becomes unavailable for the test. This topic covers a workaround.
Normally you can install the add-ons for Chrome and Firefox directly from the browser's app store (just search for Rapise). This is the easiest option, and avoids the need to run the browsers in developer mode.
Rapise 6.3 includes an experimental feature - new UIAutomation2 locator for UIAutomation based desktop testing. Rather than specifying a path from the element tree root to the element this locator relies on built-in ability of UIAutomation to search for elements based on property values.
When you are integrating Spira with Jira cloud (hosted by Atlassian) and Jira server (locally hosted) you need to to connect to Jira using a login and Jira API Key. Previously (prior to June 3rd, 2019) you could also use a Jira login and password, that is no longer allowed by Atlassian.
SpiraTeam is designed to work on both 32-bit and 64-bit systems, taking advantage of the extra memory and power available if you have a 64-bit operating system. However Microsoft's Team Foundation Server (TFS) - part of Visual Studio Team System (VSTS) - only runs in 32-bit mode. Therefore when using our integration there are a couple of steps you need to perform.
When using Spira or KronoDesk on a separate web and database server, the easiest configuration is to use SQL Server authentication to connect between the web server and database. However that means hard coding a password in the web server (in the Web.config file). So in this article we explain how to use Windows Integrated Authentication instead.
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 had a customer ask us what was the recommended way to enter mathematical equations into a requirement in Spira. There are a couple of options depending on several factors:
- You want to do it 100% natively in Spira, vs. using an external tool with Spira
- How complex the equation is
- Does the equation need to be editable after the fact
As you move your web applications (such as SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk) to newer encryption protocols such as Transport Layer Security (TLS) 1.2, you will need to make sure the client applications are configured to use the latest version of TLS. Specifically applications using Microsoft .NET may not use the latest version by default.
When you use the Perforce Provider for Spira you may sometimes run into a Windows folder permission error. This is due to the Perforce API running as a specific user that does not have access to the Windows temporary profile storage area.
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
A customer recently asked us for some diagrams that illustrate the logical system and application architectures for use in their documentation of the system. We thought these diagrams might be useful for our other customers.
When you are running the import from HP / MicroFocus ALM into Spira, you sometimes come across error messages that look like the following:
Error "The field <RQ_USER_17> cannot be used with requirement type <Non Functional>"
When you integrate Spira with Microsoft Azure DevOps (formerly known as Team Foundation Server or TFS) you have the option of matching up the custom properties in Spira with the user defined fields in Azure DevOps. This guide explains how you get the 'system names' for custom vs. standard fields.
The latest version of SpiraTeam and SpiraPlan (v6.5.2) has support for creating and managing project baselines. In this initial release there are no standard reports built into the system for viewing baselines and the changes that have occurred. This article we provide some custom reports you can use until the next version is released.
When you have a rich text box in a web application, the process for recording a test and playing it back will be different to a standard HTML plain text box. This is because the browser actually uses a separate IFRAME and HTML document for the editable rich text box. This article explains the process for recording/playing back such a test.
A customer asked us why Rapise uses Pascal Case names for the various operations, functions and properties, as well as the reason why operations are prefixed with a "Do" action name.
If you are integrating Spira (SpiraTest, SpiraTeam, or SpiraPlan) with Atlassian Jira, you may get this error message if you have not updated the integration for a while:
Basic auth with password is not allowed on this instance
A customer recently had some questions about what synchronizes between Spira and Jira, so we thought that this article would help clarify things.
Sometimes the goal is to find specific image on the screen. It may be special symbol, map pointer or an icon. This topic contains ImageFinder and sample test demonstrating its capabilities.
One of the features of the Spira synchronization service for Atlassian Jira is that it automatically adds relevant links to the user story and issue pages in Jira to make it easier to navigate from Jira back to SpiraTest, SpiraTeam, or SpiraPlan. Some users have reported these links are no longer visible.
There are situations when object location attribute depends on the object data and it is not possible to record/learn all such objects in advance. In this case it may be convenient to calculate object location at playback time using FormatString and SetLocatorOpts actions of the RVL global object.
Of the unique needs of a requirements and test management system when working in the Defense industry, specifically when designing, building, and testing mission systems, is the ability to link individual test steps to the requirements. This article provides you with a custom report to use to display such a traceability matrix.
A workflow is a predefined sequence of incident statuses linked together by “workflow transitions”. Incident statuses and workflow transitions are highly configurable. This article gives an overview of workflow transitions.
There are many different ways of passing test parameters to Rapise from an external system. This guide describes the different ways of passing parameter values to Rapise.
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+
This articles describes how you can use the Navigator.CheckObjectExists(...) action to see if an element exists on a web page and how it differs from the Global.DoWaitFor / DoWaitForProperty actions that are described in another article.
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.
We have had some questions asked about the TestRail migration tool. This KB provides some additional information about what is migrated and how the artifacts relate between SpiraTest and TestRail.
UI Automation is a default technology for testing desktop applications on Windows. If your application is not .NET or Java then Rapise will turn on UI Automation library during recording. If some elements in your application are not recognized or there are issues with playback of recorded steps then most likely your application is using custom UI controls. You may inspect those controls and send information to Rapise support team to get recommendations on how to proceed with testing.
Sometimes it is necessary to move a SpiraTeam, SpiraTest, SpiraPlan, or KronoDesk installation to another server, without wanting to lose all of your data. This KB will guide you through the steps of transferring the install over, and optionally upgrading the application. This guide will walk you through the recommended steps when needing to move both the application and database to new servers.
Sometimes, when you try to create a new release, a error message says that "You need to choose a Version Number that's not already been used." But you cannot find a release with that version number.
This article is for those who test a desktop application via UI Automation library. Since desktop applications are frequently built using UI controls from different vendors and the number of such controls available on the market is pretty big (> 1k) - Rapise may not have out-of-the-box support for some controls in your application. For such cases Rapise offers a low level API to navigate UI Automation tree of elements inside an application and read/write element properties. In this tutorial we'll show how to use this API and quickly add minimal support for a custom control.
If a test needs to verify existence or absence of a specific option in a dropdown you can do it via a simple function presented below.
Sometimes customers want to download their list of tickets and file attachments. This article explains how to read the data that we provide.
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.
You can use the Spira Project Backup & Migration Tool to move projects between one instance of SpiraTest and another pretty easily. However there is a known issue that can sometimes occur if you have deleted custom properties.
One of the benefits of using Inflectra software is that you get unlimited upgrades for the first year and as long as you maintain an active service plan. This articles describes the process for upgrading your installation of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk to the latest version. It also answers many common questions about the process.
Many of our customers are using SpiraTest / SpiraTeam with their own in-house test automation framework. In this article we explain how you can use our REST API and/or our sample jUnit code to integrate your own framework easily with Spira.
If you have disabled TLS 1.0 and 1.1 encryption protocols on your IIS web server, you may run into issues accessing the web interface of Spira or KronoDesk from older versions of Windows and/or IE.
If you install Rapise on non-vanilla system, e.g. old workstation with a lot of other software, especially with anti-virus and development tools, it may end-up in a state when some components are not registered successfully and some files are blocked. In this article we describe symptoms and ways to cure.
When SpiraTeam or SpiraPlan is connecting to a Subversion (SVN) repository running on Windows Server, sometimes the Windows server will not close connections fast enough, causing the cache build to fail.
This post shows you how you can migrate or downgrade a SQL Server database from one version to a lower or earlier one. E.g. 2016 to 2014, 2014 to 2012, 2012 to 2008 etc. This can be useful if you maintain a heterogeneous environment of SQL Server instances and you have a backup from a newer version that needs to be hosted onto an older version. This happens to us quite a bit when customers installed a trial on SQL Server Express (latest version) and we need to host it on one our cloud servers.
By design Rapise tries to record user activity on the highest possible level. This makes recorded actions more readable and universal. However that sometimes means that certain actions that a user performs won't be automatically picked up. This guide explains ways to handle situations when a specific user activity is not recorded.
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.
When trying to install the Add-In SpiraTeam Explorer for Visual Studio for VS2017, the install may fail, or prevent installation due to an error.
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.
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.
When you integrate SpiraTeam or SpiraPlan installed on-premise with an external Git source code repository, Spira has to maintain a copy of the Git repository locally. Sometimes you need to refresh this Git repo manually if an update did not complete. This article explains the process
This article explains the process for making a backup image of your "on-premise" SpiraTeam (or SpiraTest, SpiraPlan) instance and preparing it so that it can be sent to Inflectra to host on our cloud environment. This can happen when you have been using SpiraTeam on-premise, but now want to migrate to the cloud.
When you use SpiraTest with GitLab, the synchronization plugin synchronizes some fields unidirectionally and other fields bidirectionally. To clarify the details, this article illustrates which fields are synched and in which directions.
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?
Customers running Spira v5.0 or v5.1 may experience an issue where the system will let you create test case folders that point to one of their children as parent. This causes an infinite loop which will break the system. This article provides a solution to fix the issue (though we recommend upgrading to v5.4 to prevent it happening in the future).
When you are integrating TestComplete (from SmartBear) with SpiraTest and RemoteLaunch, you need to map the test case in SpiraTest to the matching test script in TestComplete. This article provides more details.
Rapise is evolving product and we release new versions of it from time to time. If you plan to upgrade your copy of Rapise follow these simple steps.
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.
Sometimes customers will contact us regarding questions as to why the execution status indicator of their test sets is not being updated (i.e. everything still looks as not run) even after running some of the test cases. This article explains why this might be the case and provides solutions.
We provide the source code for a number of the data sync solutions we provide (eg Jira). This gives customers the ability to tweak the precise behavior of the sync to their specific business needs. The open source code does not run in isolation and this article explains how to make sure you have everything you need to build and test your custom code.
When you are first using the SpiraTeam plugin for JetBrains TeamCity, you may run into the issue where the settings for TeamCity are not being saved correctly.
We sometimes get contacted by customers that are not sure about the two ways that RemoteLaunch can be used - in normal scheduled polling mode, and when you immediately execute a test set from the SpiraTest UI. This articles explains the two modes in more detail.
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 of the artifacts in Spira are "soft deleted", i.e. they are simply marked with a deleted flag, and can be recovered easily by a project administrator using the Project History Changes option to review the changes, filter by deletes and revert the change. However when a system administrator deletes a whole project, it physically deletes the project and cannot be undone.
Robotic Process Automation (RPA) is well suited for processes that are clearly defined, repeatable and rules based. With Rapise you can create software robots that can do boring repetitive tasks and free employee time for more creative work.
Below you will find a brief description of RPA tasks that Rapise can do.
Sometimes using Rapise you need to access files on the Windows filesystem, either for testing purposes, or to object test data stored in a flat CSV, TSV or text file. This sample illustrates how you can access the File System using Rapise and the Windows FileSystemObject (http://msdn.microsoft.com/en-us/library/aa242706(v=vs.60).aspx).
The steps to perform when needing to move the database to another SQl Server, or when changing the DNS name of your SQL Server.
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.
When using SpiraPlan, SpiraTest or SpiraTeam with Microsoft Visual Studio Online instead of a local installation of Microsoft Team Foundation Server there are a couple of differences in the integration configuration that you will want to be aware of. This article describes those differences.
Customers sometimes contact us with questions about how the Releases and Iterations in Spira work, specifically what kinds of data (test status, task progress, etc.) roll up from an iteration to a minor release, and from a minor release to a major release. Also they want to know whether iterations are included when you filter by release. This article provides some clarifications.
This article is kindly provided by one of our customers - Boris - who has been using the Desktop Data Sync and JIRA to integrate his on-premise JIRA instance with a cloud instance of SpiraTeam.
When you have a user defined function in Rapise, you sometimes want to jump to it.
If you are using SpiraTeam and SpiraPlan on-premise, and are looking at our TaraVault cloud-hosted code management service, this article explains what TaraVault is, and how you can have the same functionality on Premise.
This article describes the steps in integrating a hosted instance of SpiraTest, SpiraPlan or SpiraTeam with Atlassian's JIRA On-Demand (hosted). We recommend using our cloud hosted data synchronization service that means you don't need any special tools or downloads to use both products together. Let us do the work for you!
If you want to migrate your TaraVault Subversion repositories from Subversion (SVN) to Git, to take advanced of the superior merging and branching functionality, as well enabling your teams to work in a distributed manner, this KB article explains the steps to perform the migration, whilst keeping your commit history and branches.
By default, all projects are completely self-contained; artifacts in one project can only be linked or associated with artifacts in the same project. However, there is a way for the project admin to selectively allow other projects to access artifacts in the current project. (Administration -> Project Associations)
The cross-project functionality is being introduced gradually. As of Spira version 5.4, it applies only to requirements, test cases, and incidents.
This article explains how and where the artifacts from another project can be used.
Sometimes it is required to have list of files from some folder. Here we demonstrate how to get this list and how to iterate through it in RVL.
The incidents in Spira are able to have customizable incident types, statuses, priorities and severities. This means that each project has unique IDs for the various attributes. Sometimes when you incorrectly load in data using our Excel Add-In, you can link incidents to attributes from other projects. This article describes the problem and the solution.
We show how to do data generation for test scenario using RVL Variable loop in Rapise. This sample shows how to produce a sequence of filenames: FILE1.txt, FILE2.txt, FILE3.txt and so on.
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.
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.
Some of our customers wanted to know that we delete the data in the SpiraTest, SpiraPlan, and SpiraTeam tables when we delete a project. This article outlines the approximate order in Spira v18.104.22.168.
Sometimes you want to test a process which requires a handoff between departments and would involve different testers to complete the full range of functionality. This article describes how to set that up, using a test set.
In some cases it is convenient to store tests in the same Git repository where source code of an application under test is located. For example, if you are using Visual Studio Team Services. From this article you will learn how to execute Rapise tests stored in a Git repository with SpiraTeam and leverage the power of SpiraTeam reporting and analysis features.
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+
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+
During the evaluation of Rapise 5.2 for Microsoft Dynamics AX testing, a customer collected the following tips and tricks from our support team (thanks Maxime!).
Rapise is a test automation platform for desktop, web and mobile applications. It is designed for building automated and manual end-to-end UI tests and fits any TestOps infrastructure.
Elasticsearch is a distributed, RESTful search and analytics engine capable of solving a growing number of use cases. As the heart of the Elastic Stack, it centrally stores your data so you can discover the expected and uncover the unexpected.
From this article you will learn how to integrate Rapise and Elasticsearch together.
Jasmine is a behavior-driven development framework. If you want to test UI with Rapise in a behavior-driven way learn how to tie Rapise and Jasmine together.
This article explains the process for taking a SpiraTeam (or SpiraTest, SpiraPlan) backup image from Inflectra's cloud servers and installing it on a local "on-premise" instance of SpiraTeam. This can happen when you have been using SpiraTeam in the cloud, but now want to host it locally.
Anti-virus software is very sensitive to test automation tools. This is normal, because test automation tools usually do API, keyboard and mouse hooking to be able to record and playback user actions.
One of the limitations in SpiraTest and SpiraTeam v4.x was that for performance reasons we could not handle test sets with very large numbers of test cases and that the system was not able to display the counts of the test cases and the execution status for test set folders.
The plugins listed on our website for integrating with JIRA are compatible with the latest major version (5.0 at time of writing) of SpiraTest, SpiraPlan or SpiraTeam. This article provides older versions of the JIRA data-synchronization plugin for customers that are using older versions of Spira.
This article enumerates the different skills you need to be self-certified at the training course: Rapise iRP-100 fundamentals. The article includes the list of skills in a readable format as well as a downloadable spreadsheet that you can fill out.
This article enumerates the different skills you need to be self-certified at the training course: KronoDesk iKD-100 fundamentals. The article includes the list of skills in a readable format as well as a downloadable spreadsheet that you can fill out.
This article enumerates the different skills you need to be self-certified at the training course: Spira iSP-100 fundamentals. The article includes the list of skills in a readable format as well as a downloadable spreadsheet that you can fill out.
This article contains a sample spreadsheet that describes each of the course modules for being trained on our products:
Please download the spreadsheet and use to help self-certify your skills and competency with our products.
Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:
Could not load file or assembly 'WebDriver, Version=22.214.171.124,
Culture=neutral, PublicKeyToken=null' or one of its dependencies. The
system cannot find the file specified.
The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.
Sometimes when running the SpiraTeam v4.1 installer to upgrade from an older version of SpiraTeam (same also applies to SpiraTest and SpiraPlan)
you will get the error message:
You must install the Microsoft .NET Framework 4.0.30319
even though .NET 4.0, 4.5 or 4.5.1 is installed.
We have many different plugins available for different bug-tracking tools (see https://www.inflectra.com/SpiraTeam/Downloads.aspx
) however there may be cases where you need to integrate SpiraTest, SpiraPlan or SpiraTeam with a bug-tracker we do not currently support. This article explains the process for writing such a plugin.
When running Spira or KronoDesk on certain versions of Windows, when using the Czech or Slovak culture settings (or using Server default when Windows is installed in those languages) you may get unusual formatted dates.
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.
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.
In the KB62 article - Accessing Files using Rapise
we explain how to access the names, versions and locations of files on the Windows file system. One customer asked - can we verify any file details other than version. This article provides sample code for accessing other information.
Since TaraVault is an add-on feature to either SpiraPlan or SpiraTeam (hereafter just 'Spira') you use the Spira web interface to handle the provisioning of new TaraVault projects. This articles explains the steps.
Inflectra can automatically upload your Subversion repository from
your current self-managed copy or from another provider. We accept
Subversion dump files (as produced by the "svnadmin dump" command)
either uncompressed or compressed as ZIP, GZIP, or BZip2.
Sometimes when you are using the SpiraTeam Importer for IBM Rational DOORS, you will get a DXL Runtime Error. This article explains the cause and provides the appropriate solution.
TaraVault allows you to create as many projects as you like. Each project has its own source code repository
(Subversion or Git) and its own linked Spira project. Therefore, each project has its
own source code URLs for the relevant repository type.
When testing web applications you will often need to use XPath to query the browser DOM for elements based on the scenario under test. This guide explains how you can use XPath queries with Rapise to make your browser testing more flexible and adaptive to changes on the screen.
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.
This articles describes the steps to create a custom report that displays a table of test cases with the following fields:
- Test Case ID
- Test Case Name
- Last Execution Date
- Last Execution Status
- Number of Test Runs
This is a common need, since you may have installed SpiraTest, SpiraPlan, SpiraTeam, or KronoDesk on a workstation to evaluate its capabilities and now need to install it on a production server for real use, but you don't want to lose all your existing data.
Our web-based products: SpiraTest, SpiraPlan, SpiraTeam and KronoDesk make use of the Microsoft IIS web-server and Microsoft SQL Server database platforms.
This KB article explains some of the more common error messages that can occur after installing one of our products and the steps to remedy them.
This article was written specifically for versions v3.0 - v4.2 of Spira and versions v1.x of KronoDesk.
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. However due to the way REST web service tests are stored, there are some slight changes needed to handle REST services. This articles describes the process.
When testing Silverlight applications, you may find that Rapise fails to recognize the objects in the Silverlight app using the UIAutomation library. When using the Rapise Spy Tool, the whole app is identified as a single window. The objects such as a dropdown, buttons etc. inside the silverlight app are not individually recognized.
It is common for test scenarios to share similar pieces of functionality. A good example of such sharing is login logic. This guide outlines ways in which you can share such logic to avoid having repeated code in your tests.
By design Rapise tries to record user activity on the highest
possible level. This makes recorded actions more readable and universal (often several lower-level user actions are combined)
Rapise uses a heuristics to
distinguish meaningful activity from low level actions. In some cases
this leads to a result that some user activity is not automatically
recorded (for example, a mouse click before entering text in a box).
There is a broad range of available UI platforms and libraries.
The variety of graphical widgets makes user interface robust and
beautiful. Rapise tries to recognize as much objects as possible.
However this range is growing and there are always widgets that are not
We need to call many common functions from a common library frequently.
A Flex application requires some instrumentation to be ready for testing.
By default Flash player has security restrictions preventing Rapise from accessing the application contents.
Please, check the this help topic to learn more about Adobe Flex testing.
Sometimes it is necessary to examine the state of an object. For example, determine if Toggle Button is pressed or not, Radio/Check Button is checked or not, etc. This guide describes a couple of different ways of achieving this.
Rapise has built-in
We are planning on adding the ability to email the entire user list of the system and/or the membership of a specific project through the Spira UI, but for now this article explains how you can use a custom report to get a list of all the email addresses of the users of a Spira installation:
If you ever see the following message in the Application Event Logs on your SQL Server database server:
SQL Server has encountered X occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [Path to either your database's MDF or LDF files]
It can often mean that the Size/Shrink settings for the database files are not correct for the size of database. This articles suggestions some techniques for fixing this error message.
Sometimes when installing our products
you get error messages during the installation and it's necessary to provide Inflectra support personnel with detailed trace/logging information so that they can better support you. This article describes the steps necessary to enable Windows Installer (.msi) trace logging.
Sometimes when you install Rapise on a computer that had a previous version of Rapise installed, when you try to record and/or playback a test you get the following error message:
C:\Program Files (x86)\Inflectra\Rapise\Engine\Player.js WScript.CreateObject: Could not connect object.
This article describes the steps to correct the error.
If you are running Spira v4.1 and you have the situation where you cannot create requirements or use case steps, please read this article for instructions on how to fix the issue.
After upgrading from v3.2 to v4.0 you may receive this error message when you access the Reports home page on certain projects:
Cannot deserialize the blob of personalization data associated with the current page.
Parameter name: data [System.ArgumentException]
The serialized data is invalid. [System.ArgumentException]
Value cannot be null.
Parameter name: enumType [System.ArgumentNullException]
This article describes the solution to fix this issue.
If you ever receive the following error message:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: nlssorting.dll, version: 4.0.30319.1, time stamp: 0x4ba21c2f
Exception code: 0xc00000fd
Fault offset: 0x0000000000001ef9
Faulting process id: 0x1208
Faulting application start time: 0x01ce67177b5b877f
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
Report Id: 5ef990e5-d30e-11e2-863b-005056b1010f
Sometimes you will have controls in a WPF or Silverlight application which use dynamic lists.
Depending on certain settings, the widgets in the list will appear in different places.
This means that a Learned Rapise object which works fine if its in the original ListBox location position is then played-back when it's displayed in another position, it will be ListBox or .
Unlike the XPath option with web testing, Rapise doesn't currently allow regular expressions (Regex) in locators stored inside the objects.js file. This article describes a way around the problem:
When installing Spira on SQL Server 2012 (any edition) using Windows Authentication, you may receive an error message "Cannot Create User" (or similar) during the installation. This is because of a configuration change in SQL Server 2012 (as opposed to earlier versions). This article explains the step needed to prepare SQL Server 2012 for installing Spira v3.x. Newer versions of Spira will not need this step as the installer has been updated.
This article describes the process and steps for moving your SpiraTest, SpiraPlan or SpiraTeam database from one computer to another.
The article will refer to SpiraTeam, but it applies equally to the other products.
This articles describes how to write custom reports in SpiraTest, SpiraPlan and SpiraTeam. It also can be used to modify the layout and styling of the various built-in reports.
This information applies to the following versions of Spira: