Below are some of the most popular features in SpiraTeam. Click
on the thumbnail image for each feature to expand the screenshot:
 | Personalized Home Page |
| Upon login to SpiraTeam®, you are presented with a personalized ‘dashboard’ of all your key information, consolidated onto a single page for you to take immediate action. |
|
| Project Summary Dashboards |
| Each project has a dashboard home-page that summarizes all of the information regarding the project into a comprehensive, easily digestible form that provides a “one-stop-shop” for people interested in understanding the overall status of the project at a glance. It contains summary-level information for all types of artifact (requirements, test cases, incidents, etc.) that you can use to drill-down into the appropriate section of the application. |
|
| Project Portfolio Management |
| Projects in SpiraTeam® can be organized into Project Groups that belong to a common organization, customer or division. This allows you to view a summary project group dashboard that lets you view the aggregate status of the group as whole as well as compare the relative health of the different projects in the group: |
|
| Printable Reports Library |
| In addition to the summary tables, charts and graphs displayed on the project homepage, there are more detailed reports that display information such as Requirements Coverage, Test Case Execution, and Incident Status. |
|
| Graphical Charts Library |
| SpiraTeam® includes a rich library of graphical charts and graphs that illustrate key metrics in the system including Requirements Coverage, Test Run Progress, Incident Discovery Rate, Cumulative Artifact Counts, etc. |
|
| Requirements Management |
| SpiraTeam® provides the ability to create, edit and manage project scope / requirements in a hierarchical organization that resembles a typical scope matrix. You can move, copy and filter the requirements according to a variety of criteria, and associate them with a specific release. |
|
|
| Requirements Coverage |
| Each requirement is mapped to one or more test cases that can be used to validate that the functionality works as expected. |
|
| Requirements Elaboration (Tasks) |
| Each requirement can then be decomposed into its low-level assignable work items called ‘tasks’. Each can be separately estimated to validate the overall high-level requirement estimate. |
|
| Test Case Management |
| SpiraTeam® provides the ability to create, edit and delete project test cases that are stored in a hierarchical folder structure that will be familiar to users of Windows® or MacOS®. You can move, copy and filter the test cases according to a variety of criteria. |
|
|
| Test Step Management |
| 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, giving the ultimate in reusability. |
|
| Test Case Coverage |
| Each test case is mapped to one or more requirements that the test is effectively validating, providing the test coverage for the requirement. This provides complete traceability from a recorded incident to the underlying requirement that was not satisfied |
|
| Test Set Management |
| To streamline the assignment and tracking of multiple test cases, SpiraTest allows users to select groups of test cases and arrange them into test sets. Each test set can contain test cases from a variety of different folders and can be associated with a specific release of the system being tested. |
|
| Test Case Execution |
| SpiraTeam® provides the ability to 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. Any deviations from expected behavior can then be recorded, and optionally a new incident raised in the system – linked to the test step failure. |
|
| Test Run Archiving |
| Every time you execute a test case, SpiraTeam® 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. |
|
| Release Planning |
| You have the ability to create a master release schedule containing all the major milestone releases together with the individual iterations – smaller releases of the system delivered every 4-6 weeks. |
|
| Iteration Planning |
| Tasks developed during the requirements elaboration together with Incidents raised during testing can be associated with specific iterations in the release schedule. The system will track the available resources for an iteration and calculate the available effort as tasks/iterations are added. |
|
| Resource Tracking |
| Once the tasks and incidents have been scheduled against the iteration plan and assigned to the project personnel resources, you can use the Resource Tracking screens to view the total assigned workload for the members of the project and determine if any resource load balancing is necessary: |
|
| View Incidents by Release |
| Each release provides drill down capability to list the incidents detected, resolved and/or verified in a particular release, enabling a quick determination to be made as to the stability and readiness of a particular release. |
|
| View Test Runs by Release |
| You can view the list of all the test runs executed against a specific release. Each test run is listed together with a customizable set of fields as well as a link to the actual test run details. The fields that can be displayed include - date of execution, name, tester, execution status, estimated duration, actual duration or any of the custom properties. |
|
| Manage Test Cases by Release |
| 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. |
|
| Artifact Associations |
| Each requirement can be linked to an unlimited number of other requirements, incidents and source code revisions, providing traceability between related artifacts. For example a change request incident that turns into a new requirement can be associated to preserve the pedigree of the requirement. |
|
| Incident / Defect Management |
| SpiraTeam® 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. |
|
| Incident Entry and Modification |
| Incidents can be categorized into bugs, enhancements, issues, training items, limitations, change requests, and risks, and each type has its own specific workflow and business rules. |
|
| Incident Resolution Tracking |
| As different users collaborate on the identification, verification and resolution of a particular incident, their comments and resolutions are tracked as a threaded discussion so that the case history is always available. |
|
| Incident Traceability |
| Unlike a standalone bug/issue tracking tool, you can trace the incidents/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. |
|
| Software Configuration Management (SCM) |
| SpiraTeam® allows you to link your existing software configuration management (SCM) repositories to a particular project. When this is done, you can browse the contents of the repository (folders, files and revisions) directly in the SpiraTeam® web interface, without needing to install the native SCM application. This extends the reach of the SCM repository to managers and other casual users who need to report on the source code repository. |
|
| Source Code Integration |
| In addition to being able to view the contents of the source code repository, using SpiraTeam® you can link artifacts in the system to specific source code revisions. This allows you to associate implemented requirements, completed tasks or resolved defects/incidents with the corresponding code changes. This provides end-to-end traceability from requirements to software code. |
|
| Document Management |
| All documents and web links uploaded to the system are available in the integrated document management system. This allows you to organize the documents into folders, categorize by document types and associate with meta-tags. Once uploaded, users can search, sort and filter the documents as well as find dynamically related items through the meta-tag hyperlinks. |
|
| Document Version Control |
| Once uploaded to the central knowledge repository, revisions to the documents can be uploaded so that there is complete audit trail of all changes made to artifacts and associated documentation in the project. |
|
| Customizable Incident Fields |
| 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. |
|
| Customizable Workflows & Notifications |
| Each of the different incident types can follow its own customized workflow that you can map to the business processes used by your organization. Each workflow consists of a customizable set of steps and transitions. You can set the security on each transition so that only the appropriate user can change the status of an incident. In addition each transition can be used to send email notifications to the detector, owner or users in a certain project group. |
|
| Attachment Support |
| You can upload document attachments to Requirements, Test Cases, Releases and Incidents in the system. Each of these artifacts includes an attachment view that allows users to view the existing attachments, delete an existing attachment and upload new documents from their workstation. |
|
|
| Change History Tracking |
| All of the changes made to a particular artifact in the system (e.g. Requirement, Test Case, etc.) 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. |
|
|
| Custom Artifact Properties |
| In addition to the built-in fields that are associated with each type of artifact (Requirements, Test Cases, etc.), 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. |
|
| System / Project Administration |
| Once SpiraTeam® is set up on your web server it can be fully administered and maintained using only a web browser. No need to install complicated software or have IT staff involved every time you wish to create new project or add a user to the system. |
|
| Project Management |
| SpiraTeam® allows you to easily create, edit, copy, and delete projects using a web-based interface. In addition you have the option of creating a new project using the customized settings of an existing template project. |
|
| User Management |
| SpiraTeam® allows you to easily create, edit and make inactive users using a web-browser. In addition you can import user profiles from any LDAP compatible directory server (e.g. Microsoft ActiveDirectory). Once imported, SpiraTest will authenticate those users against that server, removing the need for users to manage passwords in multiple places. |
|
| Excel Data Import |
| The web-based interface of SpiraTeam® is ideal for creating and managing requirements, test cases and incidents for a new project. However when migrating requirements, test cases, test steps and incidents for an existing project from another system or Microsoft Office document (e.g. Excel), it is useful to be able to load in a batch of artifacts, rather than having to manually enter them one at a time. To simplify this task, SpiraTeam® comes with a Microsoft Excel data importer that can bulk-load requirements, test cases, test steps and incidents from a populated Excel sheet into SpiraTeam®. |
|
|
| Mercury QualityCenter® Importer |
| Add-on utility that allows users of HP Mercury QualityCenter (formerly TestDirector) to easily migrate their Requirements, Test Cases, Test Steps, Test Runs and Defects into SpiraTeam. This allows those users to take advantage of our business-friendly licensing scheme. |
|
|
| IBM Rational RequisitePro® Adapter |
| Add-on utility that allows users of IBM Rational RequisitePro to import Requirements and Use Cases into SpiraTeam on an ongoing basis. This means that users can manage requirements and use cases in RequisitePro and seamlessly use SpiraTeam to manage the testing of those same requirements and test cases. |
|