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.
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.
If you need to connect Database object to PostgreSQL database follow these simple steps.
If you need to connect Database object to MySQL database follow these simple steps.
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.
The SQL Server Database Engine Tuning Advisor examines how queries are processed in the databases you specify, and then recommends how you can improve query processing performance by modifying database structures such as indexes, indexed views, and partitioning. This can be used by on-premise customers to improve the performance of their Spira and KronoDesk instances.
When you are installing SpiraTest, SpiraTeam, SpiraPlan or KronoDesk on a database server with a large 'model' database sometimes the install will fail because the initial Spira/KronoDesk database is not large enough to contain your model database. This article provides the solution
Sometimes customers want to download their list of tickets and file attachments. This article explains how to read the data that we provide.
Sometimes you want to delete the sample users in SpiraTest, SpiraTeam or SpiraPlan. This article explains the steps for doing this.
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.
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.
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.
Sometimes you create user accounts in SpiraTeam for real users to login and test the system. For example you may have a UAT (user acceptance testing) phase, or a crowdsourced testing event (like our Software Testing Bowl). You then want to turn over the data to a third party supplier, but you need to anonymize the users' personal information
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. Since v5 of SpiraTest, this has been possible inside the Spira user interface, however many customers have been looking for a way to map test steps to requirements in bulk using Excel.
The steps to perform when needing to move the database to another SQl Server, or when changing the DNS name of your SQL Server.
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.
With the establishment of the EU General Data Protection Regulation (GDPR), you now may need to find old SpiraTeam projects that are not active any more so that you can delete them and reduce unnecessary storage of personal data.
When you try and do a substring on a value returned from a database, you may get an error about the object not supporting the property.
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.
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.
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.
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 v22.214.171.124.
When you install SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk on premise, you have a choice in different ways to configure SQL Server. Every situation is different, but this article presents some recommendations.
One common requirement is to run a query in an application being tested and verify that the data on the screen matches the data in the application. This article explains the recommended process for doing 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.
With the latest version of SpiraTest, SpiraPlan and SpiraTeam, we have provided a simple button in the Data Tools section that lets you rebuild the database indexes using the same script that we published in KB10. However sometimes the database is so large that the execution takes longer than the 30 minutes allowed by the application, or you want more control over the fragmentation levels that trigger a rebuild. This article provides guidance and a more advanced script for power users.
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.
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.
A customer had a question - is there a way to suppress the DoSetText or DoSendkeys methods from sending their text to the logs. They didn't want users to see this text in the Rapise (and SpiraTest) logs because they contained sensitive information (e.g. passwords).
As part of the v5.0 update to SpiraTest, SpiraPlan and SpiraTeam, we made major changes to the database structure to improve performance and usability as well as lay the foundation for v5.1, v5.2 and v5.3 due out later this year. Customers using custom reports
that relied on the old v4.2 database structure will need to modify their custom reports.
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?
When connecting from Spira or Krono installed on a separate application server to a remote SQL server, you may have difficulties connecting. This article describes the steps for making sure that your SQL Server can be accessed remotely.
This usually just means that the restored database just needs to be linked to the existing database server login. This can be done by executing the appropriate SQL command listed below:
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.
This article answers some common questions about which databases you can run SpiraTest, SpiraPlan, SpiraTeam and KronoDesk on, and where you can get them from.
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.
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 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.