A customer recently asked how Spira could support their internal process of Test Cases moving through a sequential Workflow for approval, first as a manual Test Case and then as an Automated Test case.
Test Cases in Spira can have both a manual Test Steps section and an Automation section.
In this article, we describe how to set up a two workflows that will work in a sequence.
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).
This article is now obsolete.Custom Properties are now always active and do not require separate activation.
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.
During the upgrade of an older version of Spira v6.x to the latest version of Spira v6.x the installer logs the following:
Cannot insert the value NULL into column 'TASK_WORKFLOW_ID', table 'SpiraTest.dbo.TST_TASK_TYPE'; column does not allow nulls. UPDATE fails. The statement has been terminated. [System.Data.SqlClient.SqlException]
When you upgrade from v5.4 to v6.0 upon opening a test case detail page you receive the error: "The 'TestCaseWorkflowId' property on 'TestCaseType' could not be set to a 'null' value". This article explains the cause and provides the solution