SpiraTest v1.0 User Manual
Contents
1. E eae AAA Copyright C 2006 inflectra Corporation SpraTeat v1 0 inflectra Zz The screen is divided up into three main elements gt The top navigation bar with a gray background contains a link back to the test case list together with the navigation that allows you to move between the different test cases being executed You can either directly select the test case from the drop down list and click lt Select gt or use the movement buttons that look like the buttons on a music player from left to right they move to first move to previous move to next and move to last test case Regardless of the method chosen when the test case is changed the list of test steps available in the left hand pane is refreshed The left hand navigation pane contains the list of test steps for the currently executing test case You can click on the test step link to move between the test steps in the current test case In addition each test step has a colored square next to the name that indicates its status green Passed red Failed gray Not Run in the current test run The overall test case also has an execution status If any of the steps are marked as Failed then the overall test case Failed if all the test steps passed then the overall test case is ma2. If the actual results differ from those expected you need to enter a description of the result observed and click the lt Fail gt button this is illustrated in the screen shot below V elcome Fred Bloggs My Profle Log Out n System gt Test Cases gt Tost Case Execution Curent Test Case Ab ity to create new author gt Select 10 0 gt 0 BK Ability to create mew author Please follow the directions outlined n the box below i Stee 0001 Weer clicks link tc create author KM Stop 0002 Step 0003 Step 0004 Expected Resut_ Stee 0005 User taken to first screen in wizard Please erter the actual test result it differs then chck the appropnate button Actual Resu E Log an incident for thes step The screen displaye e 404 error page Name Create Author Page Miseng ma ERA gt Fintan Cancet Copynght C 2006 Intactra Corporation SperaTest v1 0 inflectra Unlike the lt Pass gt button if you don t enter a description of the actual result the system will display an error message and re prompt you again for input In the case of a failure both the individual test step and the overall test case will be marked with a red square containing a cross You will now have the option of moving to the next test step by clicking the lt Next Test gt button if it is the last test case being executed the lt Finish gt button will be displayed instead In addition to logging the failure you can option
3. Test Script Management Defect Issue Bug Tracking However this stove piped approach has many limitations and drawbacks most importantly that fact that there is no traceability between the different artifar all the ramuiramanta haun haan tantad Mammals Clicking on any of the links in the left hand table of contents will automatically scroll the reading pane on the right to the appropriate section in the help manual By default the reading pane will open to the help item that is most closely related to the screen you happened to be on when you clicked the Help link 3 4 Project Home When you click on either the Project Home tab or the name of the project in the My Page project list you will be taken to the homepage of the specific project in question Sampie apphcaton that allows users to manage books authors and lending records tor a typrcal Priority Dare Opened branch trary 10ec 200 Garoa emat tem on Wingows WE a gt J An t D ly Maze 1Oec 200 Wed enn ANI Cr Management af ct ans tec 200 hoger Dacorer Rate Systems xta charge 100200 Date Opened 10 Dec 2009 10 Dec 2003 10 Dec 2009 Ea 4 Low Nene TOTAL 3 5 16 e 3 Functional System Requirements Oncino brary Management Sytem Book Managemect la add new bocta y the sy3ten This page summarizes all of the information regarding the project into a comprehensive easily digestible form that provides a one stop shop for p
4. User Project Management 3 1 Login Screen 3 2 My Page 3 3 Global Navigation 3 4 Project Home 3 5 My Profile 4 Requirements Management 4 1 Requirements List 4 2 Requirement Details 5 Test Case Management 5 1 Test Case List 5 2 Test Case Detais 5 3 Execute Test Case s 5 4 Test Run Details 6 Incident Tracking 6 1 incident List 6 2 Incident Details 6 3 ncident Discovery Report SpiraTest User Manual 1 Introduction Quality Assurance QA is a key component of the Software Development Life Cycle SDLC which needs to be integrated into the management of the program or project from its inception Too often though QA is implemented as quality control whereby testing that the required functionality works as expected is performed at the end when it is most costly to make corrections and changes To manage QA across a project from day one it is imperative that the original requirements are documented together with the use cases that validate the desired functionality These use cases then form the basis for the test scripts that can be executed to validate that the functionality has been correctly built and that the requirements have been satisfied During the execution of these test scripts failures may occur which are recorded as incidents to either be fixed or documented depending on the severity Typically these activities require people to use at least three different types of software Requirements Management
5. but before any of the test cases Note that in a test folder all of the child test folders are always displayed before any of the actual test cases Once the new test folder has been inserted the item is switched to Edit mode so that you can rename the default name and choose an owner and or author 5 1 3 Delete Clicking on the lt Delete gt button deletes all the test cases and or test folders whose check boxes have been selected If any of the items are test folders then all the children are all deleted whether test cases or folders This behavior is similar to that in Microsoft Windows Explorer Note that you cannot delete all the test cases in a test folder at least one test case needs to be left in the folder the system will warn you if you try to do this 5 1 3 Execute Clicking on the lt Execute gt button executes all the test cases selected together with all the test cases contained with any selected test folders The test execution functionality of SpiraTest is explained in more detail in section 5 3 5 1 4 Refresh Clicking on the lt Refresh gt button simply reloads the test case list This is useful as other people may be modifying the list of test cases at the same time as you or executing specific test cases and after stepping away from the computer for a short time you should click this button to make sure you are viewing the most current test case list for the project 5 1 5 Edit Each test case
6. Project Home Requirements Test Cases and Incidents that correspond to the five main parts of the system as well as three secondary links to My Profile and Log Out and Help Each of the main sections is described separately in this manual however it is worth noting that the section you re currently accessing will always be displayed in a darker color blue that matches the horizontal bar The main tabs will take you to the appropriate artifact type requirement test case incident etc for the currently selected project However if you haven t selected a project then clicking on any of the tabs will simply take you back to My Page so that you can select a project 3 3 1 Log Out Clicking on the Log Out link will immediately log you out of your current session and return you to the login page illustrated in section 3 1 If you had set the Remember Me option during your previous login that setting will be reset so if you want to avoid having to keep logging in you ll need to re check that box during your next log in 3 3 2 Help Clicking on this link on any page will bring up the online version of this manual shown below a SpiraTest Online Help Microsoft Internet Explorer Spira Table of Contents 4 Introduction 2 Functionality Overview 2 1 Requirements Management 2 2 Test Management 2 3 Incident Tracking 2 4 Projects and Users 2 5 Artifact Relationships 26 Application Ste Map 3
7. ability to view the incidents associated with particular test cases and test runs enabling drill down from the requirements coverage display right through to the open incidents that are affecting the requirement in question 2 4 Projects and Users SpiraTest supports the management of an unlimited number of users and projects which can be administered through the same web interface as the rest of the application All artifacts requirements tests and incidents are associated with a particular project and each user of the system can be given a specific role for the particular project So a power user of one software project may be merely an observer of another That way a central set of users can be managed across the enterprise whilst devolving project level administration to the manager of the project In addition to these administration functions each user profile and project has its own personalized dashboard view of all the pertinent and relevant information This feature reduces the information overload associated with managing such a rich source of project information and allows a single user or project snapshot to be viewable at all times for rapid decision making 2 5 Artifact Relationships The sections above have outlined the different features and functions available in the system and have described the various artifacts managed in the system e g projects users requirements tests etc To aid in understanding h
8. consolidated onto a single page for you to take immediate action The page typically consists of the following elements 3 2 1 My Projects This section lists all the projects you have been given access to together with the name description web site and date of creation To view the description of the project simply position the mouse pointer over the link and a tooltip window will popup containing the description When you initially view the page all of the projects will be shown as links in normal type with a white background When you click on a project to view you will be taken to that project s home page and that project will be set as the current project That project will now appear in your home page in bold type with a yellow background see above screen shot To change the currently selected project simply click on the link of another project name 3 2 2 My Tests This section lists all the test cases you have been made owner of across all the different projects you are a member of This typically means that the project manager has assigned you to be responsible for executing the assigned test scripts To aid in this process the script name is displayed along with its last execution status failed passed or not run and date of last execution This enables you to see how recently the tests have been run and whether they need to be re run If you click on the test name hyperlink you will be taken to the details page fo
9. current project 6 1 5 Refresh Clicking on the lt Refresh gt button simply reloads the list of incidents this is useful when new incidents are being added by other users and you want to make sure you have the most up to date list displayed 6 1 6 Edit Each incident in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information This is useful for making simple changes to an incident it avoids having to first go to the incident details page To change fields not displayed in the incident list you will however need to click on the incident name to view the Incident Details page see section 6 2 6 2 Incident Details When you click on an incident item in the incident list or click the lt New Incident gt button as described in section 6 1 you are taken to the incident details page illustrated below aits Ojolcia Cannot add a new book to the system Bug Assgned v Test Run Step 000003 Proety Cissed On Last oddities mir Description Waen I click on the Button to edd a book enter the sew informatics and clic oubmit get e subecript out of
10. folder in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information 5 2 Test Case Details When you click on a test case item in the test case list described in section 5 1 you are taken to the test case details page illustrated below Welcome Fred Bloggs My Profle Log Oss spiraTest ibrary Information System gt Tes ases gt lost Caso Details Premise 3 Oete O Moo MorDon 2 Roter Functional Tests Test Case Abrity to create new book T ability to create new book O View Test Steps View Test Runs View Coverage Y Absity to edt eating hook a 00001 User logs in to app cation User taken to man menu screen Abiity to oct sating author A Da a O 000002 User clicks link to create book User taken to first screen in wizard 000003 User enters books name and author then User taken to next screen in wizard checks Next 000004 User chooses book s genre and sub genre User sees screen displaying all entered from list wformabon O 000005 User clicks submit button Confirmabon screen is displayed Copynght C 2006 Intactra Corporation SpiraTest vt 0
11. of incidents either created or closed in a 7 day period and the x axis represents a specific week in the time span Each data point can be viewed by positioning the mouse pointer over the point and a tooltip will pop up listing the actual data value Clicking the Back to Project Home hyperlink will take you back to the Project Home dashboard Legal Notices This publication is provided as is without warranty of any kind either express or implied including but not limited to the implied warranties of merchantability fitness for a particular purpose or non infringement This publication could include technical inaccuracies or typographical errors Changes are periodically added to the information contained herein these changes will be incorporated in new editions of the publication Inflectra Corporation may make improvements and or changes in the product s and or program s and or service s described in this publication at any time SpiraTest and Inflectra are trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Explorer and Microsoft Project are registered trademarks of Microsoft Corporation All other trademarks and product names are property of their respective holders Please send comments and questions to Technical Publications Inflectra Corporation 10301 Julep Avenue Silver Spring MD 20902 U S A info inflectra com
12. rence error Copyright C 2005 infiectra Corporation SpraTest vt 0 inflectra This page is made up of two areas the top navigation bar with the gray background that allows you move between incidents and the main pane yellow background that contains the details of the incident in question The navigation bar allows you to move within the list of incidents that were displayed in the incident list page without having to go back to that page So if the incident list page contained a list of all bugs sorted by priority the buttons on this navigation would allow you to cycle between the different bugs in order of priority If you want to view incidents that are outside this filtered list or want to change the way they are sorted you need to click the Back to Incident List hyperlink and change the filter sort on the incident list page You can either enter a specific incident number in the text box and click the lt Find gt button or simply click one of the four movement buttons move first move previous move next and move last to cycle to a different incident in the list 6 2 1 Editing an Existing Incident If you are editing an existing incident the following fields will be editable for you to change gt Name Status New Open Assigned Fixed Closed Duplicate Cannot Reproduce Incident Type Bugs Enhancements Issues Training Items Limitations Change Requests and Risks Detected By User Assigned Owner P
13. 2 3 4 7 Incident Summary This section consists of a summary table that displays the aggregate count of incidents in the system broken down by importance on the x axis and status on the y axis This allow the project manager to determine how many critical vs low priority incidents are waiting to be addressed and how many new items need to be categorized and assigned Clicking on the View Details link at the top of the table simply brings up the incident list see section 6 1 By default this summary table displays the total count of all incidents regardless of type however my changing the drop down list to a specific incident type e g bug enhancement issue etc the project manager can filter the summary table to just items of that type 3 4 8 Test Execution Status This section consists of a bar graph that displays the aggregated count of test cases in each execution status for the project Note that this graph does not consider past test runs when calculating the totals in each status Passed Failed or Not Run it simply looks at each test case and uses the last run status as the best health indicator Thus if a test case that previously passed has subsequently failed upon re execution it will be considered a failure only If you position the mouse pointer over any of the three bars the color of the bar changes slightly and the underlying raw data is displayed as a tooltip together with the percentage equivale
14. ally choose to have the failure result in a new incident be automatically created This is achieved by selecting the Log an Incident for this step checkbox and entering a name for the new incident The other information needed for the new incident is automatically populated from the test step details The newly created incident will also be linked to the test step allowing traceability from within the incidents module The functionality for managing incidents is described in more detail in section 6 Note that the entire test run is not actually saved until the lt Finish gt button is clicked so you can use the move forward backward buttons to revisit previous test cases and or test steps and make changes before saving the test run As a consequence however you should make sure you complete the test run or at least the test cases you have time for and save it before leaving the computer for a period of time this will ensure work is not lost due to the timeout of your session 5 4 Test Run Details As described in section 5 2 8 when you view the details of a test case one of the views possible is to list all the test runs for that test case Welcome Fred Bloggs My Profile Log Out spiraTest Test Case Ability to create new book O View Test Steps View Test Runs View Coverage 100c 2003 Ability to create new book 1 Dec 2003 Ability to create new book Copynght C 2006 ieflectra Corporation SpraTest v1 0 i
15. c 2003 Edition Management in Progress Fred Bloggs 1 Dec 2007 Author Management In Progress Joe P Smith 1 Dec2003 Subject Management Planned Joe P Smith 1 Dec2003 000019 Ed Administration Functions Requested Joe P Smith 1 Dec2003 000022 Edit Copyright C 2006 Infectra Corporation SperaTest v1 0 inflectra Z The requirements list consists of a hierarchical arrangement of the various requirements and functionalities that need to be provided by the system in question The structure is very similar to the Work Breakdown Structure WBS developed in Microsoft Project and users of that software package will find this very familiar to use When you create a new project this list will initially be empty and you will have to start using the lt Insert gt button to start adding requirements Requirements come in two main flavors summary items shown in bold type and detail items shown in normal type with a hyperlink When you indent a requirement under an existing requirement the parent is changed from a detail item to a summary item and when you outdent a child item its parent will return to a detail item assuming it has no other children This behavior is important to understand as only detail items are assigned a status themselves the summary items simply display an aggregate of the worst case assessment of their children s status Also only detail items can be mapped against test cases for test coverage thus only they hav
16. d to insert it first then indent it with the lt Indent gt button If you insert a requirement without first selected an existing requirement from the list the new requirement will simply be inserted at the end of the list Once the new requirement has been inserted the item is switched to Edit mode so that you can rename the default name and choose a priority status and or author 4 1 2 Delete Clicking on the lt Delete gt button deletes all the requirements whose check boxes have been selected If any of the items are summary items then if the item is expanded and the children are visible the children are simply made children of the item above it in the list however if the item is not expanded and the children are hidden then the children are all deleted This behavior is similar to that found in project planning tools like Microsoft Project In addition if all the children are deleted from a summary item it changes back into a detail item 4 1 3 Indent Clicking on the lt Indent gt button indents all the requirements whose check boxes have been selected If any of the items are made children of a requirement that had no previous children it will be changed from a detail item into a summary item 4 1 4 Outdent Clicking on the lt Outdent gt button de indents all the requirements whose check boxes have been selected If any of the items were the only children of a summary requirement item then that item will be cha
17. e hyperlinks the summary items simply display an aggregate coverage status of their children Each requirement is displayed along with its importance priority ranked from Critical to Low and its completion status from Requested to Completed as well as a graphical indicator that represents its coverage status For those requirements that have no test cases covering them i e validating that the requirement works as expected the indicator consists of a yellow solid bar bearing the legend Not Covered For those requirements that have at least one test case mapped against them they will display block graph that illustrates the last execution status of each of the mapped test cases Thus if the requirement is covered by two test cases one of which passed and one of which wasn t run the graph will have three green bars 50 passed and three gray bars 50 not run Note The number of bars has no relation to the number of tests To determine the exact requirements coverage information position the mouse pointer over the bar chart and the number of covering tests along with the pass fail not run breakdown will be displayed as a tooltip 4 1 1 Insert Clicking on the lt Insert gt button inserts a requirement above the currently selected requirement i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a requirement below a summary item you nee
18. e original requirements are documented together with the use cases that validate the desired functionality These use cases then form the basis of the test scripts that can be executed to validate that the functionality has been correctly built and that the requirements have been satisfied During the execution of these test scripts failures may occur which are recorded as incidents either to be fixed or documented depending on the severity Typically these activities require people to use at least three different types of software gt Requirements Management gt Test Script Management gt Defect Issue Bug Tracking However this stove piped approach has many limitations and drawbacks most importantly the fact that there is no traceability between the different artifacts How can the project manager know that all the requirements have been tested Conversely how can the developer know which test script was responsible for a recorded bug needed to accurately reproduce the issue This user manual outlines the features and functionality available in SpiraTest and demonstrates how to use the application for managing the QA processes on a typical project 2 Functionality Overview This section outlines the functionality provided by SpiraTest in the areas of requirements management test management incident tracking and project user management 2 1 Requirements Management SpiraTest provides the abil
19. e past 60 days of data daily or for the past 12 months of data weekly The screen shot below illustrates the discovery report loaded with the past 60 days of incident discovery closure data depicted on a daily basis Welcome Fred Bioggs My Profle Log Oss gt Last 60 Days of Data Day OLast 12 Months of Data Weekly Incident Discovery Rate Report Ducowed Closed og LN SI INi Be bP oh 0 0 5 Oo 09 0 08 444 4480000 50 0 5 0 00 0 22 OP PPP LOL LSESOOOEOD z 11 90 2003 00S NEADS M MSQUO eNO 1152003 10012003 1026 2003 10210003 1235000 nas Copyright C 2006 Infectra Conperation SpiraTest vt 0 inflectra Zz In this version of the report the y axis represents the number of incidents either created or closed in a 24 hour period and the x axis represents a specific day in the time span Each data point can be viewed by positioning the mouse pointer over the point and a tooltip will pop up listing the actual data value Similarly by clicking on the date range radio button you can display the past 12 months of incident discovery data organized on a weekly basis Welccene Fred Bloggs My Profle Log Osi spiraTest Library Information System O Last 60 Days of Data Day Last 12 Months of Data Weekly Incident Discovery Rate Report Discoeed Closed Copyright C 2006 infectra Corporation SpiraTest vt 0 inflectra In this version of the report the y axis represents the number
20. ed by their gray color The right box which will initially be empty contains the list of test cases mapped to this requirement The test cases in this box are color coded according to their most recent execution status red for failed green for passed and gray for not run Double clicking on items in this box will jump you to the test case details screen for this test case see section 5 2 9 To change the coverage for this requirement you use the buttons Add Remove Remove All positioned between the two list boxes The lt Add gt button will move the selected test cases from the list of available on the left to the list of mapped on the right Similarly the lt Remove gt and lt Remove All gt buttons will remove either the selected or all the test cases from the right list box and add them back to the left list box Note that none of the changes are committed until you click the lt Update gt button at the bottom right of the screen If you want to discard the changes you have made simply click either the lt Cancel gt button or the Back to Requirements List link and you will be returned to the Requirements List page 5 Test Case Management This section outlines how the use case test case management features of SpiraTest can used to develop the business use cases for the system which specify how the different pieces of functionality are expected to work in practice In addition these use test cases form the basis of t
21. em ey mw spiraTest we SpiraTest User Manual Version 1 0 Inflectra Corporation Date November 21 2006 inflectra Contents 1 Introduction 2 Functionality Overview 2 1 Requirements Management 2 2 Test Management 2 3 Incident Tracking 2 4 Projects and Users 2 5 Artifact Relationships 2 6 Application Site Map User Project Management 3 1 Login Screen 3 2 My Page 3 3 Global Navigation 3 4 Project Home 3 5 My Profile Requirements Management 4 1 Requirements List 4 2 Requirement Details Test Case Management 5 1 Test Case List 5 2 Test Case Details 5 3 Execute Test Case s 5 4 Test Run Details Incident Tracking 6 1 Incident List 6 2 Incident Details 6 3 Incident Discovery Report 1 Introduction SpiraTest provides an integrated holistic Quality Assurance QA management solution that manages requirements tests and incidents in one environment with complete traceability from inception to completion Quality Assurance is a key component of the Software Development Life Cycle SDLC which needs to be integrated into the planning and management of a program or project from its inception Too often though QA is implemented as Quality Control whereby testing that the required functionality works as expected is performed at the end when it is most costly to make corrections and changes To manage QA across a project from day one it is imperative that th
22. eople 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 Each of the sections that make up the homepage is described below 3 4 1 Project Overview This section displays the name of the project together with a brief description the web site that points to any additional information about the project the names of the owners of the project and a link to the all available reports for the project Currently the only report available is the Incident Discovery Rate report that is described in section 6 3 3 4 2 Requirements Summary This section consists of a summary table that displays the aggregate count of requirements in the system broken down by importance on the x axis and status on the y axis This allow the project manager to determine how many critical vs low priority enhancements are waiting to be implemented vs actually being implemented In addition it makes a distinction between those requirements simply requested and those actually planned for implementation so the project manager can see what the backlog is between the customer s demands and the plan in place Clicking on the View Details link at the top of the table simply brings up the project requirements list see section 4 1 3 4 3 Requirement
23. es are committed until you click the lt Update gt button at the bottom right of the screen If you want to discard the changes you have made simply click either the lt Cancel gt button or the Back to Test List link and you will be returned to the Test Case List page 5 3 Execute Test Case s When you select test cases on the test case list page and click the lt Execute gt button or click the Execute link on the test cases listed under My Tests on your personalized home page you are launching the test execution module with the selected test cases This section describes how a tester can follow the steps defined for a series of test cases and record what actually happened in the process In addition recorded failures of test cases can be used to automatically generate new incidents that will be added to the incident tracking module see section 6 Regardless of the route taken to launch the test execution module the screen that will be displayed will look like the following stom gt Test Cases gt Tost Case Execution Current Test Case Abikty to create new book v ie 4 gt Ability to croste new book Please follow the deectons outlined in the box below Stop 0001 Weer logs in to spplicatics Step 0002 Sep 000 Step 000 Sent Expected Result Step 0005 User taken to main menu screen Please enter the actual test result if difers then click the appropriate button Actual Resut O Log an incident for this step
24. have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information 5 2 8 View Test Runs This view displays the name of the test case together with a list of the previous execution runs that the test case has been put through Each test run is listed together with the date of execution the name of the test case the name of the tester the overall execution status for the test case in that run and a link to the actual test run details see section 5 4 Welcome Fred Bloggs My Profile Log Out dP immertsieo 3 Dee QMowUp Move own Qy Rates Test Case Ability to create new book OView Test Steps View Test Runs View Coverage Ability to cromo new book Frod Bloggs Abiity to create new book Joe P Smith nF Copyright C 2005 inflectra Corporation SpieaTest vt 0 inflectra Z 5 2 9 View Coverage This view displays the name of the test case together with the requirements coverage information for the test case in question a gt Welcome Fred Bloggs My Profle Log Oss spiraTest _ ibrary information System gt Test Ca lt lt Back to Test List Test Case Ability to create new book Funcional Tests T Ability to create mew book View Test Steps View Test Runs View Coverage The requrements coverage box mdicates the requirements that are Currently mapped against the test case To add reqarements to thes test case choose fro
25. he business specification of the system when associated with the underlying requirements matrix Typically when starting a new project gt The requirements matrix is entered first gt Then the list of use cases is developed to outline the key scenarios that need to supported to implement the requirement gt Then the use cases are fleshed out into full test cases by adding the detailed test steps with the expected result and suggested sample data However when migrating existing projects into SpiraTest you may need to migrate the test case list first and then add the supporting requirements matrix afterwards 5 1 Test Case List When you click on the Test Cases tab on the global navigation bar you will initially be taken to the test case list screen illustrated below Welcome Fred Gloggs My Profle Log Oss spiraTest Ex A C 0 100c2003 Fred Bloggs 1Dec2003 sad Fred Bloggs 1Dec 2003 Fred Bloggs 1 Dec 2003 Passed Fred Bloggs 1 Dec 2003 Fred Bloggs 1 Dec 2003 JoeP Sman 1Dec 2003 Fre Bloggs 1 Dec 2003 nsting author Sd JoeP Smith t Dec 2003 FredBloggs 1 Dec 2003 Ablity to reassign book to diferent author PaeEed JoeP Smah 1 Dec 2003 FredEloggs 1 Dec 2003 Regression Tests Posse 1 Dec 2003 JoeP Smith 1 Dee 2003 Scenario Tests Not Rum Joe P Smith Joe P Smith 1 Dec 2003 Exception Scenario Tests Not Rum Joe P Smith Joe P Smith 1 De 2003 gt Na Run Jos P Smith 1 Dec 2003 not ABE
26. ik lt HHEN Net Run Joe P Seth 11 Dec 2003 Copynght C 2006 infectra Corporation SpiraTest vt 0 inflectra The test case list consists of a hierarchical arrangement of the various test folders and test cases that the system being developed needs to be able to demonstrate The structure is very similar to the folder structure in Microsoft Windows Explorer and users will find this very familiar and intuitive to use When you create a new project this list will initially be empty and you will have to use the lt New Folder gt and lt New Test gt buttons to start adding test cases to the system The list consists of test folders shown with a folder icon and in bold type and test cases that are shown with a document icon and a hyperlink You can nest test folders and test cases under an existing test folder but you cannot nest anything under a test case All of the items in the list have a name together with the most recent execution status passed failed or not run and owner author execution date creation date and test case number In addition if you position the mouse pointer over the name of the test case folder a more detailed description is displayed as a tooltip Clicking on a test case s hyperlink will take you to the test case details page for the item in question see section 5 2 It is important to understand that only test cases are assigned a status themselves the test folders simply display a
27. ility to edt existing beaks in the ay oa Joug l a x ks in Ability to delete m sting hooks in the Available Test Cases Test Coverage tuo mca on ten cece Abibty to create new book Ability to associate books with diferen Ab ty to edt mosting book FR Abiity to aasociate books with diferen Ability to edt mosting author Ada gt Ability 10 completedy erase all books st Aoi 10 Seat Deel te Spend bi Author management Remove an Person loses dook and needs to re Adding new book and mathor to keran Doutie clicking on a covered test case will take you to the test case tsel Copyright C 2006 Infectra Corporation SpiraTest v1 0 i nflectra This page is made up of two areas the left pane is the navigation window and the right pane contains the requirements test coverage information The navigation pane consists of a link that will take you back to the requirements list as well as a list of the peer requirements to the one selected This latter list is useful as a navigation shortcut you can quickly view the coverage information of all the peer requirements by clicking on the navigation links without having to first return to the requirements list page The main right pane contains the test coverage information for the requirement in question The pane consists of two lists of test cases the one on the left being the hierarchical list of the test cases belonging to the project arranged in test folders denot
28. inflec ra wz This page is made up of two areas the left pane is the navigation window and the right pane contains the test case detailed information itself The navigation pane consists of a link that will take you back to the test case list as well as a list of the peer test case to the one selected This latter list is useful as a navigation shortcut you can quickly view the detailed information of all the peer test cases by clicking on the navigation links without having to first return to the test cases list page The main right pane can be switched between three different views by clicking the appropriate radio button Initially the pane will be in View Test Steps mode but it can be switched to View Test Runs and View Coverage modes if so desired Each of the views is described separately below 5 2 1 View Test Steps This view displays the name of the test case together with all the defined test steps that a tester would need to perform to verify that the functionality works as expected The list of test steps displays the position number the description the expected result some suggested sample data and the most recent execution status of the individual test step 5 2 2 Insert Step Clicking on the lt Insert Step gt button inserts a new test step before the currently selected by means of the radio button test step Clicking the lt Insert Step gt button without selecting a test step will insert a new step a
29. ity to create edit and delete project scope requirements in a hierarchical organization that resembles a typical scope matrix Each requirement is associated with a particular importance level ranging from critical to low and a status identifier that designates where the requirement is in the development lifecycle requested planned in progress and completed In addition each requirement is mapped to one or more test cases that can be used to validate that the functionality works as expected This mapping is called the Requirement Test Coverage since the test cases cover the requirement so that if all the tests can be executed successfully then the requirement is validated 2 2 Test Management SpiraTest provides the ability to create edit and delete project test cases that are stored in a hierarchical folder structure that resembles Windows Explorer Each test case consists of a set of test steps that represent the individual actions a user must take to complete the test These test steps also contain a description of the expected result and any sample data elements that the tester should use when performing the action When a user executes a test case the results are stored in a test run that contains the success failure status of each test step as well as the actual observed result that the tester experienced In addition each test case is mapped to one or more requirements that the test is effectively validating providi
30. m the bst below and chek Add You can use the Remove and Remove AS buttons to remove requeemerts that are no longer covered by the test case Available Requirements Requirements Coverage Abily to add mew books to the system Ability to edit existing books 1 TANE Absity to delete esting book Abthty to associate books wt Remove lt Ability to associate books wt Ability to associate books we AbiMy to completely erase al Remove an Ability to create doren edax t gt Deuble chcking on a covered reqarement will take you to the requirement itself The main right pane consists of two lists of requirements the one on the left being the hierarchical list of the requirements belonging to the project the summary items are denoted by their gray color The right box contains the list of requirements mapped to this test case Double clicking on items in this box will jump you to the requirements details screen for this requirement see section 4 2 To change the coverage for this test case you use the buttons Add Remove Remove All positioned between the two list boxes The lt Add gt button will move the selected requirements from the list of available on the left to the list of mapped on the right Similarly the lt Remove gt and lt Remove All gt buttons will remove either the selected or all the requirements from the right list box and add them back to the left list box Note that none of the chang
31. me assigned owner detection date and original detector In addition you can view a more detailed description of the incident along with a resolution if any by positioning the mouse pointer over the incident name hyperlink and waiting for the popup tooltip to appear If you click on the incident name hyperlink you will be taken to the incident details page described in section 6 2 Clicking on any of the pagination links at the bottom of the page will advance you to the next ten incidents in the list according to the applied filter and sort order 6 1 1 Sorting and Filtering You can easily filter and sort the list of incidents as illustrated in the screen shot below Welcome Fred Gleggs My Profle Leg Out spiraTest ibrary Information System gt Ie Hip Now incident 3 Delete Y Cioarfiters Refresh Database not backng up correcto 2Ho 2003 Cannot add y new book to the Fred Bloggs 1540 2003 aysiem Canos instal system on Oracle 24402003 Canos add a nea book to the Joe P Smath 44o0v2003 atom Validation on the eda book page Joe P Smath 15How 2003 Saaran handing Joe P Smah 15 Nov 2003 Quote handing sues throughout Fred Bloggs 15 Nov 2003 Editing the date on a book is Fred Bloggs 4tlor 2003 chrky The homepage hangs wtutst Fred Bloggs 1S Now2003 loa ng hy ck batina screen dosent 24l0v 2003 201 iaa ai pp 0000 e y if ooann i 11 2 ea gt To filter the list by incident type status priority owne
32. n aggregate of the worst case assessment of their children s status Also only test cases can be mapped against requirements for test coverage or have lists of associated test steps 5 1 1 New Test Clicking on the lt New Test gt button inserts a test case above the currently selected test case i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a new test case below an existing test case you need to select the test folder below it If you insert a new test case without first selected an existing item from the list the new test case will simply be inserted at the end of the list Once the new test case has been inserted the item is switched to Edit mode so that you can rename the default name and choose an owner and or author Note that all new test cases are initially set with an execution status of Not Run 5 1 2 New Folder Clicking on the lt New Folder gt button inserts a test folder above the currently selected test folder e the one whose check box has been selected at the same level in the hierarchy The new folder is automatically populated with a single default test case If you want to insert a new test folder below an existing test folder you need to select the test folder below it If you insert a new test folder without first selected an existing item from the list the new test folder will simply be inserted at the end of the list of test folders
33. nflectra When you click on any of the individual test runs in the list you are taken to the Test Run details page not to be confused with the Test Case details page This page lists all the steps of the test case as they appeared during the test run in question this means that if the test steps were changed after running the test the list here will reflect the original information Welcome Fred Bloggs My Profile Log Out Test Case Abiity to create new book Test Run 09900 Execution Date 1 Dec 2003 000001 User logs in to appkcation User taken to man menu scroen 000002 User clicks link to create book User taken to frst screen in mza 000003 User enters books name and author User taken to neat screen Macbeth Vilkam An error page is displayed No such object or with block then chcks Next in wzad Sharerpeare vanable at lee 4777 gt View Incatents Copyright C 2006 Infectra Corporation SpiraTest v1 0 Each test step is displayed along with the description expected result suggested sample data actual result and the execution status for this step in this particular test run Where the test step was listed as a Failure you will have an additional hyperlink View Incidents displayed This allows you to view any incidents that are associated with this particular test step failure Welcome Fred Gloggs My Profit Log Oss spiraTest ibrary information System gt Test Ca 000001 User logs in to app ca
34. ng the test coverage for the requirement During the execution of the test case each failure can be optionally used to record a new incident which can then be managed in the incident tracking module see below This provides complete traceability from a recorded incident to the underlying requirement that was not satisfied 2 3 Incident Tracking SpiraTest provides the ability to create edit assign track manage and close incidents that are raised during the testing of the software system under development These 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 Typically each incident is raised initially as a New item of type Incident Following the review by the project manager and customer they are changed to one of the other specific types given a priority critical high medium or low and status changed to Open Once it is assigned to a developer for fixing it is changed to status Assigned The developer now works to correct the incident after which time its status changes to Fixed or Not Reproducible depending on the actions taken or not taken Finally the project manager and customer verify that it has indeed been fixed and the status is changed to Closed SpiraTest provides robust sorting and filtering of all the incidents in the system as well as the
35. nged back from a summary item to a detail item 4 1 5 Refresh Clicking on the lt Refresh gt button simply reloads the requirements list This is useful as other people may be modifying the list of requirements at the same time as you and after stepping away from the computer for a short time you should click this button to make sure you are viewing the most current requirements list for the project 4 1 6 Edit Each requirement in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information 4 2 Requirement Details When you click on a requirement item in the requirements list described in section 4 1 you are taken to the requirement details page illustrated below Welcome Fred Bloggs My Profile Log Out Requirement Ability to associate books with different subjects Book Management The test coverage box m catos the test cases that are currently mapped agaist the requirement To add test cases to this requirement choose from the ist below and click Add You can use the Remove and Remove All buttons to remove tests that no longer cover the requirement Ab
36. nt Clicking on the View Details link at the top of the table simply brings up the project test case list see section 5 1 In addition to the bar chart there is a also a display of the total number of test runs recorded for the project and a list of the five most recent days of recorded test runs together with the daily count 3 5 My Profile When you click on either the My Profile link in the global navigation you will be taken to the page in the system that allows you to view and edit your personal profile Welcome Fred Bloggs My Profil Log Out Please rewew the eformabon lested below and make any changes if necessary Once you have finished click Update to confiem them Fira Name Fred Middle Initial Last Name User Name Copyright C 2006 inflectra Corporation SpraTest v1 0 inflec ra Z You can change your user information including your first name last name middle initial and user name The system will check to make sure that the user name is not already in use and warn you if this is the case Clicking the lt Update gt button will commit the changes whereas clicking lt Cancel gt returns you back to either Project Home or My Page depending on whether you have a project currently selected or not 3 5 1 Change Password In addition to being able to update your user information you can optionally change your password at the same time If you check the Change Password b
37. ow the information is related the following diagram illustrates the relationships between the different artifacts and entities 2 6 Application Site Map The following diagram illustrates overall application site map and how a user can navigate from one page to another PE With these overall concepts in mind the rest of this help manual will outline the functionality in each of the SpiraTest screens and provide specific information on how to manage each of the artifacts illustrated above Note that this manual does not explain the Administration level functionality of the system for that please refer to the SpiraTest Administration Guide 3 User Project Management This section outlines how you can log into SpiraTest view your personalized home page that lists the key tasks that you need to focus on and drill down into each of your assigned projects in a single dashboard view In addition to your personal homepage each of your projects has its own dashboard that depicts the overall project health and status in a single comprehensive view 3 1 Login Screen Upon entering the SpiraTest URL provided by your system administrator into your browser you will see the following login screen pm Please enter your user name Welcome to and password then click the log in button User Name cm m spiraTest Version v1 0 0 Copyright C 2006 Inflectra Corporation You need to enter your gi
38. ox when the lt Update gt button is clicked the system will expect you to have entered your old password and two instances of your new proposed password If the old password matches the one stored in the system and the two entries of the new password match then the system will update your password otherwise you will simply get a warning message indicating what needs to be corrected 4 Requirements Management This section outlines how the requirements management features of SpiraTest can used to develop a requirements scope matrix for a project and how you can map any existing test cases to the requirements Typically when starting a project developing the requirements list is the first activity after the Administrator has set up the project in the system 4 1 Requirements List When you click on the Requirements tab on the global navigation bar you will initially be taken to the requirements list screen illustrated below Welcome Fred Bloggs My Prefile Log Oss spiraTest Functional System Requirements Fred Bloggs 1 Dec 2003 Online Library Management System Fred Bloggs 1 Doc 2003 Fred Bloggs 1 Dec 2003 Fred Bloggs 1 Dec 2003 MIDE Fes Biggs 2 Oct 2006 Completos HE Fred Bloggs 1 Dec 2003 Completes MM Fres Bloggs 1 Dec 2003 Completes IT Fred Goggs 1 Dec 2003 a 3 Comptes MDE Fred Bloggs 1 Dec 2003 Abikty to completely erane all bo ed in the system with one chek Completes SBi N E Fred Boggs 1 De
39. r or detector name you simply choose an item from the appropriate drop down list and for the other fields you enter a free text phrase then click lt Filter gt to apply the different filters Note that the name field is searched using a LIKE comparison so that searching for database would include any item with the word database in the name The other freetext fields need to be exact matches e g dates incident numbers To change the column that is sorted or to change the direction of the current sort simply click on the up down arrow icon in the appropriate column The currently sorted column is indicated by the larger white arrow with the back border In the screen shot above we are filtering on type bug and sorting by decreasing priority 6 1 2 New Incident Clicking on the lt New Incident gt button takes you to the new incident screen This is essentially the same screen as the incident details screen shown in section 6 2 except that the lt Update gt button is replaced by an lt Insert gt button and some of the fields are disabled type status owner since all incidents are initially created as type incident and status new 6 1 3 Delete Clicking on the lt Delete gt button deletes the incidents whose check boxes have been selected in the incident list 6 1 4 Clear Filters Clicking on the lt Clear Filters gt button removes any set filters and expands the incident list to display all incidents for the
40. r this test case see section 5 2 and the project that the test case belongs to will be made your current project If you click on the Execute link listed in parenthesis it will actually launch the test case in the test case execution module see section 5 3 so that you can easily retest failed cases 3 2 3 My Open Incidents This section lists all the incidents you have been made owner of across all the different projects you are a member of This typically means that the project manager has assigned you to be responsible for resolving the incident In the case of a bug this can mean actually fixing the problem whereas for other incident types e g training item it may mean simply documenting a workaround In either event this section highlights the open incidents you need to manage ranked by importance priority and categorized by type with the open date displayed to give you a sense of the age of the incident Clicking on the incident name hyperlink takes you to the incident details page see section 6 2 that describes the incident in more detail and allows you to add new information or change its status to indicate actions taken In addition if you position the mouse pointer over the name of the incident a more detailed description is displayed as a tooltip 3 3 Global Navigation Regardless of the page you are on SpiraTest will always display the global navigation bar consisting of five section tabs My Page
41. riority Critical High Medium Low Closed Date Description Resolution Note that the mandatory fields are listed in bold type with asterisks Once you ve made the changes to the appropriate incident fields you can either click lt Update gt to commit the changes or lt Cancel gt to discard the changes and return back to the incident list 6 2 2 Inserting a New Incident If you are inserting a new incident only the following fields will be editable for you to fill in gt Name Detected By User Priority Critical High Medium Low Closed Date Description gt Resolution The reason for the limited number of editable fields is that all incidents are created as type Incident and status New so that they have to be formally reviewed assigned a type priority owner and status by the project manager Note that the mandatory fields are listed in bold type with asterisks Once you ve filled out the appropriate incident fields you can either click lt Insert gt to commit the new item or lt Cancel gt to discard the insertion and return back to the incident list 6 3 Incident Discovery Report When you click on the Incident Discovery Rate report from the Project Home dashboard see section 3 4 1 you will be taken to the incident discovery report for that project The incident discovery report displays the total number of incidents created and closed over a particular date range The report can either be displayed for th
42. rked as Passed any other case results in the test case being marked as Not Run The main pane displays the details of the current test step for the current test case As the tester you would read the description of the test step carry out the instructions on the system you are testing and then compare the results with those listed as expected As described below depending on how the actual system responds you will use the buttons on the page to record what actually happened If the expected results are indeed observed then you simply need to click the lt Pass gt button to mark the test step as passed and advance to the next test step This is illustrated in the screen shot below Welcome Fred Gleggs My Profle Log Out Please follow the Grections outined in the box below User clicks submit button Expected Result Confirmation screen is displayed Please enter the actual test resul it Giiers then click the appropriate button Actual Result O Log an incident for this step EE PAI Next ost Cancer Copyright C 2006 Infecira Conporation SpiraTest v1 0 inflectra z This will change the icon in the left hand navigation bar into a green square with a check mark in it Once all the test steps have passed you will now have the option of moving to the next test step by clicking the lt Next Test gt button if it is the last test case being executed the lt Finish gt button will be displayed instead
43. s Coverage This section consists of a bar graph that displays the aggregated count of requirements test coverage for the project The Passed Failed and Not Run bars indicate the total count of requirements that have tests covering them allocated across the execution status of the covering tests For example if a requirement is covered by four tests two that have passed one that has failed and one that has not yet been run the counts would be passed 0 5 failed 0 25 and not run 0 25 These fractional quantities are then summed across all the requirements to give the execution status breakdown of the covered requirements In addition to the three statuses for the covered requirements the fourth Not Covered bar depicts the total number of requirements that have no tests covering them putting the three other bars into perspective Typically a project is in good health if the Not Covered bar is zero and the count of Passed requirements is greater than Failed or Not Run The greatest risk lies with the Not Covered and Not Run status codes since the severity quantity of any bugs lurking within is not yet known If you position the mouse pointer over any of the four bars the color of the bar changes slightly and the underlying raw data is displayed as a tooltip together with the percentage equivalent Clicking on the View Details link at the top of the table simply brings up the project requiremen
44. section 3 4 it is a powerful tool for representing all the key risks and issues associated with a project in a single graphical format Unlike a standalone bug issue tracking tool however 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 This power is clearly illustrated in the Requirement Incident Count pane in the Project Home dashboard see section 3 4 4 6 1 Incident List When you click on the Incidents tab on the global navigation bar you will initially be taken to the incidents list screen illustrated below Welcome Fred Bloggs My Profile Log Out Library Information System gt Incidorts Sampie Risk 1 Sargis Fisk 2 Sergile Risk 3 Change Request Test Change Request Change Request Test Change Request Change Request Test Change Reques Change Request Test Change Reques Change Request Test Change Request Change Request tyt Charge Request Change Request Test Charge Request 2 00000500000 2 3 4 5 Gitto Copyright C 2006 infiectra Corporation SpeaTest vt 0 inflectra Z The incident list screen displays all the incidents entered for the current project in a filterable sortable grid The grid displays the incident number together with the incident type bug issue risk etc status new open etc priority na
45. t the end of the list The new test step will be set initially to Edit mode so that the description expected result and sample data fields will be editable allowing you to enter the appropriate data see section 5 2 7 5 2 3 Delete Clicking on the lt Delete gt button deletes the currently selected test step and reorders the test step position numbers to close the gap in numbering 5 2 4 Move Up Clicking on the lt Move Up gt button simply reorders the test step list so that the currently selected test step is one position higher up the list Note Attempting to move a test step above the top of the list will give a warning message 5 2 5 Move Down Clicking on the lt Move Down gt button simply reorders the test step list so that the currently selected test step is one position lower down the list Note Attempting to move a test step below the bottom of the list will give a warning message 5 2 6 Refresh Clicking on the lt Refresh gt button simply reloads the list of test steps This is useful if other people are making changes to the test list and you want to make sure that you have the most current version 5 2 7 Edit Each test step in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you
46. the system may not have detected the logout In this case the other user needs to log back in and then click the Log Out link 3 2 My Page Once you have successfully logged in you will initially be taken to your personalized home page called My Page Welcome Fred Bloggs My Prosie Log Out spiraTest My Page Project Home Requirements My Page MyProjcts My Ope Incidents AN Projects Project Name Web Site Creation Date Type Priority Date Opened Library Information System www libraryintormationsystem org 1 Dec 2005 Ability to associate multiple authors Enhancement 17 Nov 2003 Sample Application One www tempun org 1 Dec 2005 st Sy n Limitation 4 Dec 2003 Sample Application Two 1 Dec 2005 est Tra Training 3 Dec 2003 Bug 4 Now2003 i e in Training 3 Dec 2003 Name Status Last Executed Test Change Reque Change Request 7 Dec 2003 Ability to create new book Execute Passed 1 Dec 2003 ility to impor hom excel Enhancement 25 Nov 2003 Ability to edit existing book Execute Passed 1 Dec 2003 Test System Limitation Limitation 4 Dec 2003 Risk 10 Dec 2003 All Project Copyright C 2006 inflectra Corporation SpiraTeat vt 0 i nflectra Note that once you have successfully logged in and chosen a project SpiraTest remembers this selection and on subsequent log ins will automatically take you to that project s home page instead see section 3 4 below Your homepage contains all the information relevant to you
47. tion User taken to m n menu screen 000002 User clicks link to create book User takon to first screen in ward 000003 User enters books name and author User taken to next screen Macbeth Wiliam An error page is displayed Mo such object or with block then chicks Med in ward Shakespeare variable at line 473 gt View Incedents Incidents List for Step 000003 Test Run Stop 000003 Cannat add a new book to the system Jos P Smith dAor 2003 Copyright C 2006 infectra Corporation SpiraTest vt 0 inflectra Clicking on the link will change the background color of the test case to gray and display a list of all the associated test steps in a grid below the test step list Each of the incidents listed will reflect the most up to date information regarding that incident including its type status priority name assigned owner detection date and who first detected it Clicking on the incident number hyperlink will take you to the details page for that incident which is described in section 6 2 6 Incident Tracking This section outlines how the incident defect tracking features of SpiraTest can used to manage key project artifacts during the software development lifecycle Although the primary purpose of the incident tracker is to manage the defects raised during the execution of test cases in the test management module it is also a powerful risk issue bug tracking system in its own right When coupled with the project dashboard see
48. tions at the same time If for any reason you do try and log in to the system when you already have an active session in progress you will see the following screen Welcome to AT spiraTest we You can either Log Out and try a different user name or Sign Off The Other Locations to force the other Version v1 0 locations to log out Copyright C 2006 Inflectra Corporation inflectra You have two choices you can either click the Log Out link and try logging in as a different user or if you want to log off any other active sessions e g you closed the browser and the session is still listed as active simply click the Sign Off The Other Locations link and you will be logged in to the application Since SpiraTest is licensed to organizations for a specific number of concurrent users unless they have purchased an unlimited Enterprise license only a fixed number of users may be active at the same time So for example if an organization has a five 5 concurrent user license and a sixth user tries to log in they will be presented with the following screen Welcome to em spiraTest wee Return to Login page Version v1 0 Copyright C 2006 Inflectra Corporation inflectra This means that one of the other users who is already logged in needs to click the Log Out button so that one of the concurrent licenses is freed for your use If the user has logged out by closing the browser
49. ts list see section 4 1 3 4 4 Requirement Incident Count This section displays a count of the total number of incidents and the number of open incidents mapped against requirements in the system displayed in an indented list This section is useful for determining the parts of the application that have the most instability as you can look at the requirements that have yielded the greatest number of incidents Clicking on any of the requirements hyperlinks will take you to the detail page for the requirement in question see section 4 2 3 4 5 Top Open Issues This section displays a breakdown of the top five issues logged against the project in order of decreasing priority Note that items not given a priority are listed at the top since critical issues could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the issue item hyperlink will take you to the incident details page for the issue in question see section 6 2 3 4 6 Top Open Risks This section displays a breakdown of the top five risks logged against the project in order of decreasing priority Note that items not given a priority are listed at the top since critical risks could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the risk item hyperlink will take you to the incident details page for the risk in question see section 6
50. ven user name and password into the system in the appropriate boxes then click the lt Log In gt button to gain access to the application Normally you only remain logged in to the application whilst in active use and you will be asked to log in again after either closing the browser or 20 minutes of inactivity To prevent this and stay logged in to SpiraTest regardless of browser window closing or inactivity select the Remember Me check box before clicking the lt Log In gt button Note that this setting is specific to each individual computer you are logging in from and that it will be reset when you explicitly log out with the log out link described in more detail in section 3 3 If for any reason you are unable to login with the provided username password combination and error message will be displayed If you cannot remember the correct log in information click on the Forgot user name password link and your password will be emailed to the email address currently on file If you don t have an SpiraTest account setup clicking on the Don t have an account link will take you to a form that you need to fill in which will be forwarded to the system administrator who will actually create your account In addition the system will prevent you logging on to the system with the same username at the same time on multiple computers This is to avoid the system getting confused by a user trying to make contradictory ac
Download Pdf Manuals
Related Search