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.
Note: this manual is out of date. Please refer to the new one for Jenkins 2.440 instead.
Beginning on February 15, 2024 and continuing into March, Atlassian will be migrating its customers to a new, centralized user management experience called Atlassian Administration. These changes will change the default permissions and roles in Atlassian's products. These changes may require you to update your permissions to ensure the integration between Jira and SpiraTest works uninterrupted.
When you are installing the Spira plugin for Eclipse on workstations running Eclipse 2022-12, sometimes it won't install because of missing/invalid dependencies. This article provides information on fixing this issue and also how to deploy the fixes for customers where their Eclipse instance is not able to download packages from the Internet.
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
We had a customer that was integrating Spira that was hosted on-premise with a cloud instance of KronoDesk. When they used the feature to log the incident in Spira from a KronoDesk ticket, the incident was created in Spira, but the information did not reflect back in KronoDesk, and an error message was displayed.
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.
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
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.
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.
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.
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.
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.