Home

SpiraTest User Manual Version 1.5 Inflectra Corporation

Contents

1. Clicking on any of the expand links in the left hand table of contents will open up the detailed list of topics for each of the main areas of the system In each area clicking on one of the individual links will open 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 3 3 Choose Project Choosing a project from the list of your assigned projects in the drop down menu allows you to quickly and easily jump between projects regardless of the page you happen to be on When you choose a project you will be taken to the home page for that project which is described in section 3 4 below 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 Welcome Fred Bloggs My Profile Log Out My Page Project Home Requirements Releases Test Cases Incidents spiraTest Library Information System gt Project Home Role Manager Library Information System PR000001 Display data for Project Overview Sample application that allows users to manage books authors and lending records for a typical Description Priority Date Opened branch library Cannot install system on Windows ME 1 Dec 2003 Owner s System Administrator Ability to be accessed
2. 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 box 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 Note If your SpiraTest user profile is linked to an account stored in an external LDAP server you may find the change password option is disabled This is because the system uses the password held in the external server To change the password in this case please contact your system administrator who will be able to help you change the password in your LDAP environment 4 Requirements Management This section outlines how the requirements manage
3. Ability to associate books with different editions ET Completed RQ000009 Ability to completely erase all books stored in th ET Completed RQ000010 mean Edition Management Not Covered In Progress RQ000011 Author Management Not Covered In Progress RQ000013 Subject Management Not Covered Planned RQ000019 Administration Functions Not Covered Requested RQ000022 ap inset 3 Delete c gt indent lt Outdent 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
4. Edi Ability to edit existing books in the system BEE Completed RQ000005 Edit Ability to delete existing books in the system bE Completed RQ000006 i Ability to associate books with different subjects ERB B Bw Completed 1 0 RQ000007 Edit Ability to associate books with different authors Be Completed 1 0 RQ000008 Edit Ability to associate books with different editions B ee Completed 1 0 RQ000009 Ability to completely erase all books stored in th Bo Completed RQ000010 Edit Edition Management In Progress RQ000011 Author Management In Progress RQ000013 Edit Subject Management Planned RQ000019 Edit Administration Functions Requested RQ000022 Edit Choose the destination location for the copied moved requirements by selecting the checkbox of the requirement you want to copy move in front of and then clicking the Paste Requirements link If you want to copy move the requirements to the end of the list you just click the link without selecting a destination To abort the copy or move all you need to do is click the Cancel link and the operation will be aborted Note that copied requirements will also include the test coverage information from the originals 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 E p9 Welcome Fred Bloggs My Profle Log Out Library
5. s status Also only detail items can be mapped against test cases for test coverage thus only they have 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 its completion status from Requested to Completed the version of the software that the requirement is planned for and 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 re
6. 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 O http sandman section 4 1 Requirements List SpiraTest Online Help Windows Internet Explorer Table of Contents 4 1 Requirements List 1 Introduction 2 Functionality Overview 3 User Project Management 4 Requirements Management 4 1 Requirements List 4 1 1 insert 4 1 2 Delete 4 1 3 Indent anwar Aaa Sevens See rerrenes 4 1 4 Outdent et eS ee aat 4 1 5 Refresh 4 1 6 Edit 4 1 7 Show Level 4 1 8 Filtering 4 1 9 Copying and Moving 4 2 Requirement Details 4 2 1 View Coverage 4 2 2 View Attachments When you click on the Requirements tab on the global navigation bar you will initially be taken to the requirements list screen illustrated below 5 Test Case Management 6 Incident Tracking 7 Release Management 8 Reports Center td ome pmnan lt Onm The renitiramentec lict rnncicte nf a hicrarchical arrannament nf tho varinuce ranitiramante and lt m
7. Book Management This document outlines the functional specification for the book Fred 5 2 2006 12 00 00 Functional Spec doc management part of the library management system Bloggs AM Graphical Design Joe P 5 1 2006 12 00 00 Mockups psd Smith AM Book Management Screen Joe P 3 2 2005 12 00 00 Wireframe ai Smith AM Requirement Change History 6 2 2006 12 00 00 AM status In Progress Completed Fred Bloggs 3 4 2005 12 00 00 AM status Requested In Progress Joe P Smith 8 2 Test Case Reports 8 2 1 Printable Test Scripts This printable report is useful when you want to be able to conduct the testing activities offline on paper or when testers need paper copies of the test script in addition to using the online test execution wizard In either case this report simply displays all of the test cases defined for the current project in the order they appear in the test case list together with their detailed test steps and a list of any attached documents gt Print Report Printable Test Scripts Folder 1 Functional Tests Call Login to Application User clicks link to create book User taken to first screen in wizard User enters books name and author then Dee Rae eee Ree mane Macbeth William i D User taken to next screen in wizard T clicks Next Shakespeare User chooses book s genre and sub genre from User sees screen displaying all entered list information Play Tragedy 5 User clicks submit button Confirmation scree
8. see 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 Requirements Releases Test Cases Incidents spiraTest Library Information System gt Incidents Role Manager ap New Incident 3 Delete Refresh Show hide columns Y ApplyFilters YY Clear Fitters V inc AY Wome AY Typo AY StatusaY Priory AY DotectedByAY Owned By aY Closed On AY eam E ay AO a ea 1N000061 Sample Risk 3 Risk Assigned Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith 11 Dec 2003 Fred Bloggs Joe P Smith 10 Dec 2003 Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Fred Bloggs Joe P Smith 7 Dec 2003 Joe P Smith Fred Bloggs Fred Bloggs Joe P Smith Joe P
9. 1 SP1 1 1 1 0 30 Nov 2004 Joe P Smith RLO00005 Library System Release 2005 1 2 0 0 1 Apr 2005 Fred Bloggs Yes RLOO0006 dh Insert 3 Delete D Indent lt a Outdent To filter the list by any of the displayed columns you either choose an item from the appropriate drop down list or enter a free text phrase depending on the type of field 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 release numbers In the screen shot above we are filtering on Active Yes Clicking on lt Clear Filters gt clears all the set filters and displays all the releases for the project 7 1 2 Insert Clicking on the lt Insert gt button inserts a release above the currently selected release i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a release below a summary item you need to insert it first then indent it with the lt Indent gt button If you insert a release without first selected an existing release from the list the new release will simply be inserted at the end of the list Once the new release has been inserted the item is switched to Edit mode so that you can change the default name active flag version number and creator 7 1 3 Delete Clic
10. Description The attachment list includes the filename that was originally uploaded together with the file size in KB name of the person who attached it and the date uploaded In addition if you position the pointer over the filename and hold it there for a few seconds a detailed description is displayed as a tooltip To actually view the document simply click on the filename hyperlink and a new web browser window will open Depending on the type of file this window will either display the document or prompt you for a place to save it on your local computer To delete an existing attachment from an incident simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the incident you need to click the Browse button and select the file from your local computer optionally enter a detailed description then click the lt Update gt button The document will be copied from your computer and attached to the incident Note If you are using a non Windows computer e g Macintosh that doesn t put file extensions on filenames e g xls for an Excel sheet automatically then you will need to manually add the file extension to the filename before uploading if you want it to be displayed with the correct icon in the attachment list 6 2 6 History In this mode the main pane displays the list of changes that have been performed on the incident artifact since its creation An examp
11. If you have not configured any releases for the project then the release drop down list will be disabled and the test runs incidents will not be associated with any particular release Once you have chosen the appropriate release name and or custom properties click the lt Submit gt button to begin executing test steps Welcome Fred Bloggs My Profile Log Out Liprary Mormation System v Help spiraTest My Page Project Home Requirements Releases Test Cases Incidents Library Information System gt Test Cases gt Test Case Execution Role Manager lt lt Back to Test List Curent TestCase Ability to create new book Select a __ Ability to create new book TC2 Please follow the directions outlined in the box below M1 1C16 Step 1 User opens up browser and enters application URL heep wew libraryinformationsystem com beta TC17 Step 2 TC2 Step 2 _ Tc2 Step 3 Ste Semple Data E Tc2 Step 4 The browser loads the login web page hetp wer libraryinformationsystem c a om beta LJ TC2 Step Plesse enter the actual test result if it differs then click the appropriate button Actual Result E Leg an incident for this step Lo l The screen is divided up into four 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 dire
12. Remove gt and lt Remove All gt buttons will remove either the selected or all the releases from the right list box and add them back to the left list box 5 2 6 Attachments In this mode the main pane displays the list of documents that have been attached to the test case The documents can be in any format though SpiraTest will only display the icon for certain known types Test Steps Req Coverage Custom Props Test Runs History T Sequence Diagram for Book Mat_pdf 10 KB Fred Bloggs 3 May 2006 Upload New Attachment Filename Description S O The attachment list includes the filename that was originally uploaded together with the file size in KB name of the person who attached it and the date uploaded In addition if you position the pointer over the filename and hold it there for a few seconds a detailed description is displayed as a tooltip To actually view the document simply click on the filename hyperlink and a new web browser window will open Depending on the type of file this window will either display the document or prompt you for a place to save it on your local computer To delete an existing attachment from a test case simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the test case you need to click the Browse button and select the file from your local computer optionally enter a detailed description then click the lt Uplo
13. Smith Fred Bloggs IN000060 Sample Risk 2 Risk Open IN000059 Sample Risk 1 Risk Open IN000057 Test Change Request Change Request Duplicate INO00056 Test Change Request Change Request Closed INO00055 Test Change Request Change Request Closed INO00054 Test Change Request Change Request Assigned IN000053 Test Change Request Change Request Assigned IN000052 Test Change Request Change Request Open IN000051 Test Change Request Change Request Open INO00050 Test System Limitation Limitation Duplicate IN000049 Test System Limitation Limitation Closed IN000048 Test System Limitation Limitation Assigned IN000047 Test System Limitation Limitation Assigned IN000046 Test System Limitation Limitation Assigned Displaying 1 15 of 60 incidents Show 15 rows per page 1 2 3 4 Next gt 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 fields such as incident type bug issue risk etc status new open etc priority name assigned owner detection date detector closed date etc The choice of columns displayed is configurable per user per project giving extensive flexibility when it comes to viewing and searching incidents In addition you can view a more detailed description of the incident along with a resolution if any by positioning the mouse pointer ov
14. TRO00001 Test Case 1C000002 Estimated Duration 10 minutes Release 1 0 0 0 Actual Duration 75 minutes Execution Date 12 1 2003 10 45 20AM Execution Status Failed Tester Name Joe P Smith Test Run Type Manual Custom Properties This page consists of three panes gt The left hand navigation pane displays a list of the last fifteen 15 runs gt The main pane displays the details of the test run itself name description estimated and actual duration tester name test run type etc gt The tab control displays the list of test run steps populated if a manual run executed by a user the stack trace populated if an automated run executed by an automated testing tool such as NUnit JUnit etc and any custom properties set for the run 5 4 1 Test Run Steps In the case of a manual test run this tab displays 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 Stack Trace Custom Properties RS000001 User logs in to application User taken to main menu screen RS000002 User clicks link to create book User taken to first screen in wizard RS000003 User enters books name and author User taken to next Macbeth William An error page is displayed No such object or with then clicks Next screen in wizard Shakespeare block variable at line 473 gt View Incident
15. ae ouecaae Test System Limitation Library Information System Limitation 4 Dec 2003 Ability to edit existing book Library Information 1 Dec 2003 Sample Risk 3 Library Information System Risk 10 Dec 2003 gt Execute System Copyright C 2006 2007 Inflectra Corporation SpiraTest v1 5 i n flectra 2 Note that once you have successfully logged in and chosen a project SpiraTest remembers this selection and on subsequent log ins will automatically select that project and highlight it for you in the My Projects list see 3 2 1 below Your homepage contains all the information relevant to you 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 c
16. and test case icon e g Call Login to Application in the screen shot above are in fact linked test cases Linked test cases are a useful way of reusing existing test steps from other test cases For example if you want to have a set of steps be in more than one test case e g a login step then you would create a separate test case just containing these steps then have all the other test cases just link to it This avoids the need to have duplicate test steps throughout the project 5 2 1 1 Insert Step Clicking on the lt Insert Step gt button inserts a new test step before the currently selected by means of the check box test step Clicking the lt Insert Step gt button without selecting a test step will insert a new step at the end of the list All test steps are displayed in Edit mode so the description expected result and sample data fields are editable allowing you to enter the appropriate data see section 5 2 7 In addition to the existing test steps the system always displays five blank test steps so that it is easy and quick to enter large numbers of test steps Upon entering up to five test steps and clicking the lt Update gt button five new blank rows will be added at the bottom of the list 5 2 1 2 Insert Link Clicking on the lt Insert Link gt button brings up the following panel that allows you to choose the test case to be inserted Req Coverage Custom Props Test Runs History Choose the t
17. by Mozilla 1 Dec 2003 Web Site wow libraryinformationsystem org Management of children s loans 1 Dec 2003 FRc rase ts SUT SV LUIS NNN _Svstem may require process changes 3 Medium 1 Dec 2003 Status 1 Critical 2 High 3 Medium 4 Low None TOTAL 3 1 2 Requested Planned In Progress Completed TOTAL Description Priority Date Opened Sample Risk 1 10 Dec 2003 Sample Risk 2 10 Dec 2003 Sample Risk 3 Banm 10 Dec 2003 oo l IN IO In amp ja ja ja Status 1 Critical High 3 Medium r Low None TOTAL temo Assigned 5 Closed 2 Duplicate New Not Reproducible Open Failed Blocked Caution Not Run Not Covered Reopen Resolved TOTAL N iw Bia io B 1 ia 1m B S _ D ia 11 Roqukoment ei Cost _ na Name Open Total Functional System Requirements Online Library Management System Book Management Daily Run Count Ability to add new books to the system gt 12 5 2007 1 Ability to associate books with different subjects gt 12 1 2003 11 Ability to associate books with different editions Ability to completely erase all books stored in the system with one click Edition Management Failed Passed Not Run Blocked Caution Author Management Ability to add new authors to the system Subject Management Administration Functions Data Import Functionality Ability to create new users in the system TOTAL Total Runs 12 This page summarizes all of the information regardin
18. case cases it will display an aggregate status for all releases of the project e the test list will include all the test cases in the system regardless of which release they apply to and the execution status will reflect the most recent test run regardless of which release it was for To change the test case list to just display test cases and execution status for a particular release simply change the release selected in the drop down list located below the toolbar on the right hand side from Any to a specific release Welcome Fred Bloggs My Profile Log Out Test Cases Incidents Show hide columns Y Gear Fitters Display data for 1 0 1 0 Library System Release 1 SP1 A spiraTest Project Home Requirements Releases Library Information System gt Test Cases Role Manager db New Test db New Folder 3 Delete gt Execute Ch Copy Ch Move Refresh Displaying 5 out of 7 test case s for this release 1 Dec 2003 amp Functional Tests 5 Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith T Ability to create new book T Ability to edit existing book T Ability to create new author D Ability to edit existing author T Ability to reassign book to different author Regression Tests 2 amp Scenario Tests 0 amp Exception Scenario Tests 0 amp Common Tests 0 Joe P Smith Joe P Smith dh New Test db New Folder 3 Delete gt Exec
19. changed to Closed SpiraTest provides robust sorting and filtering of all the incidents in the system as well as the 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 Release Management SpiraTest provides the ability to track different versions releases of the application being tested Ea
20. depend on how your project administrator has setup the system for you Administrators should refer to the SpiraTest Administration Guide for details on configuring the incident workflows to meet their needs 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 creating a new incident the fields that are available and the fields that are required will depend on how your project has been for configured For example some projects may require that all incidents be started with Status New and Type lIncident others may allow you to specify the incident type The types of change allowed will depend on how your project administrator has setup the system for you Administrators should refer to the SpiraTest Administration Guide for details on configuring the incident workflows to meet their needs 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 2 3 General In this mode the lower section of the screen displays the detailed description of the incident together with any recorded resolution Custom Properties Attachments History Description The latter text box is optional for certain stages of the
21. experienced In addition each test case is mapped to one or more requirements that the test is effectively validating providing 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
22. incident workflow and can be used to enter guidance to the development team suggestions for resolving the bug issue etc 6 2 4 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for incidents To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Assuming that custom properties have been defined for your project you will see a list of optional parameters that can be set on the incident These can be either freetext or drop down lists In the example below you can enter Notes and or the Operating System that the incident was observed on General Attachments History Please edit the following custom properties of this artifact and click Update when finished Notes May be an array bounds issue r Operating System Windows XP Once you are satisfied with the values for the custom properties simply click Update to commit the changes 6 2 5 Attachments In this mode the lower section of the screen displays the list of documents that have been attached to the incident The documents can be in any format though SpiraTest will only display the icon for certain known types General Custom Properties History W Error Stacktrace doc 1 500 KB Fred Bloggs 1 May 2006 Web Page capture htm 120 KB Fred Bloggs 25 Apr 2006 Upload New Attachment Filename Browse
23. is stored on a per project basis so you can have different display settings for each project that you are a member of The fields can be any of the built in fields or any of the custom properties set up by the project owner 5 1 8 Filtering You can easily filter the list of test cases as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out Project Home Requirements Releases Test Cases spiraTest S Library Information System gt Test Cases Role Manager cp New Test Gp New Folder 3 Delete gt Execute ShowLevel QjCopy yMove Ry Refresh Show hide columns _v Y Clear Filters Display data for All Releases hd Displaying 6 out of 8 test case s for this release Owner Last Executed 12012003 Functional Tests 5 Fred Bloggs i Ability to edit existing book Fred Bloggs Joe P Smith T Ability to edit existing author Joe P Smith Ability to reassign book to different author Joe P Smith amp Regression Tests 2 BBE ERS 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Tc000001 Ped Tc000003 p Edit Tco00004 Beat Tc000005 Meg Tc000006 meae Tc000007 Pen amp Common Tests 2 BREE 1 Dec 2003 Fred Bloggs Tc000015 P Edt Open Up Web Browser 1 Dec 2003 Fred Bloggs Tc000016 Peat o Login to Application 1 Dec 2003 Fred Bloggs TC00001
24. page for each report differs slightly but the general format is illustrated below Requirements Coverage Report Please choose from the various options below to specify how you would like this report to appear You can filter the results displayed by various parameters as well as choose which elements of the report are displayed HTML Narrative Format MS Word Narrative Format w HTML Tabular Format MS Excel Tabular Format E AEN AEN ION AN my O O WH F List of Attached Documents E Artifact Change History Test Case Coverage Targeted Release Importance Status Author Created On Last Updated You can configure each of the reports in the following ways gt Report Format This allows you to specify the display format of the report The is a distinction between a narrative report in which the data is presented as a written report suitable for printing and a tabular report in which the data is presented as a data grid that is best used for charting and analyzing The narrative reports can be displayed either as a web page HTML or downloaded as a Microsoft Word document The tabular reports can be displayed either as a web page HTML or downloaded as a Microsoft Excel spreadsheet gt Report Elements This allows you to determine which types of information to include in the report This varies by report type but includes the dependent items related to the artifact being reported on atta
25. 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 Welcome Fred Bloggs My Profile Log Out L rary Information System Project Home Requirements Releases Test Cases spiraTest Library Information System gt Test Cases gt Test Case Execution Role Manager lt lt Back to Test List Current Test Case Select lt M Ability to create new book TC2 Please Choose the Release To Execute Against TC16 Step 1 E TC17 Step 2 Release 1 0 0 0 Library System Release 1 Md TC2 Step 2 C TC2 Step 3 TC2 Step 4 Notes TC2 Step 5 7 TC2 Step 6 E TC2 Step 7 Web Browser Operating System None Now enter the following properties for this test run Before actually executing the test scripts you need to select the release of the system that you will be testing against and any test run custom properties that have been defined by the project owner This ensures that the resulting test runs and incidents are associated with the correct release of the system and that the test runs are mapped to the appropriate custom properties e g operating system platform browser etc
26. the built in fields or any of the custom properties set up by the project owner 4 1 10 Copying and Moving To copy or move a release or set of releases simply select the check boxes of the releases you want to copy or move and then click either lt Copy gt or lt Move gt as appropriate Upon clicking the button the rows you selected will be marked in bold with a light yellow background and the screen will prompt you to choose the destination for the copy move Welcome Fred Bloggs My Profile Log Out Library Information System X spiraTest Project Home Requirements Releases Incidents Library Information System gt Releases dh inset 3 Delete o indent lt Outdent ShowLewel copy MhmMowe Refresh Showihide columns ov Release Name O O lt OOOO O Version Created On Creator Active Release ID o lt Any X E Library System Release 1 1 0 0 0 Library System Release 1 SP1 1 0 1 0 Library System Release 1 SP2 1 0 2 0 Library System Release 1 1 1 1 0 0 1 1 1 0 1 1 2 0 1 2 0 0 Library System Release 1 1 SP1 Library System Release 1 1 SP2 A 15 Feb 2004 5 May 2004 5 Jun 2004 15 Oct 2004 30 Nov 2004 5Jan 2005 1 Apr 2005 Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Fred Bloggs Any X R RL000001 RL000002 RL000003 RL000004 RL000005 RL000007 RL000006 gt Fiter Edit Choose the destination location
27. 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 Finally as a shortcut you can click the Create Requirement from This Test Case link to create a new requirement in the list of covered requirements that will be automatically linked to this test case This is useful when you have created a new test case and want to generate an initial placeholder requirement to be fleshed out later 5 2 3 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for test cases To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Assuming that custom properties have been defined for your project you will see a list of optional parameters that can be set on the test case These can be either freetext or drop down lists In the example below you can enter a URL and or Test Type Test Steps Req Coverage Test Runs Attachments History Please edit the following custom properties of this artifact and click Update when finished URL http www libraryreferences org Test Type Once you are satisfied with the values for the custom pr
28. 7 F Edit dh New Test db New Folder 3 Delete gt Execute To filter the list by any of the displayed columns you either choose an item from the appropriate drop down list or enter a free text phrase depending on the type of field 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 test case numbers In the screen shot above we are filtering on Execution Date 01 Dec 2003 5 1 9 Copying and Moving To copy or move a test case or test folder simply select the check boxes of the test cases folders you want to copy or move and then click either lt Copy gt or lt Move gt as appropriate Upon clicking the button the rows you selected will be marked in bold with a light yellow background and the screen will prompt you to choose the destination for the copy move Welcome Fred Bloggs My Profile Log Out Library information System spiraTest Requirements Releases Test Cases Incidents Library Information System gt Test Cases dp New Test cpNewFolder 3 Delete gt Execute ShowLevel Mhcopy GyMove Refresh Showhide columns v Displaying 6 out of 10 test case s for this release Display data for All Releases oe LamBoaed Maor O aede Dadan TeS Cy Ay B Ay a o F
29. B Functional Tests 4 Fred Bloggs 1 Dec 2003 Fred Bloggs TC000001 T Ability to create new book E Fred Bloggs Ability to edit existing book Fred Bloggs T Ability to edit existing author _ Joe P Smith D Ability to reassign book to different author EET Joe P Smith F O Regression Tests 2 Bo Do 80 Scenario Tests 2 Joe P Smith B6 Common Tests 2 Bow Y Open Up Web Browser T Login to Application 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs 10 5 5 8 TC000002 TC000003 TC000005 TC000006 TC000007 Pedi TC000010 TC000015 TC000016 TC000017 dp NewTest pNewFolder 3 Delete gt Execute Choose the destination location for the copied moved test cases folders by selecting the checkbox of the test case folder you want to copy move in front of and then clicking the Paste Test Cases link If you want to copy move the test cases folders to the end of the list you just click the link without selecting a destination To abort the copy or move all you need to do is click the Cancel link and the operation will be aborted Note that copied test cases folders will also include the requirements coverage and test step information from the originals 5 1 10 Viewing the Test Status for a Release By default when you view the list of test
30. History Available Test Cases Test Coverage Functional Tests Ability to create new author Regression Tests Ability to create new book Scenario Tests Ability to edit existing author Exception Scenario Tests Ability to edit existing book Person loses book and needs to reportloss Ability to reassign book to different autt Adding new book and author to library ana Author management Common Tests EE Book management Open Up Web Browser Login to Application The test coverage box indicates the test cases that are currently mapped against the release To add test cases to this release choose from the list above and click Add You can use the Remove and Remove All buttons to remove tests that no longer cover the release Double clicking on a covered test case will take you to the test case itself The test case mapping section consists of two lists of test cases the one on the left being the hierarchical list of the test cases belonging to the project that are not currently mapped to this release The right box contains the list of test cases currently mapped to this release Double clicking on items in this box will jump you to the test case details screen for this requirement see section 5 2 To change the test case mapping for this release 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 avai
31. ach change was made together with the fields that were changed the old and new values and the person who made the change This allows a complete audit trail to be maintained of all changes in the system 5 Test Case Management This section outlines how the use case test case management features of SpiraTest can be 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 the 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 Then the list of use cases is developed to outline the key scenarios that need to supported to implement the requirement 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 Bloggs My Profile Log Out Requirements Releases Test Cases Incidents copy GyMove amp Refresh Y Clear Filters Display
32. ad gt button The document will be copied from your computer and attached to the test case Note If you are using a non Windows computer e g Macintosh that doesn t put file extensions on filenames e g xls for an Excel sheet automatically then you will need to manually add the file extension to the filename before uploading if you want it to be displayed with the correct icon in the attachment list 5 2 7 View History In this mode the main pane displays the list of changes that have been performed on the test case artifact since its creation An example test case change history is depicted below Test Steps Reg Coverage Custom Props Test Runs Attachments 5 2 2006 12 00 00 AM Need to create new book Ability to create new book Fred Bloggs 3 4 2005 12 00 00 AM Fred Bloggs Joe P Smith The change history displays the date that each change was made together with the fields that were changed the old and new values and the person who made the change This allows a complete audit trail to be maintained of all changes in the system 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
33. agement incident tracking and project user management 2 1 Requirements Management SpiraTest provides the ability 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 ina 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
34. ange 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 If the actual results differ from those expected you need to enter a description of the result observed and click the lt Fail gt lt Blocked gt or lt Caution gt button this is illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out Library information System v Help spiraTest My Page Project Home Requirements Releases Test Cases Library Information System gt Test Cases gt Test Case Execution Role Manager lt lt Back to Test List Current TestCase Ability to edit existing author Pi XX Ability to edit existing author TC5 Please follow the directions outlined in the box below User opens up browser and enters application URL TC16 Step 1 x p Ihnttp wew libraryinformationsystem com beta _ 1C17 Step2 _ IC5 Step 2 C TCS Steo 3 Lj Ien Stee Sample Data he browser loads the login web page a heep wew libraryinformationsysten c om beta Plesse enter the actual test result if it differs then click the appropriate button Actus Result The screen Gsplays a 404 error rressage Log an incident for this step Name Priority 4 Critical Opera
35. c login to application test case that others call as an initial step which could be provided with different login information depending on the calling test case To view change the parameters associated with the current test case click on the lt Parameters gt icon in the toolbar and the list of current parameters will be displayed Req Coverage Custom Props Test Runs Attachments The following parameters have been defined for this test case login Copy To Clipboard Delete password Copy To Clipboard Delete Add a new parameter to this test case tamet oo Default Value The list of existing parameters is displayed in a grid followed by the option to add a new parameter and default value used when the test case is run directly rather than being called by another test case You can delete an existing parameter and also copy the parameter token to your computer s clipboard The latter option is useful so that you can insert the parameter token in the format parameter name in the test step description expected result or sample data fields and have it converted into the parameter value during test execution 5 2 2 Requirements Coverage This view displays the name of the test case together with the requirements coverage information for the test case in question Test Steps Custom Props Test Runs Attachments History Available Requi uirements Coverage Functional System Requirements Abilit
36. ch project in the system can be decomposed into an unlimited number of specific project releases denoted by name and version number Requirements and Test Cases developed during the design phase can then be assigned to these different releases When a tester executes a series of test cases they are able to choose the version of the project being tested and the resulting test run information is then associated with that release In addition all incidents raised during the testing process are associated with this release allowing the development team to easily determine which version of the project is affected Finally as the incidents are resolved and verified during the testing phase the appropriate release can be selected to indicate which release the incident was resolved and or verified in 2 6 Miscellaneous 2 6 1 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 how the information is related the following diagram illustrates the relationships between the different artifacts and entities Role Project Requirement Release Incident Test Coverage Pi f ri Test Mapping Test Step Test Run Step With these overall concepts in mind the rest of this help manual will outline the functionality in each of the SpiraTest screens a
37. chments test steps coverage history etc gt Report Filters This allows you to constrain the range of data being reported on based on the various fields associated with the artifact in question These filters are typically selections from drop down lists and date ranges Once you have selected the format elements and filters clicking the lt Create Report gt button launches the report in a new window Each of the reports is now briefly described below 8 1 Requirements Reports 8 1 1 Requirements Coverage Report This printable report displays all of the requirements defined for the current project in the order they appear in the requirements list For each individual requirement the name priority author status and coverage status are displayed along with tables containing the list of covering test cases attached documents and the change history The ability to add new books into the system complete with ISBN publisher and other related information Priority 1 Critical Status Completed Author Fred Bloggs Creation Date 12 1 2003 12 00 00 AM Coverage 3 Covering 0 Failed 2 Passed Last Modified 12 1 2003 12 00 00 AM Targeted Release 1 0 0 0 URL http www libraries org Difficulty Moderate Requirement Type Requirement Test Coverage 2 Ability to create new book Passed 12 1 2003 12 00 00 AM 13 Adding new book and author to library Not Run a Book management Passed 12 1 2003 12 00 00 AM Attachment List
38. ctly 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 gt 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 yellow Blocked orange Caution 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 Blocked or Caution then the overall test case is marked with that status if a the test steps passed then the overall test case is marked as Passed any other case results in the test case being marked as Not Run gt 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 sys
39. d simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names This is stored on a per project basis so you can have different display settings for each project that you are a member of The fields can be any of the built in fields or any of the custom properties set up by the project owner 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 Welcome Fred Bloggs My Profile Log Out Library information System Help spiraTest My Page Project Home Requirements Releases Test Cases Incidents Reports Library Information System gt Incidents gt Incident Details Role Manager lt lt Back to Incident List incident IN 7 i gt Find Mi R Refresh Name Type Bug Detected By Joe P Smith Status Assigned Detected In Release 1 0 0 0 Library System Release 1 Test Run Step RS000003 Resolved In Release 1 0 1 0 Library System Release 1 SP Priority 1 Critical Seventy 3 Medium Owned By Joe P Smith m Detected On 4 Nov 2003 Last Modified 1 Dec 2003 History 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 backgro
40. data for spiraTest Library Information System gt Test Cases db New Test dbh NewFolder 3 Delete gt Execute ShowLevel Displaying 9 out of 11 test case s for this release Y Teame tn int Owner Lam ned abor O Aee O Te lt Any a remer a Aay d oef amp amp Functional Tests 5 g Ability to create new book YH Ability to edit existing book g Ability to create new author g Ability to edit existing author g Ability to reassign book to different author amp Regression Tests 2 B Scenario Tests 2 amp Exception Scenario Tests 1 T Person loses book and needs to report loss Adding new book and author to library Common Tests 2 Y Open Up Web Browser Y Login to Application dP New Test qp New Folder 3 Delete gt Execute Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith 1 Dec 2003 5 Dec 2007 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 41 Dec 2003 1 Dec 2003 Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs TC000001 TC000002 TC000003 TC000004 TC000005 TC000006 TC000007 TC000010 TC000011 TC000012 TC000013 TC000015 TC000016 TC000017 The test case list consists of a hierarchical arrangement of the various test folders and t
41. dent priority The report can either be displayed for a 60 day interval on a daily basis or for a 12 month interval of a weekly basis The screen shot below illustrates the discovery report loaded with the past 60 days of cumulative incident count data depicted on a daily basis AGE Tit Welcome Fred Bloggs My Profile Log Out Lerary information System v Help SP iraTest My Page Project Home Requirements Releases Test Cases Incidents Reports Library Information System gt Reports gt Open Incident Count By Priority Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Priority Chart Tumaround Time By Priority Chart Incident Type All Date Interval Daily Weekly Date Ending 6 10 2007 midlyyyy gt Filter Open Incident Count By Priority 1 Critical O2 High O3 Medium 1 Low 40 36 32 28 10 12 2003 10 17 2003 10 22 2003 10 27 2003 11 1 2003 11 6 2003 11 11 2003 11 16 2003 11 21 2003 11 26 2003 12 1 2003 12 6 2003 In this version of the report the y axis represents the number of incidents and the x axis represents a specific day in the time span The exact count of each bar in the stacked histogram can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value You can also filter the type of incident being reported as well as change the end date for the dat
42. displays the name of the test case together with the release mapping information for the test case in question Test Steps Req Coverage Custom Props Test Runs Attachments History Available Releases Library System Release 1 1 SP1 a System Release 1 Library System Release 1 1 SP2 Library System Release 1 SP1 Library System Release 2005 a Library System Release 1 SP2 Library System Release 1 1 The release coverage box indicates the releases that are currently mapped against the test case To associate releases with this test case choose from the list above and click Add You can use the Remove and Remove All buttons to remove releases that are no longer covered by the test case Double clicking on a covered release will take you to the release itself The release mapping section consists of two lists of releases the one on the left being the list of the releases belonging to the project that are not currently mapped to the test case The right box contains the list of releases currently mapped to this test case Double clicking on items in this box will jump you to the release details screen for this requirement see section 7 2 To change the release mapping 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 releases from the list of available on the left to the list of mapped on the right Similarly the lt
43. e interval Similarly by clicking on the weekly radio button you can display the past 12 months of open incident counts organized on a weekly basis categorized by priority 8 3 5 Incident Aging The incident aging chart displays the number of days incidents have been left open in the system The chart is organized as a stacked histogram with the count of incidents on the y axis and different age intervals on the x axis Each bar chart color represents a different incident priority giving a project manager a snapshot view of the age of open project incidents by priority Date Interval 9 Date Ending eno2007 mid yyyy Incident Aging By Priority 1 Critical 2 High OF 3 Medium O 1 Low This report can be filtered by the type of incident so for example you can see the aging of just bugs or just issues for the project in question 8 3 6 Incident Turnaround Time The incident turnaround time chart displays the number of days incidents have taken to be closed from the time they were first raised in the system The chart is organized as a stacked histogram with the count of incidents on the y axis and different turnaround time intervals on the x axis Each bar chart color represents a different incident priority giving a project manager a snapshot view of the turnaround time of project incidents by priority Welcome Fred Bloggs My Profile Log Out L rary information System X spiraTest Project Home Requirement
44. ed description is displayed as a tooltip To actually view the document simply click on the filename hyperlink and a new web browser window will open Depending on the type of file this window will either display the document or prompt you for a place to save it on your local computer To delete an existing attachment from a requirement simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the requirement you need to click the Browse button and select the file from your local computer optionally enter a detailed description then click the lt Upload gt button The document will be copied from your computer and attached to the requirement Note If you are using a non Windows computer e g Macintosh that doesn t put file extensions on filenames e g xls for an Excel sheet automatically then you will need to manually add the file extension to the filename before uploading if you want it to be displayed with the correct icon in the attachment list 4 2 4 History In this mode the main pane displays the list of changes that have been performed on the requirement artifact since its creation An example requirement change history is depicted below Test Coverage Custom Properties Attachments 2 2006 12 00 00 AM Status In Progress Completed Fred Bloggs 3 4 2005 12 00 00 AM Status Requested In Progress Joe P Smith The change history displays the date that e
45. ed 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 equivalent 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 Profile Log Out Ubrary information System Project Home Requirements Releases i spiraTest Role Manager Please review the information listed below and make any changes if necessary Once you have finished click Update to confirm them First Name Fes O O Middle Initial Last Name User Name fredbloggss Email Address LDAP DN N A __ Change Password Current Password New Password Confirm Password
46. enoted 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 Finally as a shortcut you can click the Create Test Case from This Requirement link to create a new test case in the list of covered test cases that will be automatically linked to this requirement This is useful when you have created a new requirement and want to generate an initial covering test to be fleshed out later 4 2 2 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for requirements To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Assuming that custom prope
47. er 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 There is also a drop down list at the bottom of the page which allows you to specify how many rows should be displayed in each page helping accommodate different user preferences 6 1 1 Sorting and Filtering You can easily filter and sort the list of incidents as illustrated in the screen shot below spiraTest Library Information System gt Incidents Gp New Incident 3 Delete 2 Refresh Show hide columns Welcome Fred Bloggs My Pro le Log Out Test Cases Y Apply Filters Y Clear Filters Incidents Role Manager Vo inc AY Nome AY Type AY Status AY Priory AY Detected By AY Owned By AY Closed On AY Operating System AY Seay a IN000017 Cannot add a new book to the system IN000004 Database not backing up correctly IN000005 Cannot install system on Oracle 9i IN000007 Cannot add a new book to the system IN000011 Validation on the edit book page IN000015 Session handling IN000016 The homepage hangs whilst loading IN000012 Quote handling issues throughout IN000008 Editing the date on a book is clunky IN000006 The book listing screen does
48. er your user name We Ico me to and password then click the log in button a User Name spiraTest fredblaggs Version v1 5 Copyright C 2006 2007 Inflectra Corporation Forgot your password Don t have an account inflectra You need to enter your given 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 a 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 sys
49. es a spiraTest wo SpiraTest User Manual Version 1 5 Inflectra Corporation 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 Release Management 2 6 Miscellaneous 3 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 Details 5 3 Execute Test Case s 5 4 Test Run Details 6 Incident Tracking 6 1 Incident List 6 2 Incident Details 7 Release Management 7 1 Release List 7 2 Release Details 8 Reports Center 8 1 Requirements Reports 8 2 Test Case Reports 8 3 Incident Reports N O ON OO BF OO ONNENN ND 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 i
50. est case to add as a link in the test step list Functional Tests Ability to edit existing book Ability to edit existing author Ability to reassign book to different author Regression Tests Book management Author management Scenario Tests Exception Scenario Tests You need to then select the name of the test case you want to insert as a link and click lt Next gt If the test case has declared parameters see the section on Parameters below for more details you will be taken to the following screen Req Coverage Custom Props Test Runs Attachments History Please fill out the parameters for this linked test case password You need to fill out the values of the parameters for the linked test case and then click the lt Insert gt button to complete the operation The system will then insert the test case as a link just before the currently selected test step If no existing test step was selected the link will be added at the end of the test step list 5 2 1 3 Delete Clicking on the lt Delete gt button deletes the currently selected test steps and reorders the test step position numbers to close any gaps in numbering 5 2 1 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
51. est 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 active flag and test case number 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 instead display a block LED style graph that illustrates the aggregate execution status of its child test cases Thus if the test folder contains 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 exac
52. ests Name Ability to create new book A q A T Ability to create new book Description T Ability to edit existing book P T Ability to edit existing author Tests that the user can create a new book in the system T Ability to reassign book to different au Author Fred Bloggs Estimated Time minutes Owner Fred Bloggs Creation Date 1 Dec 2003 Priority 1 Critical Execution Status Passed Active Yes Execution Date 1 Dec 2003 Req Coverage Custom Props Test Runs This page is made up of three areas the left pane is the navigation window the upper part of the right pane contains the test case detailed information itself and the bottom part of the right pane contains related information about the test case 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 top part of the right pane allows you to view and or edit the details of the particular test case You can edit the various fields name description etc and once you are satisfied with them simply click the lt Update gt button just below the fields to commit the changes The lower part of the right pane can be switched between six d
53. for the copied moved releases by selecting the checkbox of the release you want to copy move in front of and then clicking the Paste Releases link If you want to copy move the releases to the end of the list you just click the link without selecting a destination To abort the copy or move all you need to do is click the Cancel link and the operation will be aborted Note that copied releases will also include the test mapping information from the originals 2 Release Details When you click on release item in the release list described in section 7 1 you are taken to the release details page illustrated below a v gt Welcome Fred Bloggs My Profile Log Out Library information System spiraTest a S Project Home Requirements Releases Test Cases Library Information System gt Releases gt Release Details Role Manager lt lt Back to Release List Release Name Library System Release 1 RLO000001 sg de aera as Name ibr m Rel 1 1 i tem Rel Library System Release 1 1 SP1 Library System Release 1 1 SP2 Library System Release 2005 This is the initial release of the Library Management System Version Number 1000 Created By Fred Bloggs Active Yes Created On 15 Feb 2004 Test Cases Custom Properties This page is made up of three areas the left pane is the navigation window the upper part of the right pane contains the release detailed information itself and the bottom part
54. g 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 In addition to viewing the project home page you can choose to filter by a specific release to get the homepage for just that release 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 and the names of the owners of the project 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 t
55. he project requirements list see section 4 1 whereas clicking on the individual values in the cells will display the requirements list with the filter set to match the importance and status of the value 3 4 3 Requirements Coverage This section consists of a bar graph that displays the aggregated count of requirements test coverage for the project The Passed Failed Blocked Caution 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 five statuses for the covered requirements the sixth Not Covered bar depicts the total number of requirements that have no tests covering them putting the five 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 Caution or Not Run The greatest risk lies with the Blocked Not Covered and Not Run status codes since the severity quantity of any bugs lurking within is not yet fully known If you position the
56. ifferent views by clicking the appropriate tab Initially the pane will be in Test Steps mode but it can be switched to Requirements Coverage Custom Properties Test Runs Releases Attachments and History modes if so desired Each of the views is described separately below In addition there is a shortcut link Execute This Test that allows you to execute this test see section 5 3 without having to return to the Test Case list 5 2 1 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 Req Coverage Custom Props Test Runs cP InsertStep cp insertLink Delete 4 MoveUp Wy MoveDown Refresh E Parameters F 14 Call Login to Application TC17 A N A User clicks link to create User taken to first screen in book v wizard v User enters books name and User taken to next screen in a Macbeth William a author then clicks Next wizard v Shakespeare v User chooses book s genre and User sees screen displaying Play Tragedy sub genre from list all entered information me bmit lUser clicks submit button k Note Test steps that are marked with a hyperlink
57. ill display a list of all the incidents that have been reportedly resolved in this release This is useful for double checking that all the resolved incidents for a release have indeed been fixed gt Verified in this Release This will display a list of the incidents that have been verified as being fixed in this release This is useful for generating release notes for a specific release indicating what changes and enhancements have been made in the release Regardless of the mode each incident is listed together with the type status priority name owner detector detection date and a link to the actual incident details see section 6 2 Test Cases Custom Properties Test Runs Attachments History a EEE This Release Incident Type Status Priority Name Owned By Detected On Detected By IN000007 Bug Assigned 4 Critical Cannot add a new book to the system Joe P Smith 4 Nov 2003 Joe P Smith IN000002 Incident New Not able to add new author 1 Nov 2003 Joe P Smith IN000001 Incident New Cannot log into the application 1 Nov 2003 Fred Bloggs Displaying 1 3 of 3 incidents Show 15 rows per page 11 To change between the three modes outlined above simply select the desired mode from the drop down list contained within the header of the incident list table 7 2 2 Test Case Mapping This mode displays the test case mapping information for the release in question Incidents Custom Properties Test Runs Attachments
58. information System spiraTest Requirements Releases Test Cases incidents Library Information System gt Requirements gt Requirement Details Role Manager lt lt Back to Requirements List Requirement Ability to add new books to the system RQ000004 Book Management Name Ability to add new books to the system Ability to add new books to the system Description Ability to delete existing books in the The ability to add new books into the system complete with ISBN publisher and other related i k information i EE TCE Importance 1 Critical Author Fred Bloggs Status Completed Release Library System Release 1 Last Updated 1 Dec 2003 Created On 1 Dec 2003 History This page is made up of three areas the left pane displays the requirements list navigation the top of the right pane displays the details of the selected requirement and the bottom of the right pane can display different information related to the requirement 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 top part of the right pane allows you to view and or edit the details of the particular requirement You ca
59. king on the lt Delete gt button deletes all the releases 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 Any test runs or incidents that were associated with a deleted release are not themselves deleted but the relationship between them is lost 7 1 4 Indent Clicking on the lt Indent gt button indents all the releases whose check boxes have been selected If any of the items are made children of a release that had no previous children it will be changed from a detail item into a summary item 7 1 5 Outdent Clicking on the lt Outdent gt button de indents all the releases whose check boxes have been selected If any of the items were the only children of a summary release item then that item will be changed back from a summary item to a detail item 7 1 4 Refresh Clicking on the lt Refresh gt button simply reloads the release list This is useful as other people may be modifying the list of releases at the same time as you and after stepping away from the computer for a short time
60. lable 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 7 2 3 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for releases To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Assuming that custom properties have been defined for your project you will see a list of optional parameters that can be set on the release These can be either freetext or drop down lists In the example below you can enter Notes and or the Operating System that the release is intended for Test Cases Test Runs History Please edit the following custom properties of this artifact and click Update when finished This is the first version of the system Operating System Once you are satisfied with the values for the custom properties simply click Update to commit the changes 7 2 4 Test Runs This view displays the list of all the test runs executed against the release Each test run is listed together with the date of execution the name of the test case the name of the tester the release version of the system that the test was executed against the overall execution status for the test case in that run and a link to the actual te
61. le incident change history is depicted below General Custom Properties Attachments 5 2 2006 12 00 00 AM Status Open Assigned Fred Bloggs 3 5 2005 12 00 00 AM Status New Open Fred Bloggs 3 4 2005 12 00 00 AM Type Incident Bug Joe P Smith The change history displays the date that each change was made together with the fields that were changed the old and new values and the person who made the change This allows a complete audit trail to be maintained of all changes in the system 7 Release Management This section outlines how to use the Release Management features of SpiraTest to manage different versions of the system being tested in a particular project This is an optional feature of the system and you can manage the testing for a project successfully without tracking individual releases Typically when you develop a system it is important to ensure that features introduced in Successive versions do not impair existing functionality this is known as regression testing In such situations you will want to be able to execute the same set of test scripts against multiple versions of the system and be able to track failures by version A feature that works correctly in version 1 0 may fail in version 1 1 and the maintenance team may be testing the existing lifecycle of v1 0 in parallel with the development team testing v1 1 Therefore by developing a master set of releases versions in the Release Management module you ca
62. lick on the link of another project name You can always change your current project by clicking on the drop down list of projects displayed on the global navigation bar to the right of the Log Out link 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 for 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 gt Execute link listed below 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 trai
63. list as columns for the current project To show a column that is not already displayed simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names This is stored on a per project basis so you can have different display settings for each project that you are a member of The fields can be any of the built in fields or any of the custom properties set up by the project owner 4 1 10 Copying and Moving To copy or move a requirement or set of requirements simply select the check boxes of the requirements you want to copy or move and then click either lt Copy gt or lt Move gt as appropriate Upon clicking the button the rows you selected will be marked in bold with a light yellow background and the screen will prompt you to choose the destination for the copy move Welcome Fred Bloggs My Profile Log Out Library information System X spiraTest Project Home Requirements Releases Test Cases Incidents Library Information System gt Requirements Role Manager db insert 3 Delete indent lt Outdent ShowLevel MhCopy OyMove Refresh Show hide columns J SS Se a ay Ra S Functional System Requirements In Progress RQ000001 Ec Online Library Management System In Progress RQ000002 Book Management EA Se Completed RQ000003 Ability to add new books to the system bE hE amp Completed RQ000004
64. ly by clicking on the weekly radio button you can display the past 12 months of incident discovery data organized on a weekly basis s Pd Welcome Fred Bloggs My Profile Log Out L rary information System X spiraTest Project Home Requirements Releases Incidents Reports Library Information System gt Reports Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Priority Chart Turnaround Time By Priority Chart Incident Type All Date Interval Daily Weekly Date Ending 6 10 2007 mid yyyy Incident Discovery Rate Discovered Closed In this version of the report the y axis represents the number 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 Again you can filter this report by the type of incident and also specify the ending date of the date range Clicking the Back to Project Home hyperlink will take you back to the Project Home dashboard In addition the toolbar displays a list of shortcuts to other incident reports that can be displayed 8 3 3 Cumulative Incident Count Chart The cumulative incident count chart displays the cumulative total number of incidents logged in the system for the current project
65. ment features of SpiraTest can be 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 Profile Log Out Project Home Requirements Test Cases spiraTest Library Information System gt Requirements Role Manager dh Insert 3 Delete amp gt indent lt Outdent ShowLevel GyCopy ChMove amp Refresh Show hide columns Y Clear Filters Requirement Name TestCoverage Importance Status Release Difficulty Req E SS any ra E Functional System Requirements Not Covered In Progress RQ000001 Online Library Management System Not Covered In Progress RQ000002 Book Management itt Completed RQ000003 Ability to add new books to the system HE Completed Moderate RQ000004 Ability to edit existing books in the system BH Completed RQ000005 Edit Ability to delete existing books in the system Hh Completed RQ000006 Ability to associate books with different subjects EE Completed RQ000007 Edit Ability to associate books with different authors E m m Completed RQ000008 Edit
66. 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 requirements 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 priorit
67. n edit the various fields name description etc and once you are satisfied with them simply click the lt Update gt button just below the fields to commit the changes In addition the bottom part of the right pane can be switched between four views Test Coverage Custom Properties Attachments and History each of which will be described in more detail below 4 2 1 Test Coverage In this mode the right pane contains the test coverage information for the requirement in question Custom Properties Attachments History Available Test Cases Test Coverage Ability to edit existing book Adding new book and author to libra Ability to create new author 5C anageme Ability to edit existing author Ability to reassign book to different author Regression ests Author management Person loses book and needs to reportloss Open Up Web Browser gt Create Test Case From This Requirement The test coverage box indicates the test cases that are currently mapped against the requirement To add test cases to this requirement choose from the list above and click Add You can use the Remove and Remove All buttons to remove tests that no longer cover the requirement Double clicking on a covered test case will take you to the test case itself 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 d
68. n have the different testing teams correctly assign their testing actions to the appropriate version 1 Release List When you click on the Releases tab on the global navigation bar you will initially be taken to the release list screen illustrated below Welcome Fred Bloggs My Profile Log Out Requirements Releases spiraTest _ Library Information System gt Releases Role Manager Gp inset 3 Delete g gt indent lt p Outdent ShowLevel yCopy ThMove Refresh Show hide columns Y Clear Fitters ov Release Name resin CreatedOn E E A Library System Release 1 1 0 0 0 15 Feb 2004 Fred Bloggs RLOOO001 Library System Release 1 SP1 1 0 1 0 5 May 2004 Joe P Smith RL000002 Library System Release 1 SP2 1 0 2 0 Jun 2004 Joe P Smith RLOOO003 Library System Release 1 1 1 1 0 0 15 Oct 2004 Fred Bloggs RLO00004 Library System Release 1 1 SP1 1 1 1 0 30 Nov 2004 Joe P Smith RL000005 Library System Release 1 1 SP2 1 1 2 0 Jan 2005 Fred Bloggs RLOOO007 Library System Release 2005 1 2 0 0 1 Apr 2005 Fred Bloggs RLOOO006 The release list will contain all the releases associated with current project When you create a new project this list will initially be empty and you will have to use the lt Insert gt button to start adding releases to the project The hierarchical organization of releases in the list is configurable so you can organize the various releases in the way
69. n is displayed Attachment List Sequence Diagram for Sequence diagram in UML format that provides additional detail ed 5 3 2006 12 00 00 Book Mgt pdt surrounding the book managament use case test case Bloggs AM 8 2 2 Test Case Execution Report This printable report displays all of the test cases defined for the current project in the order they appear in the test case list For each individual test case the name execution status author owner and execution date are displayed along with tables containing the list of individual test runs attached documents the change history and finally any associated open incidents Folder 1 Functional Tests Tests that the user can create a new book in the system Status Fassed Author Fred Bloggs Creation Date 12 1 2003 12 00 00 AM Owner Fred Bloggs Last Execution 12 1 2003 12 00 00 AM URL http www _libraryreferences org Test Type Functional Test Call Lagin to Application User clicks link to create book User taken to first screen in wizard User enters books name and author then ee eee Macbeth William User taken to next screen in wizard clicks Next Shakespeare User chooses book s genre and sub genre from User sees screen displaying all entered list information Play Tragedy User clicks submit button Confirmation screen is displayed Open Incidents List Bug Assigned 1 Critical Cannot add a new book to the system Joe P Smith 11 4 2003 12 00 00 AM Test R
70. n t sort IN000009 Editing the date on an author is clunky IN000013 The tables get cutoff on low res modes IN000014 Permissions not updating when changed IN000010 Doesn t let me add a new category Show 15 rows per page Bug Bug Bug Bug Bug Bug Any X Duplicate Open Open Assigned Resolved Closed Not Reproducible Resolved Assigned Open Assigned Closed Closed Resolved Any Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Windows XP 21 Nov 2003 Windows 2003 20 Nov 2003 21 Nov 2003 Displaying 1 14 of 14 incidents 11 To filter the list by incident type status priority owner 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 Apply Filters 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 sim
71. nd provide specific information on how to manage each of the artifacts illustrated above Note that this manual does not expan ae Administration level functionality of the system for that please refer to the SpiraTest Administration Guide 2 6 2 Artifact Naming Conventions On various screens in the system you will see lists of artifacts requirements test cases etc together with a unique identification number In order to make it easier to recognize at a glance which type of artifact the identification number refers to SpiraTest uses a system of two letter prefixes which help identify the type of artifact being displayed The current prefixes used by the system are Artifact Prefix Artfact Prex Projet PR__ incidentTye SIT Requirement RQ Incident Priory P incident Severity Vv incident N S SS incident Status Js o o 0 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 Please ent
72. ning 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 seven section tabs My Page Project Home Requirements Releases Test Cases Incidents and Reports that correspond to the 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
73. nt which is described in section 6 2 5 4 2 Stack Trace In the case of an automated test run this tab will display the details of the test run as reported from the test runner application These details will vary depending on the type of automated tool being used but typically they include the name of the automated test runner the number of assertions raised the name of the corresponding test case in the tool the status of the test run and a detailed error message and stack trace in the case of a failure An example test run as reported from the NUnit automated test runner is illustrated below Test Run Steps SS Custom Properties Runner Name NUnit Assert Count 1 Message Expected 1 but 2 was found Test Name _01_TestCreateBook Failure Details Object variable or With block variable not set Description An unhandled exception occurred during the execution of the current web request Please review the stack trace for more information about the error and where it originated in the code Exception Details System NullReferenceException Object variable or With block Variable not set Source Error Line 215 Response Write lt option selected value _ amp MonthCheck MonthCount amp gt MonthCount amp lt option gt amp vbCrLf Line 216 Else Line 217 Response Write lt option value amp MonthCheck MonthCount amp gt amp MonthCount amp lt option gt amp vbCrLf Details
74. o 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 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 lis
75. of the right pane displays different information associated with the release The navigation pane consists of a link that will take you back to the release list as well as a list of the other releases in the current project This latter list is useful as a navigation shortcut you can quickly view the test run information of all the other releases by clicking on the navigation links without having to first return to the release list page The top part of the right pane allows you to view and or edit the details of the particular release You can edit the various fields name description etc and once you are satisfied with them simply click the lt Update gt button just below the fields to commit the changes The lower part of the right pane can be in one of six possible modes that can be selected Incidents Test Cases Custom Properties Test Runs Attachments and History Each of the different views is described separately below 7 2 1 Incidents This is the default view for the release details page It displays the incidents associated with the selected release The incident list can be one of three modes gt Detected in this Release this will display a list of all the incidents that were detected during the testing of the selected release This is useful in determining if there are open incidents associated with a release that need to be dealt with gt Resolved in this Release This w
76. on how to use SpiraTest in conjunction with an automated testing tool are provided in the SpiraTest Automated Testing Integration Guide which can be downloaded from the Inflectra website 5 4 3 Custom Properties In this mode the tab displays any custom properties that the project owner has defined for test runs To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Assuming that custom properties have been defined for your project you will see a list of optional parameters that have been set during the test run Test Run Steps Stack Trace Please edit the following custom properties of this artifact and click Update when finished Notes Testing with IE v5 5 SP1 Web Browser Internet Explorer Operating System Windows XP For test runs custom properties are most commonly used to capture and record the system configuration that the test was performed on for example the operating system hardware platform web browser 6 Incident Tracking This section outlines how the incident defect tracking features of SpiraTest can be used to manage key project artifacts during the software development lifecycle In addition to managing the defects raised during the execution of test cases in the test management module the Incident Tracker is also a powerful risk issue bug tracking system in its own right When coupled with the project dashboard
77. operties simply click Update to commit the changes 5 2 4 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 release version of the system that the test was executed against the overall execution status for the test case in that run and a link to the actual test run details See section 5 4 In addition you can choose to display any of the custom properties associated with the test run Test Steps Reg Coverage Custom Props Releases Attachments History 12 1 2003 11 30 55 AM Passed 10 minutes 90 minutes Mozilla Firefox Windows 2000 TR000002 12 1 2003 10 50 20 AM 0 0 0 Failed 9 10 minutes 70 minutes Opera Windows 2003 TR000012 12 1 2003 10 45 20 AM 00 Failed 10 minutes 75 minutes Internet Explorer Windows XP TR000001 Customize columns Show hide columns v 1 The customize columns drop down list allows you to change the fields that are displayed in the test run list as columns To show a column that is not already displayed simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names The displayed columns can be any standard field or custom property 5 2 5 Release Mapping This view
78. over a particular date range The report can either be displayed for a 60 day interval on a daily basis or for a 12 month interval of a weekly basis The report displays two data series one illustrating the total count of all incidents the other the total count of all open incidents i e with status not set to fixed or closed The screen shot below illustrates the cumulative count report loaded with the past 60 days of cumulative incident count data depicted on a daily basis Welcome Fred Bloggs My Profile Log Out Library information System X spiraTest Project Home Requirements Test Cases Incidents Reports Library Information System gt Reports gt Cumulative Incident Count Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Priority Chart Turnaround Time By Priority Chart Incident Type All Date Interval Daily Weekly Date Ending 6 10 2007 mid yyyy Cumulative Incident Count Open Total In this version of the report the y axis represents the number of incidents 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 You can also filter the type of incident being reported as well as change the end date for the date interval Similarly by clicking on the weekly radio button
79. ply 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 Clicking on the lt Clear Filters gt button removes any set filters and expands the incident list to display all incidents for the current project 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 depending on how the workflow has been configured for your project certain fields may be disabled For more details on setting and up configuring workflow for your project please refer to the SpiraTest Administration Guide 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 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 5 Show Hide Columns This drop down list allows you to change the fields that are displayed in the incident list as columns for the current project To show a column that is not already displaye
80. quirement 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 need 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 indent
81. r the list of requirements as illustrated in the screen shot below 3 Delete g gt indent lt p Outdent Alllevels yCopy GhyMove Refresh Show hide columns Y Clear Fiters Ability to link authors to their contact informati Not Covere Requested 1 1 0 0 RQ000017 Edit Administration Functions Not Covere Requested RQ000022 Edit Ability to completely backup the database Not Requested RQ000023 Edit Data Import Functionality Not Covere Requested RQ000024 Edit Ability to import from legacy system x Not Covere Requested RQ000025 Edit Ability to create new users in the system Requested RQ000026 Edit Ability to modify existing users in the system Not Covere Requested RQ000027 Edit dh Insert 3 Delete lt gt indent lt b Outdent To filter the list by any of the displayed columns you either choose an item from the appropriate drop down list or enter a free text phrase depending on the type of field 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 requirement numbers In the screen shot above we are filtering on Status Requested 4 1 9 Show Hide Columns This drop down list allows you to change the fields that are displayed in the requirement
82. report can either be displayed for 60 days of data daily or for 12 months of data weekly ending on a specified date 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 Bloggs My Profile Log Out L rary information System X spiraTest Project Home Requirements Releases Reports Library Information System gt Reports gt Incident Discovery Rate Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Priority Chart Tumaround Time By Priority Chart Incident Type All Date Interval Daily Weekly Date Ending 6 10 2007 mid yyyy Incident Discovery Rate Discovered Closed 10 PAULIN IT iN y y 10 12 2003 10 17 2003 10 22 2003 10 27 2003 11 1 2003 11 6 2003 11 11 2003 11 16 2003 11 21 2003 11 26 2003 12 1 2003 12 6 2003 N w b wn oa o 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 You can filter the report by the type of incident and also change the ending date of the date range e g displaying only the bugs for the date range Similar
83. 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 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 Test Steps Req Coverage Custom Props Releases Attachments History 12 1 2003 11 30 55 AM 1 0 1 0 10 minutes 90 minutes Mozilla Firefox Windows 2000 TROO0002 12 1 2003 10 50 20 AM 1 0 0 0 Failed 9 10 minutes 70 minutes Opera Windows 2003 TR000012 12 1 2003 10 45 20 AM 000 Failed 9 10 minutes 75 minutes Internet Explorer Windows XP TR000001 Customize columns Show hide columns v 11 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 shown below pad Welcome Fred Bloggs My Profile Log O X bd My Profile Log Out L rary Information System spiraTest a Project Home Requirements Releases Test Cases Incidents Library Information System gt Test Cases gt Test Run Details Role Manager Test Run Ability to create new book TRO00001 Tests that the user can create a new book in the system 1 Dec 2003
84. rporation 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 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 Profile Log Out E spiraTest S My Page gt Fred Bloggs Project Name Web Site Creation Date Project Type Priority Date Opened Library Information www libraryinformationsystem org 1 Dec 2005 Ability to associate multiple authors Library Information System Enhancement 17 Nov 2003 System Test System Limitation Library Information System Limitation 4 Dec 2003 Sample Application One www tempuri org 1 Dec 2005 Test Training Item Library Information System Training 3 Dec 2003 Sample Application Two 1 Dec 2005 Editing the date on a book is clunky Library Information System Bug 4 Nov 2003 Test Training Item Library Information System Training 2 High 3 Dec 2003 Na P Si Last Ex d Test Change Request Library Information System Change Request 7 Dec 2003 m oee t ai Ability to import data from excel Library Information System Enhancement 25 Nov 2003 Ability a E k gt Abiit a new boo
85. rson who attached it and the date uploaded In addition if you position the pointer over the filename and hold it there for a few seconds a detailed description is displayed as a tooltip To actually view the document simply click on the filename hyperlink and a new web browser window will open Depending on the type of file this window will either display the document or prompt you for a place to save it on your local computer To delete an existing attachment from a release simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the release you need to click the Browse button and select the file from your local computer optionally enter a detailed description then click the lt Upload gt button The document will be copied from your computer and attached to the release Note If you are using a non Windows computer e g Macintosh that doesn t put file extensions on filenames e g xls for an Excel sheet automatically then you will need to manually add the file extension to the filename before uploading if you want it to be displayed with the correct icon in the attachment list 7 2 6 View History In this mode the main pane displays the list of changes that have been performed on the release artifact since its creation An example release change history is depicted below Custom Properties Test Runs 5 2 2006 12 00 00 AM Name Library System v1 0 0 Library S
86. rties have been defined for your project you will see a list of optional parameters that can be set on the requirement These can be either freetext or drop down lists In the example below you can enter a URL difficulty and or Requirement Type Test Coverage Custom Properties History Please edit the following custom properties of this artifact and click Update when finished URL http www libraries org Difficulty Requirement Type gt Cancel Once you are satisfied with the values for the custom properties simply click Update to commit the changes 4 2 3 Attachments In this mode the main pane displays the list of documents that have been attached to the requirement The documents can be in any format though SpiraTest will only display the icon for certain known types Test Coverage Custom Properties Attachments History Jocument Name Size Uploaded By Upload Date Book Management Functional Spec doc 10 KB Fred Bloggs 2 May 2006 A Graphical Design Mockups psd 1 500 KB Joe P Smith 1 May 2006 wi Book Management Screen Wireframe ai 3 200 KB Joe P Smith 2 Mar 2005 Upload New Attachment Filename Description Upload The attachment list includes the filename that was originally uploaded together with the file size in KB name of the person who attached it and the date uploaded In addition if you position the pointer over the filename and hold it there for a few seconds a detail
87. s 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 Stack Trace Custom Properties RS000001 User logs in to application User taken to main menu screen RS000002 User clicks link to create book User taken to first screen in wizard RS000003 User enters books name and author User taken to next Macbeth William An error page is displayed No such object or with then clicks Next screen in wizard Shakespeare block variable at line 473 gt View Incidents Incidents List for Step 3 Test Run Step RS000003 IN000007 Bug Assigned 1 Critical Cannot add a new book to the system Joe P Smith 4 Nov 2003 Joe P Smith lt lt Hide Incident List 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 incide
88. s Releases Incidents Library Information System gt Reports gt Incident Closure Turnaround Time Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Prionty Chart Tumaround Time By Priority Chart Incident Type All Date Inteval D eel Date Ending 6102007 midiyyyy er Incident Closure Turnaround Time 1 Crtical 2 High 3 Medum O1 Low 64 70 This report can be filtered by the type of incident so for example you can see the turnaround time of just bugs or just issues for the project in question 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
89. s 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 changed 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 1 7 Show Level Choosing an indent level from the Show Level drop down box allows you to quickly and easily view the entire requirements list at a specific indent level For example you may want to see all requirements drilled down to the third level of detail To do this you would simply choose Level 3 from the list and the requirements will be expanded collapsed accordingly 4 1 8 Filtering You can easily filte
90. s 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 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 man
91. st run details See section 5 4 In addition you can choose to display any of the custom properties associated with the test run Incidents Test Cases Custom Properties Attachments History 12 1 2003 11 50 55 AM Caution minutes 50 minutes TR000010 12 1 2003 11 30 55 AM 0 0 Passed 5 minutes 90 minutes TRO00003 12 1 2003 10 50 20 AM 0 00 Failed 9 10 minutes 70 minutes Opera Windows 2003 TR000012 12 1 2003 10 45 20 AM 00 Failed 10 minutes 75 minutes Internet Explorer Windows XP TR000001 Customize columns Show hide columns 1 The customize columns drop down list allows you to change the fields that are displayed in the test run list as columns To show a column that is not already displayed simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names The displayed columns can be any standard field or custom property 7 2 5 Attachments In this mode the lower section of the screen displays the list of documents that have been attached to the release The documents can be in any format though SpiraTest will only display the icon for certain known types ke StaticMappings xml Fred Bloggs 6 Dec 2007 Upload New Attachment Filename Description Static Mappings The attachment list includes the filename that was originally uploaded together with the file size in KB name of the pe
92. t aggregate test folder execution status information position the mouse pointer over the bar chart and the number of tests in each of the execution statuses passed failed not run blocked caution will be displayed as a tooltip Note that if you change the owner of a test folder then all the child test cases will be assigned the same owner This allows you to more easily associate entire folders to test cases to be executed by a specific user 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 i 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 t
93. t 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 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 1 6 Show Level Choosing an indent level from the Show Level drop down box allows you to quickly and easily view the entire test case list at a specific indent level For example you may want to see all test cases drilled down to the third level of detail To do this you would simply choose Level 3 from the list and the test cases will be expanded accordingly 5 1 7 Show Hide Columns This drop down list allows you to change the fields that are displayed in the test case list as columns for the current project To show a column that is not already displayed simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names This
94. tem 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 actions 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 ee spiraTest we You can either Log Out and try a differant user name or Sign Off The Other Version v1 0 eet s the other Copyright C 2006 Inflectra Corporation tS to logout 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 spiraTest Retum to Login page Version v1 0 Copyright C 2006 Inflectra Co
95. tem responds you will use the buttons on the page to record what actually happened gt There is also an optional section below the main pane that allows you to log an incident in the system associated with the test step For failures this will typically be used to log a bug relating to the failure However even if you pass a step you can still log an incident which may be useful for logging non critical cosmetic items that are not serious enough for a failure to be recorded 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 Bloggs MyProfile Log Out Library information System v spiraTest My Page Project Home Requirements Releases Test Cases Library Information System gt Test Cases gt Test Case Execution Role Manager lt lt Back to Test List Current Test Case Ability to create new book gt Select 4 x4 gt gt 7 Ability to create new book TC2 Please follow the directions outlined in the box below W 116 Step 1 Wi TC17 Step2 Mi TC2 Step2 2 C2 Wi Tc2 Steo3 Expected Result Sample Data Mi To2 Steo 4 Confirmation screen is displayed a W TC2 Step 5 ad v Please enter the actual test result if it differs then did the sporopriste button Actual Result El Leg sn incident for this step Namet O O O Type This will ch
96. that makes most sense for a particular project Typically you have the major releases as the top level items with sub releases builds and iterations as the lower level items All of the releases in the list have a release name together with the assigned version number for that release the date that the release was first created the name of the creator of the release the release number and a set of custom properties defined by the project owner Clicking on a release s hyperlink will take you to the release details page for the item in question see section 7 2 Note Unlike requirements both the parent and child items are linked to details pages 7 1 1 Filtering You can easily filter the list of releases as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out Project Home Requirements Releases spiraTest Library Information System gt Releases cP Insert 3 Delete gt Indent lt Outdent Copy Th Move amp Refresh Show hide columns Y Clear Fitters ov Release Name lt o Version Created On Creator Active Release ID a I Yes a Ermer Library System Release 1 1 0 0 0 15 Feb 2004 Fred Bloggs Yes RLO00001 Library System Release 1 SP1 1 0 1 0 5 May 2004 Joe P Smith Yes RLO00002 Library System Release 1 SP2 1 0 2 0 5 Jun 2004 Joe P Smith Yes RL000003 S Library System Release 1 1 1 1 0 0 15 Oct 2004 Fred Bloggs Yes RL0O00004 Library System Release 1
97. ting System Windows Viste X Severity 3 Medium 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 Similarly in the case of a blocked test case they will be marked with a yellow square and in the case of a caution they will be marked with an orange square 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 optionally 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 type priority severity and any custom properties 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
98. 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 support inflectra com
99. und 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 In addition the lower section of the incident details page can be switched been four different views General Custom Properties Attachments and History These are described separately below 6 2 1 Editing an Existing Incident If you are editing an existing incident the fields that are available and the fields that are required will depend on your stage in the incident workflow For example an open incident might not require a Resolved Version whereas a resolved incident could well do The types of change allowed and the email notifications that are sent will
100. uns Fred Bloggs Library System Release 1 SP1 1 0 1 0 Passed 12 1 2003 11 30 55 AM q Joe P Smith Library System Release 1 1 0 0 0 Failed 12 1 2003 10 45 20 AM 8 3 Incident Reports 8 3 1 Incident Status Report This printable report displays all of the incidents tracked for the current project sorted by incident number For each individual incident the name type priority status opener owner and close date are displayed along with tables containing the detailed description and resolutions as well as a tabular list of attached documents and the change history gt Print Report Incident Status Report Type Incident Priority Status New Severity Opened By Fred Bloggs Opened On 11 1 2003 12 00 00 AM Assigned To Last Modified 12 1 2003 12 00 00 AM Detected In Release 1 0 0 0 Closed On Resolved In Release 1 0 1 0 Verified In Release 1 0 1 0 Notes Operating System Description Resolution When trying to log into the application with a valid username and password the system throws a fatal exception Attachment List Joe F 5 4 2006 12 00 00 Smith AM Error Logging in Captured screen shot of the error that was raised when attempting to Fred 4 24 2006 12 00 00 Screen shot git log in to the library application Bloggs AM Bug Stack Trace txt 8 3 2 Incident Discovery Rate Chart The incident discovery rate chart displays the total number of incidents created and closed over a particular date range The
101. ute Dec 2007 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Fred Bloggs TC000002 TC000003 TC000004 TC000005 TC000006 TC000007 TC000010 TC000011 TC000015 As illustrated in the example above when the drop down list is changed to select a specific release the list of test cases is filtered to just those mapped to the release in question In addition the execution status for the test releases will only reflect test runs for that specific release As can be seen in our example many test cases that have been run for other releases now show the Not Run status since they ve not been run for this specific release As a shortcut when you select a specific release for viewing subsequent execution of any of the test cases via the Execute icon will default the test run to the selected release 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 Profile Log Out L rary Information System spiraTest Project Home Requirements Test Cases Library Information System gt Test Cases gt Test Case Details Role Manager lt lt Back to Test Lis Test Case Ability to create new book TC000002 gt Execute This Test amp Functional T
102. warning message 5 2 1 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 of existing test steps will give a warning message 5 2 1 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 1 7 Update Each test step in the list is always in an editable mode When you click this button you commit any changes made to the test step list These changes consist of modifying an existing test step or entering a new test step in one of the five blank rows The delete insert move up move down operations on the other hand are committed immediately and do not need to have the lt Update gt button clicked for them to take effect 5 2 1 8 Cancel If during the entry of new test steps or the modification of existing test steps you want to revert back to the original information click lt Cancel gt and your changes will be discarded 5 2 1 9 Parameters Test cases can have parameters associated with them This enables one test case to be called several times by another test case as a link and have different parameters passed in each case making the operation different E g you could have a generi
103. y 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 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 priority 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 whereas clicking on the individual values in the cells will display the incident list with the filter set to match the priority and status of the value 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 Fail
104. y to add new books to the system Online Library Management System E Book Management Ability to edit existing books in the system Ability to delete existing books in the system Ability to associate books with different subjects Ability to associate books with different authors Ability to associate books with different editions Ability to completely erase all books stored intl Edition Management Ability to create different editions Author Management gt Create Requirement From This Test Case The requirements coverage box indicates the requirements that are currently mapped against the test case To add requirements to this test case choose from the list above and click Add You can use the Remove and Remove All buttons to remove requirements that are no longer covered by the test case Double clicking on a covered requirement 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
105. you can display the past 12 months of cumulative incident count data organized on a weekly basis Welcome Fred Bloggs My Profile Log Out Library information System lt spiraTest Project Home Requirements Test Cases Incidents Reports Library Information System gt Reports Role Manager lt lt Back to Reports Home Discovery Rate Chart Cumulative Count Chart Open Count By Priority Chart Aging By Priority Chart Turnaround Time By Priority Chart Incident Type All id Date Interval D Daily amp Weekly Date Ending 6 10 2007 mid yyyy gt Filter Cumulative Incident Count Open Total 60 S4 48 42 36 12 18 2002 1 22 2003 2 26 2003 4 2 2003 7 2003 6 11 2003 7 16 2003 8 20 2003 9 24 2003 10 28 2003 In this version of the report the y axis represents the number of incidents logged 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 Again you can also filter the type of incident being reported as well as change the end date for the date interval Clicking the Back to Project Home hyperlink will take you back to the Project Home dashboard 8 3 4 Open Incident Count The open incident count chart displays the total number of open incidents in the system for the current project over a particular date range categorized by inci
106. you should click this button to make sure you are viewing the most current release list for the project 7 1 5 Edit Each release 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 7 1 6 Show Level Choosing an indent level from the Show Level drop down box allows you to quickly and easily view the entire release list at a specific indent level For example you may want to see all releases drilled down to the third level of detail To do this you would simply choose Level 3 from the list and the releases will be expanded collapsed accordingly 7 1 7 Show Hide Columns This drop down list allows you to change the fields that are displayed in the release list as columns for the current project To show a column that is not already displayed simply select that column from the list of Show column names and to hide an existing column simply select that column from the list of Hide column names This is stored on a per project basis so you can have different display settings for each project that you are a member of The fields can be any of
107. ystem Release 1 Fred Bloggs 3 4 2005 12 00 00 AM Version Number 1 0 0 1 0 0 0 Joe P Smith The change history displays the date that each change was made together with the fields that were changed the old and new values and the person who made the change This allows a complete audit trail to be maintained of all changes in the system 8 Reports Center This section describes the reporting features of SpiraTest including an overview of each of the report types that are available When you click on the Reports tab on the global navigation bar you will initially be taken to the reports home page illustrated below Welcome Fred Bloggs My Profile Log Out Project Home Requirements Releases spiraTest Library Information System gt Reports Role Manager Requirements Reports Test Case Reports Incident Reports gt Requirements Coverage Report gt Test Case Execution Report gt Incident Status Report gt Printable Test Scripts Incident Graphs amp Charts gt Discovery Rate Chart gt Cumulative Count Chart gt Open Count By Priority Chart gt Aging By Priority Chart gt Turnaround Time By Priority Chart This page simply lists each of the reports available in the system categorized by the artifact they primarily relate to requirements test cases and incidents Clicking on any of the report hyperlinks will take you to the configuration page for the report in question The configuration

Download Pdf Manuals

Related Search

Related Contents

Word 2003 Book.cdr  GNU FreeIPMI User's Guide  TAFCO WINDOWS NU2-005V-I Instructions / Assembly  Mode d`emploi (5) : Comment obtenir la liste des  Keys Fitness 520U User's Manual  Intenso 4GB SDHC  downloaden  Original Mini Tilt User Manual  1 - Broil King  CTSC21X  

Copyright © All rights reserved. Failed to retrieve file