Our Office365 addin let's users easily and quickly send data to Spira, or get data out of Spira, across different products and artifacts. We distribute this addin from within Microsoft's Office marketplace. This gives users convenience and confidence: the addin is easy to install, and has been vetted by Microsoft's marketplace team. Some organizations do not allow users to use this marketplace. How do you use this addin in such cases?
Often you want to be able to parameterize your Rapise tests to have a common set of test functions that can use different combinations of test data. You can use a MS-Excel spreadsheet to store the test data and use Rapise to read out the matching values. This articles provides a sample for doing this.
If you are using our Excel 365 addin you may see the error message:
We Can't Load This Add-In Because We Couldn't Connect to the Catalog
The steps to take to resolve this are below
Sometimes when using our MS-Office Add-Ins (for Excel, Word and Project) on a new computer you will see an error message of the type:
Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Tools.Excel.Worksheet'. This operation failed because the QueryInterface call on the COM component for the interface with IID ...
This article explains the cause of these types of error and provides some common solutions
If you need to make a copy of data in a Table/Grid object - you may simply save it to Excel file with a single function call.
Unfortunately, Windows10 has a nasty habit of frequently updating itself and then breaking existing applications. We found that the February 14th, 2018 Windows10 update corrupted the Excel device driver that Rapise uses to access the RVL test script spreadsheet during playback.
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.
When you install the Spira MS-Office Add-Ins to help import data into SpiraTest, SpiraPlan or SpiraTeam from Excel, Word or MS-Project the installer will check that you have the Microsoft Visual Studio Tools for Office (VSTO) pre-requisite installed. Sometimes if you have this already installed with a newer version it will prevent the install from completing.
We recently announced the release of an updated MS-Office
plugin for Spira v5.0 that makes use of the new API in Spira 5.0. However some customers still need the older MS-Office 2010+ plugin for older versions of Spira (v4.x).
The symptom is that whenever a user tries to open an Excel format report in SpiraTest, SpiraPlan or SpiraTeam, the report will download. When the user clicks on it to open,
Excel opens but the area where the report should be is blank and gray. It affects all reports types in Excel format. Other formats (HTML, XML, etc.) work fine.
This article describes the steps for importing data from an Excel
spreadsheet into KronoDesk. You can use this to import help desk tickets and notes.
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 opening the SpiraTeam MS-Excel 2007+ reports in MS Office 2010 or later you may get a message displayed - "The file you are trying to open 'xxx.xls' is in a different format than specified by the file extenstion". This article explains why this message appears and how to deal with it.
The built-in Spreadsheet object in Rapise makes it easy to read data from an MS-Excel spreadsheet. What happens if you want to write data back to the Excel sheet?
If you have installed the MS-Office Add-In for SpiraTest, SpiraPlan or SpiraTeam and the necessary prerequisites (VSTO and the Primary Interop Assemblies if using the MS-Office 2003 Add-In) but it won't display the Add-In in your instance of MS-Excel, MS-Word or MS-Project, follow these instructions to help us troubleshoot.
Several users have asked -- if it is possible to extract all incidents logged in a SpiraTest sever no matter what the project is. Using the built-in Incident reports or Excel Add-In, you have to extract incidents for each project and then move into one spreadsheet however they wanted to know if it was possible to do this as one extract from within the tool.
Since our MS-Office 2007 Add-In for SpiraTeam uses the Microsoft VSTO technology, it's limited to being installed for a single user on a given PC. However if you need to be able to have multiple users access it, there are some registry keys that you can manually add.
This article describes the steps for importing data from an Excel spreadsheet into SpiraTeam. You can use this to import requirements, test cases, tasks, incidents and releases.