March 30, 2023
During a recent product demonstration we were asked to explain how SpiraTest's test case parameters work. One of the key features is the way they can be used recursively to make your test cases more modular and reusable. One of our account managers likened the concept to the way dreams were nested in the popular Science Fiction movie Inception.Read More
January 10, 2022
We had a customer ask us what was the recommended way to manage the Acceptance Criteria of requirements in a project. There are actually several different ways you can handle acceptance criteria depending on your exact process (and preference):
We discuss each of these options below:Read More
August 7, 2020
One of the focus areas in the new release v6.6 of SpiraTeam and SpiraPlan is completing the initial support for baselining. This is an exciting new piece of functionality that makes SpiraTeam and SpiraPlan especially well suited for managing requirements, test cases and artifacts on more complex systems and engineering projects.Read More
July 6, 2020
One of the focus areas in the upcoming release v6.5.2 of SpiraTeam and SpiraPlan is support for baselining. This is an exciting new piece of functionality that will make SpiraTeam and SpiraPlan especially well suited for managing requirements, test cases and artifacts on more complex systems and engineering projects.Read More
July 6, 2017
One of the questions we get asked a lot by new users of SpiraTest is:
What is the best way to assign test cases to my users so that they can do their testing?
This article discusses the different options and provides the best solutions for your situation.
June 3, 2016
We are really excited with the launch of SpiraTeam 5.0 this week.
SpiraTeam 5 brings a lot of new features, new design, and also lots of
changes from version 4.2. Over the next few weeks we will be posting a
number of articles to explain the biggest changes. This post discusses
how folders for test cases, test sets, documents and tasks have been
reworked for a more consistent and better customer experience.
February 4, 2016
When test cases are written well, the automation follows simply from the steps. Writing a good test case isn’t difficult, it’s just tedious, boring and sometimes downright painful. But when it’s done right, the results are worth it.