This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

5.2.3. Overview - Automation

The Automation section displays any automated test scripts associated with the current test case. There are three types of automated test:

  • Attached – this is when SpiraTeam physically stores the test script as an attachment in the system. This is only available for test automation tools that store their test scripts as plain text files. Examples of such tools are Selenium-RC and Squish.
  • Linked – this is when SpiraTeam stores the location of the test script stored on the automation host itself or on an external network drive.
  • Repository – This is a special option only available when using Rapise™, the test automation system from Inflectra. This allows you to store an entire folder of automated test script files in SpiraTeam and have them linked to the test case.

The screenshot below illustrates a sample Rapise automated test script attached to a test case:

The automation screen includes the following fields that you should populate when using SpiraTeam® to store an automated test script:

  • Automation Engine – this should be the name of the test automation engine that the test script should be executed with. This list is populated by a system administrator using the administration section of the application (as described in the SpiraTeam Administration Guide)
  • Script Type – This should be set to either “attached” or “linked”. If you choose to attach the test script, the large text box at the bottom will be enabled, allowing you enter/edit the test script directly in SpiraTeam. If you choose linked, the test script is stored externally and SpiraTeam just stores a reference to it. The “repository” option is never selectable within SpiraTeam and will be automatically set by Rapise when it attaches a test script to the test case.
  • Filename – If you are attaching the test script to the test case then this field just needs to contain the filename of the test script (no folders or path needed), whereas if you are choosing to link the test script, you need to follow the exact format that will be expected by the test automation engine. For details, please refer to the specific test automation engine in the SpiraTest/Team Automated Test Integration Guide.
  • Document Type - This should be set to the document type that you want the test script associated with.
  • Document Folder - This should be set to the document folder that you want the test script to be stored in.
  • Version – This should contain the version number of the test script.
  • Test Script – If you are attaching a test script, this should contain the actual program code for executing the test script. The language and syntax will be dependent on the test automation engine being used. If you are linking the test script, this section will be disabled.
  • Parameters – You can enter the various test case parameters by clicking on this hyperlink. Most of the automation tools that SpiraTeam integrates with will support the passing of parameter values from SpiraTeam to the automation tool.