Professional Documents
Culture Documents
QaTrac
TechExcel
Affordability
Empirix
Borland Segue
HP Mercury
Compuware
Uncompetitive Incumbents
“…The technical support is superb. They want your business and they will do what is
necessary to get it and keep it… We are a young company with a new product and this
tool is going to allow us to provide the level of excellence that Inflectra has provided us -
without breaking the bank...“
- James Bruno of Dreadlogic Technologies
Define
Requirements
Define Develop
Requirements Release Plan
SpiraTest provides the ability to create, edit and manage project scope /
requirements in a hierarchical organization that resembles a typical scope
matrix. Requirements can also be associated with a specific release.
Each requirement is mapped to one or more test cases that can be used to
validate that the functionality works as expected.
SpiraTest provides the ability to create, edit and delete project test cases that
are stored in a hierarchical folder structure. You can move, copy and filter the
test cases according to a variety of criteria.
Each test case consists of a set of test steps that represent the individual
actions a user must take to complete the test. You can even include other
template test steps as steps within your test case as reusable elements.
You can execute groups of test cases - along with their test steps – so that
the testers can follow the instructions and determine if the system being
tested behaves as expected. Optionally a new incident can be raised in the
system – linked to the test step failure
To make it easier to assign and track the execution of test cases, SpiraTest
allows you to optionally group the test cases into test sets that can be
assigned as a ‘package’ to individual testers.
Each test set can be associated with a particular release for testing, and you
can quickly see the execution status of each test set in one consolidated
view.
Every time you execute a test case, SpiraTest records every pass / failure as
well as the associated incidents generated as a ‘Test Run’. These archived
Test Runs can be viewed to determine if changes to the system have
introduced failures to previously working functionality.
SpiraTest provides the ability to manage the list of releases of the software
being tested. During the execution cycle, the Test Runs and Incidents can
then be associated with a particular release and reported on as such.
The various test cases in the project can be associated with different
releases, so that test runs and test case coverage can be reported on either
in aggregate or separately for each release. This enables you to determine
the quality of each release and also manage regression testing with ease.
SpiraTest provides the ability to create, edit, assign, track, manage and close
incidents (i.e. bugs, issues, risks, defects, enhancements) that are raised
during the testing of the software system under development.
Unlike a standalone bug tracking tool, you can trace the defects back to the
test case and the underlying requirement that generated them, giving the
project manager unprecedented power in analyzing the “in-process” quality
of a system during its lifecycle.
You can customize each of the fields used in the Incident tracking module to
suit your own business needs - including incident type, status, priority and
severity. You can even associate your own color schemes with the different
priorities and severities.
All of the changes made to a particular artifact in the system are tracked by
SpiraTest, so that at any time you can view the history log of all the changes
made to an artifact, including the date of the change, who made the change,
and what information was changed.
In addition to the built-in fields that are associated with each type of
artifact, you can also define custom properties for each type of
artifact in the system, both free-text properties and those where the
user has to choose from a predefined list.
SpiraTest includes an extensive reports library that can display information such
as Requirements Coverage, Test Case Execution, and Incident Status.
Supported formats include HTML, XML, Word, Excel.
Planned:
HP LoadRunner load-testing system
Compuware TestPartner
Empirix e-Tester
Rational suite of test management systems
Requirements Management
Synchronize requirements / use cases with IBM Rational Requisite Pro
Bug / Issue Tracking
Synchronize incidents with Atlassian JIRA
Synchronize incidents with Bugzilla
Synchronize incidents with FogBugz
Synchronize incidents with Microsoft Team Foundation Server