Home

SpiraTest v2.3 User Manual

Contents

1. Cone aed Cinni uuu TOET T aa tn a hasten eth Genet aia any tn wun cars harby werk davenel eeivers 5 Test Case Management 6 Incident Tracking 7 Release Management The requirements list consists of a hierarchical arrangement of the various requirements and functionalities 8 Task Tracking that need to be provided by the system in question The structure is very similar to the Work Breakdown 9 Reports Center Structure WBS developed in Microsoft Project and users of that software package will find this very fraosiline ta nuan Ulan sens mennta mo mae menia thin lint seall imitialhs ba mentis amd sames sanl bon tn ntad m 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 t
2. This page summarizes all of the information regarding the project group into a comprehensive easily digestible form that provides a one stop shop for people interested in understanding the overall status of the group as a whole as well as the relative performance of the different projects that make up the group It contains summary level metrics for all types of artifact requirements test cases tasks incidents etc that you can use to drill down into the appropriate project for more details In a similar manner to the My Page the Project Group Home dashboard is initially loaded in view mode which means that the various widgets on the page are displayed with minimum visual clutter no toolbars or control icons that makes it easy to scan the items on the page and see the health of the status of the project at a glace To switch the page to edit mode you should click on Modify Layout Settings hyperlink Once in edit mode each of the widgets displayed on the project group homepage can be minimized by clicking on the arrow icon in the top left of the window or closed by clicking on the cross icon in the top right of the window In addition the widgets allow you change their settings by clicking on the settings icon 4 This allows you to customize your view of the project group to reflect the types of information that are relevant to you If you have closed a widget that you subse
3. FMX Pause gt NextTest Release 1 2 0 0 Testing New Functionality TX5 Ability to create new author TC000004 W 4 Ability to create new author TC4 Tests that the user can create a new author record in the system Step 1 TC16 i Step 2 TC17 i Step 3 TC4 Step 1 Please follow the directions outlined in the box below W Step 4 TC4 User opens up browser and enters application URL http wvew libraryinformationsystem com beta W Step 5 TC4 Wi Step 6 TC4 C Ability to reassign book to di TC6 C 4 Person loses book and needs to TC 12 nected Result Sample Data C Z Adding new book and author to TC13 The browser loads the login web page http www libraryinformationsystem com beta Actual Result Please enter the actual test result if it differs then click the appropriate button a spiraTeam S Role Manager This will change the icon in the left hand navigation bar into a green square with a check mark in it Once all the test steps have passed you will now have the option of moving to the next test step by clicking the lt Next Test gt button if it is the last test case being executed the lt Finish gt button will be displayed instead 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
4. 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 Tasks In this mode the right pane displays the list of project tasks that need to be completed for the requirement to be satisfied Test Coverage Custom Props Attachments History Associations C dhNewTask 3 Remove Delete Refresh Est Effort 16 0h Actual Effort 15 5h O Develop new book entry screen Completed 1 0 0 0 0001 Fred Bloggs 1 Critical 8 0h 7 3h TKO00001 O 2 Create book object insert method 5s Completed 1 0 0 0 0001 Fred Bloggs 1 Critical 5 0h 5 3h TK000002 O ZJ Write book object insert queries Ss Completed 1 0 0 0 0001 Fred Bloggs Critical 3 0h 28h TK000003 Each of the tasks is displayed together with its name description by hovering the mouse over the name progress priority start date current owner estimated effort actual effort and numeric task identifier Clicking on the task name will bring up the Task Details page which is described in more detail in section 8 2 This allows you to edit the details of an existing task You can perform the following actions on a task from this screen gt New Task inserts a new task in the task list with a
5. Please edit the following custom properties of this artifact and click Update when finished http www libraryreferences org Test Type Once you are satisfied with the values for the custom properties 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 test set if applicable 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 Req Coverage Custom Props Ry SA TR z Ability to create new book 4 Dec 2003 1 1 0 00003 TR000018 z Ability to create new book 3 Dec 2003 1 1 0 0 0002 Pass d TR000015 Ability to create new book 2 Dec 2003 1 1 0 0 0001 Passed TRO00013 gt Ability to create new book 1 Dec 2003 Testing Cycle 1 0 1 0 Passec Mozilla Firefox Windows 2000 TR000002 for Release 1 1 2 Ability to create new book 1 Dec 2003 Failed Opera Windows 2003 TR000012 a Ability to create new book 1 Dec 2003 Testing Cycle internet Explorer Windows XP TR000001 for Release 1 0 Show 15 rows p
6. Attachments 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 either the lt Save gt or lt Save and News gt button at the top of the page to commit the changes In addition you can delete the current artifact by choosing lt Delete gt discard any changes made by clicking lt Refresh gt or print it by clicking lt Print gt The lower part of the right pane can be switched between six different 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 d
7. Log Out Library information System gt spiraTeam _ My Page Project Home Planning Reporting Reporting gt Tasks Velocity Task Graphs Task Summary Task Velocity Task Burnup Task Burndown Display data for _1 1 0 0 0003 Iteration 003 iy Tasks Velocity Expected Velocity Actual Velocity 10 25 2004 Role Project Owner The y axis of the graph displays the total estimated and actual effort delivered and the x axis can be configured to display three different levels of granularity gt All Releases This shows the total estimated and actual effort for each of the releases in the project gt Specific Release This shows the total estimated and actual effort for each of the iterations in the selected release gt Specific Iteration This shows the total estimated actual effort for each working day in the date range covered by the selected iteration 11 4 5 Task Burnup Chart The Task Burnup graph shows the cumulative increase in work for each release iteration in the project with the percentage of tasks that are on schedule late starting and late finishing indicated Welcome System Administrator My Profile Administration Log Out Library information System Help eee gt spiraTeam My Page Project Home Planning Testing Tracking Reporting Reporting gt Tasks Burnup Role Project Owner lt lt Back to Reports Home Task Graphs Task Summary Task Veloci
8. Q Ability to associate books with different subjects ifm Ability to associate books with different authors E Ability to associate books with different editions i 2 Ability to completely erase all books stored in th i a D Edition Management Not Covered a Author Management a D Subject Management Administration Functions Show rows per page Not Covered Not Covered o 0 o 0 0 o o 0 0 0 o a 0 o 0 Not Covered Planning Rete hem Gi Epon lt 4 n t ond oS J t x ih Welcome Fred Bloggs My Profile Log Out Tracking Reporting Show hide columns Y Fiter Role Manager In Progress In Progress ee Ce Co vE Completed y Completed Completed Completed Completed In Progress In Progress Planned Requested Ral gt Fiter RQ000001 Edit RQ000002 RQ000003 gt Edit RQ000007 gt Edit RQ000008 gt Edit RQ000009 FP Edit RQ000010 F Edit RQ000011 Edit RQ000013 Edit RQ000019 Edit 14 lt Displaying page i of 1 gt Pm If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to make the same change to multiple rows e g to change five requirements from In Progress status to Completed
9. are registered trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Explorer and Microsoft Project are registered trademarks of Microsoft Corporation All other trademarks and product names are property of their respective holders Please send comments and questions to Technical Publications Inflectra Corporation 8121 Georgia Ave Suite 504 Silver Spring MD 20910 U S A support inflectra com
10. 12 Mar 216 hours 0 2004 mins 15 hours 0 mins 15 hours 0 mins 14 hours 0 mins 15 hours 0 mins 10 hours 0 mins Est Effort 94 hours 0 mins 16 hours 0 mins 16 hours 0 mins 16 hours 0 mins 16 hours 0 mins 16 hours 0 mins 14 hours 0 mins Actual Effort 93 hours 30 mins 15 hours 30 mins 16 hours 50 mins 15 hours 10 mins 16 hours 0 mins 16 hours 0 mins 14 hours 0 mins 176 hours 0 RL2 1 0 1 0 Library System Release 1 SP1 pa INT Cannot log into the application Not able to add new author Incident Incident Cannot edd new book fo the system Bug 1 Critical 1 0 1 0 0001 Iteration 001 lteration 80 hours 0 mins 1 0 1 0 0002 Iteration 002 Iteration 48 hours 0 mins 1 0 1 0 0003 Iteration 003 iteration 64 hours 0 mins 352 hours 0 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 SpiraPlan SpiraTeam and Inflectra
11. 24 0h 72 0h 168 0h 336 0h 320 0h 24 0h 72 0h 72 0h 16 0h 94 0h RL000001 RL000002 RL000003 RL000008 RL000009 RL000010 RL000004 RL000005 RL000007 RL000017 RL000018 RL000019 RL000006 1 lt Displaying page a a of 1 gt p Show ss rows per page dp insert 3 Delete o gt Indent j lt Outdent Once you have the release iteration positioned at the correct place that you want it inserted just release the mouse button and the release list will be refreshed with the release iteration moved to the desired location 2 Alternatively you can simply select the check boxes of the release iteration you want to move and then select the Edit gt Cut menu option This will cut the current release iteration selection to the clipboard Then you should select the place where you want the release iteration to be inserted and choose the Edit gt Paste option The release iteration will now be moved into the destination location you specified 7 1 12 Exporting Releases Iterations To export releases iterations from the current project to another project in the system all you need to do is select the check boxes of the releases iterations you want to export and then click the lt Export gt button This will then bring up a list of possible destination projects spiraTest Requirements Releases a l Library System Release 1 Library System Release 1 SP1 h iteration 001 E iteration 002 E Iteration 0
12. Delete My Detected Incidents Not Executed Test Sets Library Information System gt Delete Name Project Type Date Opened W Cannot log into the application Library Information Incident 1 Nov 2003 My Assigned Requirements W Clicking on link throws fatal error Library Information Incident 1 Nov 2003 Name Importance W Cannot install system on Windows ME Library Information Issue 1 Dec 2003 Ability to create different editions Library Information 22 Ability to link authors to their contact flee DERA W Ability to associate multiple authors Library Information Enhancement 17 Nov 2003 Ability to edit existing authors in the Library information Cannot log into the application Sample Application O Incident 10 Dec 2003 Ability to delete existing authors in th Li eee eS W Test System Limitation Library Information Limitation 4 Dec 2003 Yy g brary se l Ability to create new users in the syste Library Information E Sample Risk 1 Foca i Saza prerii E S rr E W Test Training Item Library Information Training 3 Dec 2003 Ability po egacy system rary Information W Test Change Request Library Information Change Request 6 Dec 2003 W Support for IBM DB2 Library Information Enhancement 17 Nov 2003 W Test System Limitation Library Information Limitation 4 Dec 2003 W Sample Risk 2 Library Information Risk 10 Dec 2003 Abiit to create new book new book Library Information W Test Training
13. Library information System x gt spiraTeam My Page Project Home Planning Reporting Reporting gt Incidents Aging Role Project Owner lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Tumaround Time Incident Type x Date Interval Date Ending 10 19 2008 m d yyyy Incidents Aging 1 Crtical 2 High 3 Medum OO 4 Low 7 63 64 70 71 77 78 84 84 90 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 Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 3 8 Incident Turnaround Time Graph 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 s Welcome System Administrator My Profile Administration Log Out Library information System spiraTeam My Page Project Home Planning Testing Reporting Reporting gt Incidents Turnaround Time Role Project Owner lt lt Back to Repor
14. The types of change allowed will depend on how your project administrator has setup the system for you Administrators should refer to the SpiraTeam 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 Save gt lt Save and Close gt or lt Save and News to commit the new item or click on the Back to Incident List to discard the insertion and return back to the incident list 6 2 3 Resolution In this mode the lower section of the screen displays a threaded list of resolutions that have been logged against this incident Schedule Custom Props Attachments History Associations To add a new resolution or comment to this incident please enter it below and click the Update button isting Resolutions Comments Joe P Smith 11 Nov 2003 Retested and it looks good Fred Bloggs 10 Nov 2003 Fixed the permissions check in the admin module You can expand or collapse the list of existing resolutions by clicking the appropriate expand or collapse icon To add a new resolution to an incident all you need to do is enter the new resolution comment in the text box above the list and then click lt Update gt Your resolution will now be added to the existing items in the list 6 2 4 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for inc
15. This view displays the list of different versions that exist for the current document When you initially create a new document there will be only a single version e g v1 0 however as revisions are made to the document rather than having to create a whole new document you can just upload the new revision as a new version e g v1 1 and it will be added to the list of versions Each version in the list is displayed with its name a description of what changed in the version the version number assigned to the revision the file size who uploaded the new version and a link to actually open the new version T Version 1 2 Sequence diagram in UML format that provides additional 35 KB Fred Bloggs 10 May 2006 detail surrounding the book managament use case test case T Version 1 1 Sequence diagram in UML format that provides additional 30 KB Fred Bloggs 5 May 2006 gt Make Active Delete detail surrounding the book managament use case test case TE Version 1 0 Sequence diagram in UML format that provides additional 28 KB Joe P Smith 3 May 2006 gt Make Active Delete detail surrounding the book managament use case test case Upload New Version Filename Description Make this the active version On this page you have the option to delete an existing version make a different version the active one the one that users see when they view the document list and click on the link and upload a new revision If you upl
16. Training 3 Dec 2003 7 Develop new edition entry scre Library Information 12 Mar 200 7 Create edition object insert m Library Information 12 Mar 200 Z Write edition object insert qu Library Information 12 Mar 200 7 Refactor author screen to incl Library Information 10 Mar 200 In this mode each of the widgets displayed on the page can be minimized by clicking on the arrow icon in the top left of the window or closed by clicking on the cross icon in the top right of the window This allows you to customize your page to reflect the types of information that are relevant If you have closed a widget that you subsequently decide you want to reopen you can add them back to the page display by clicking the Add Items hyperlink at the top of the page In addition the various widgets have a settings icon that allows you to customize how that widget appears The settings are specific to each widget and in general allow you to specify how many rows of data are displayed and what columns are displayed You can move and reposition the various widgets on the dashboard by clicking the mouse on the title bar of the widget you want to move and dragging it to the desired location This change will be remembered when you next login to the system Once you have the dashboard configured the way you like it you can click Return to Normal View to switch back to view mode When you load your My Page for the firs
17. rows per page 4 lt Displaying page fi a of 1 gt EJE EEE EE EEEE EE E dp inset 3 Delete gt indent lt p Outdent 4 1 9 Show Hide Columns This drop down list allows you to change the fields that are displayed in the requirement 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 Requirements To copy a requirement or set of requirements simply select the check boxes of the requirements you want to copy and then select the Edit gt Copy menu option This will copy the current requirements selection to the clipboard Then you should select the place where you want the requirements to be inserted and choose the Edit gt Paste option The requirements will now be copied into the destination location you specified The name of the copied requirements will be prefixed with Copy of to distinguish them from the originals Note that copied requirements will also include the test coverage information from the originals 4 1 11 Moving Requirements To move a requirement
18. the lower section of the screen displays the list of documents that have been attached to the test step The documents can be in any format though SpiraTeam will only display the icon for certain known types Gb Expected Result Screenshot png i 314 KB Fred Bloggs 1 May 2006 Upload New Document URL Type File URL 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 step simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the test step you need to choose File as the type and then 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 test step To attach a web link URL to the test step you need to choose URL as the type and then enter the fully qual
19. 0 0 0 Library System Release 1 Cannot log into the appli anne mio te appi Priority 1 Critical v Resolved In Release 1 0 1 0 Library System Release 1 SP1 v Not able to add new autho w Clicking on link throws f Severity Verified In Release Database not backing up c Owned By Detected On 11 4 2003 12 00 00 AM Se stall system on Last Modified 5 7 2009 9 50 20 AM The book listing screen d Cannot add a new book to 8 Editing the date on a boo 8 Editing the date on an au X Doesnt let me add a new w Validation on the edit bo E Quote handling issues thr E The tables get cutoff on E Permissions not updating peer E Session handling Description When click on the button to add a book enter the new information and click submit get a subscript out of range error This page is made up of three areas the left pane is the navigation window where you can quickly jump to other incidents as well as execute workflow transitions see below the upper part of the right pane contains the incident detailed information itself and the bottom part of the right pane displays different information associated with the incident The left hand navigation pane consists of a link that will take you back to the incident list as well as a list of the other related incidents that match the currently selected sort and filter option on the incident list page If the number of incidents exceeds fifteen only
20. Administration Log Out Library information System x ET 2 spiraTeam Project Home Planning Tracking Requirements Releases Iterations indent lt Outdent Refresh hedt Exot Show hide columns Y Fiter Task Progress Start Date End Date Plan Effort TaskEffort Iteration Release Id L Ell Ell JI e vie G Library System Release 1 1 0 0 0 yom 14 Mar 2004 12 Mar 2004 216 0h 94 0h No RLO00001 P Edit Library System Release 1 SP1 1 0 1 0 No Tasks 13 Mar 2004 30 Mar 2004 176 0h No RLO00002 P Edit 5 Q Library System Release 1 SP2 1 0 2 0 No Tasks 1 Apr 2004 30 Apr 2004 352 0h No RLO00003 P Edit Library System Release 1 1 1 1 0 0 Ns 15 0ct 2004 27 Oct 2004 168 0h No RLO00004 P Edit Library System Release 1 1 SP1 1 1 1 0 No Tasks 1 Nov 2004 30 Nov 2004 336 0h No RL000005 Peake Library System Release 1 1 SP2 1 1 2 0 lo Test No Tash 1 Dec 2004 31 Dec 2004 320 0h No RL000007 Edt B Library System Release 2005 1 2 0 0 Py 14 Apr 2005 2 Apr 2005 16 0h No RL000006 Edit stated ie id lt Displaying page a of 1 gt gt ooaooa0ag 0 w 7 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 or press the lt ENTER gt key to apply the different filters Note that the name field is searched using a LIKE compar
21. Caution User logs in to application User clicks link to create book User enters books name and author then clicks Next User chooses book s genre and sub genre from list User clicks submit button File Attachments Filename Description Author Date Uploaded Sequence Diagram for Book Mat pdf Sequence diagram in UML format that provides additional detail surrounding the book managament use case test case Fred Bloggs 03 May 2006 11 2 6 Test Run Summary Report This report displays all of the test runs defined for the current project The test run s details and execution status are displayed in a summary grid form Test Run Summary Report This report displays all of the test runs defined for the current project in date order most recent first The test run s details and execution status are displayed in a summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Test Run Name Test Case Release Test Set Type Tester Est Duration Actual Duration Start Date End Date Status Runner Ability to Fred OhoursS 0 hours 50 01 Dec 01 Dec TR10 vin existing TC3 1 0 0 0 Manual Bloggs mins miis 2003 2003 Caution Ability to create new TC2 book Fred 0 hours 10 1 hours 10 01 Dec 01 Dec Bloggs mins ha 2003 2003 Failed NUnit Opera Windows 2003 Ability to create new TC2 1 1 0 0 0001 Fred 0 hours 2 1 hours 10 02 D
22. D Functional System Requirements RQ000001 5 Online Library Management System Sample Applicaton One RQ000002 F Book Management RQ000003 Ability to add new books to the system gt Export Cancel RQ000004 5 Ability to edit existing books in the system RQ000005 ree Ability to delete existing books in the system RQ000006 yee Ability to associate books with different subjects RQ000007 8 Ability to associate books with different authors Completed RQ000008 oO Ability to associate books with different editions i Completed RQ000009 Ability to completely erase all books stored in th i Completed RQ000010 D Edition Management Not Covered In Progress RQ000011 a Author Management Not Covered In Progress RQ000013 3 3 Subject Management Not Covered Planned RQ000019 D Administration Functions Not Covered 3 Medium Requested RQ000022 GP insert 3 Delete gt indent lt Outdent Once you have chosen the destination project and clicked the lt Export gt button the requirements will be exported from the current project to the destination project Any file attachments will also be copied to the destination project along with the requirements 4 2 Requirement Details When you click on a requirement item in the requirements list described in section 4 1 you are taken to the requirement details page illustrated below Welcome Fred Bloggs My Profile Administration Log Out as e spiraTeam My Page Project Hom
23. Failed Passed C NotRun O N A Blocked M Caution 10 7 2003 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 In this version of the report the y axis represents the number of test runs executed in each 24 hour period and the x axis represents a specific day in the time span Each data bar 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 release that the test run was executed against and also change the ending date of the date range By clicking on the weekly radio button you can display the past 12 months of test run data organized on a weekly basis Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 3 Incident Reports 11 3 1 Incident Summary Report This report displays all of the incidents tracked for the current project The incident s details are displayed in a summary list form Incident Summary Report This report displays all of the incidents tracked for the current project The incidents details are displayed in a summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Inc Name Description When trying to log into the Resolution Type Status Priority Severity Detec
24. 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 5 1 4 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 SpiraTeam is explained in more detail in section 5 3 5 1 5 Refresh Clicking on the lt Refresh gt button simply reloads the test case list This is useful as other people may be modifying the list of test cases at the same time as you or executing specific test cases and after stepping away from the computer for a short time you should click this button to make sure you are viewing the most current test case list for the project 5 1 6 Edit Each test case in the list has an lt Edit gt button display in its right most column When you click this button or just click on any of the cells in the row 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 Welcome Fred Bloggs My Profle Log Out Help My Page Project Home Planning Testing Tracking Reporting n spiraTeam Test Cases Test Sets Role Manager Gp inset 3 Delete lt gt indent lt p Outdent Q Refresh Qheat Toos Show hide columns Y Fiter
25. Joe P Smith 04 Nov 2003 File Attachments Filename Description Author Date Uploaded Error Logging in Screen shot gif Captured screen shot of the error that was raised when attempting to log in to the library application Fred Bloggs 24 Apr 2006 11 2 8 Test Case Summary Graph The test case summary graph shows how many test cases are currently in a project The number of test cases is displayed according to the criteria that you specify You can specify the type of data displayed along the x axis and the test case information which is used to group the data When you first open the graph you will be asked to pick the field that you would like to display on the x axis and the field that you would like to group the data by Once you have chosen the appropriate fields and clicked the lt Select gt button the graph will be displayed Kis Grouped By Test Cases Summary E 1 Critical M 2 High MH 3 Medium Caution Not Run In this version of the report the x axis represents the test case execution status and the individual bars are grouped by test case priority Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 2 9 Test Run Summary Graph The test run Summary graph shows how many test runs are currently in a project The number
26. Log Out S Incidents Tasks SP NewTask 3 Delte Refresh Copy E Export Y Fiter raana 1 4 out of 4 task s for this project My Page Project Home Planning i Tracking Z Create edition object insert method In aan 1 Critical Fred Bloggs 1 0 0 0 0003 TK000022 Z Develop new edition entry screen Develop new edition entry screen new edition entry screen EJ in Progress Y E 1 Crea YJE Fred Bloggs YED 1 0 0 0 0003 V E L Write author object delete query i in Progress V 2 High v Fred Bloggs Y Z Create author object delete method a In Progress 2 High Fred Bloggs 1 0 0 0 0003 TK000028 Show rows per page 4 lt Displaying page fi of 1 gt gt If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to make the same change to multiple rows e g to change five tasks from Not Started status to In Progress you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the
27. Open Issues Top Open Risks Test Execution Status Release Test Summary Incident Summary Incident Open Count VV VV VV VV VV V Vv Requirement Incident Count However these are not the only widgets available If you click on the Add Remove items hyperlink it will display the list of any additional widgets that are available Add Remove Items Close Select the catalog you would like to browse Closed Vidgets 0 Available Widgets 4 Available Widgets LJ Requirements Regression Coverage C Test Set Status LJ Incident Aging dl ncident Test Coverage Add to mae You can add the additional widgets by selecting the appropriate checkbox choosing the destination location left side vs right side and then click the Add button The additional widgets available in the Project Home dashboard are gt Requirements Regression Coverage gt Test Set Status gt Incident Aging gt Incident Test Coverage Each of the different widgets listed is described in more detail 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 proj
28. P Smith TC000007 E Book management 1 Dec 2003 Joe P Smith TC000008 Author management Not Run 1 Dec 2003 Joe P Smith TC000009 amp Common Tests 0 1 Dec 2003 Fred Bloggs TC000015 Pp inset 3 Delete gt Indent lt p Outdent gt Execute Once you have chosen the destination project and clicked the lt Export gt button the test cases will be exported from the current project to the destination project Any file attachments will also be copied to the destination project along with the test cases 5 1 13 Adding Test Cases to a Release or Test Set To quickly add a series of test cases to either a Release or Test Set all you need to do is select the check boxes of the appropriate test cases and then click Tools gt Add to Release Test Set This will then bring up a dialog box displaying either a list of available releases or a list of available test sets depending on which option was chosen Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing spiraTest Test Cases Test Sets qP inset 3 Delete lt gt Indent lt p Outdent ShowLlevel v Refresh Toots gt Execute Show hide columns v Y Clear Filters Display data for 1 0 1 0 Library System Release 1 SP1 Fred Bloggs Z Ability to create new book ee a 2003 Fred Bloggs Tc000002 z Ability to edit existing book 2003 Fred Bloggs TC000003 5 Ability to create new author la nen Fred Bloggs TC000004 Ability to e
29. Profile Administration Log Out My Page Project Home Planning Tracking Reporting z spiraTeam S My Page Welcome Fred Bloggs to Your Dashboard Modify Layout Settings Add Items My Projects My Assigned Incidents Project Name Group Creation Date Name Project Type Priority Date Opened Library Information System Internal Projects 1 Dec 2005 W Ability to associate multiple authors Library Information Enhancement 17 Nov 2003 Sample ication One internal Projects 1 Dec 2005 W Test System Limitation Library Information Limitation 4 Dec 2003 Sample Application Two External Projects 1 Dec 2005 W Test Training item Library Information Training 3 Dec 2003 W Editing the date on a book is clunky Library Information Bug 4 Nov 2003 My Saved Searches W Test Training Item Library Information Training 3 Dec 2003 Namo Project W Test Change Request Library Information Change Request 7 Dec 2003 Critical Not Covered Requirements Library Information System gt Delete E Ability to import data from excel Library information Enhancement 25 Nov 2003 2 Failed Active Test Cases Library Information System gt Delete E Test System Limitation Library Information Limitation 4 Dec 2003 W New Unassigned Incidents Library Information System gt Delete Sample Risk 3 Library Information Risk 10 Dec 2003 W All Reopened Incidents Library Information System gt Delete Z High Priority Late Tasks Library Information System gt
30. Run List amp 4 Dec 2003 TRO00018 Test Run Ability to create new book TR 000001 Z 3 Dec 2003 TR000015 Tests that the user can create a new book in the system P 2 Dec 2003 TR000013 P 1 Dec 2003 TR000012 Z 1 Dec 2003 TRO00002 Release 10 0 0 R 1 v Estimated Duration fos hours minutes 1 Dec 2003 TR000001 4 Tester Name Actual Duration fi hours his minutes Test Set Testin Execution Date 12 1 2003 10 45 20 AM Test Case TC000002 Execution Status Failed 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 The main pane displays the details of the test run itself name description release test set 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 any custom properties set for the run and a list of any documents URLs that were attached to the test results 5 5 1 Editing a Test Run When reviewing the test run you may find that you need to change the results of the test run e g the user selected the wrong release or custom property value Many of the fields are editable at a later date and to make changes just modify the appropriate fields and clic
31. Size Acrobat fj 35 KB Last Edited 5 10 2006 12 00 00 AM Current Version 1 2 This page is made up of three areas the left pane is for navigation the upper part of the main pane contains the details of the document and the bottom part of the right pane contains the list of document versions and the list of artifacts that the document is associated with The navigation pane consists of a link that will take you back to the project document list as well as a list of other documents in the current folder This latter list is useful as a navigation shortcut you can quickly view the detailed information of all the peer documents by clicking on the navigation links without having to first return to the main document list page The top part of the main pane allows you to view and or edit the details of the particular document You can edit the various fields name description etc and once you are satisfied with them simply click the lt Save gt button at the top of the page to commit the changes In addition you can delete the current document by choosing lt Delete gt or discard any changes made by clicking lt Refresh gt The lower part of the main pane can be switched between two different views by clicking the appropriate tab Initially the pane will be in Versions mode but it can be switched to Association as well The functionality in each of these two views is described below 10 2 1 Edit Document Versions
32. System Administrator 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 9 Resource Tracking This section outlines how you can use the Resource Tracking features of SpiraPlan and Spiraleam to view the total workload for each of the project personnel resources assigned to a specific project This allows you to verify that the work is evenly distributed amongst the project members and that no individual resource is overloaded When you click on the Tracking gt Resources link on the global navigation bar you will initially be taken to the project resources list screen illustrated below gt Welcome Fred Bloggs My Profile Log Out spiraTeam My Page Project Home Planning Tracking incidents Tasks Resources Role Manager Refresn Y Fiter Displaying the resource usage for the current project or selected release Display data for 1 0 0 0 Library System Release 1 v ov ResourceName AY eS go Fred Bloggs Manager US000002 g Joe Smith Observer US000003 Show is Y rows per page i4 lt Displaying page h of 1 gt pi This screen lists all the personnel project resources that belong to the current project together with the total value of the estimated effort of all the work assigned to th
33. TC000017 id lt Displaying page fi Role Manager ails i m Q v Y 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 or press the lt ENTER gt key 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 Owner None In addition if you have a set of filters that you plan on using on a regular basis you can choose the option Filter gt Save Filter to add the current filter to the list of saved filters that appear on your My Page The list of saved filters can also be retrieved by clicking Filter gt Retrieve Filter Lidrary Information System v My Page Project Home Planning Testing Welcome Fred Bloggs My Profile Log Out gt spiraTeam S Test Cases Test Sets rasan G3 Deete gt dent lt Ouen Sawn es E Tos Y fae Displaying 4 out of 11 test case s for this release Save Filter z Ability to reassign book to different author amp Regression Tests 2 z Book management z Author management 5 Common Tests 2 1 Dec 2003 1 Dec 2003 zJ Open Up Web Browser 1 D
34. TKO00031 TK000032 TK000043 1 lt Displaying page a of 1 gt h Joe P Smith gt The top part of the screen displays the iterations contained within the current release up to three per page together with the list of tasks and incidents currently assigned to the iteration Also any tasks incidents directly associated with the release itself are displayed in the first panel gt The bottom part of the screen displays the list of unplanned not started tasks and unplanned open incidents that need to be associated to an iteration This is essentially the backlog of tasks linked to requirements and outstanding incidents that need to be scheduled The tasks are show in one tab and the incidents are shown in the other To navigate around the release you use the small black arrow buttons located at the top of the iteration panels These allow you to quickly move to the previous next iteration in the currently selected release To change the release itself you use the drop down list at the top right of the page to change to a different release 7 3 1 Scheduling Tasks Incidents to Iterations To assign a new task incident to the iteration schedule you either position the mouse pointer over a single task incident icon dragging it to the desired iteration or you select several checkboxes in the task incident list and then drag all the selected items in one go Once the task incident s have been added to the iteration the estima
35. and the x axis can be configured to display three different levels of granularity gt All Releases This shows the total remaining work that needs to be done for each of the releases in the project gt Specific Release This shows the total remaining work that needs to be done for each of the iterations in the selected release gt Specific Iteration This shows the total remaining work that needs to be done for each working day in the date range covered by the selected iteration 11 5 Release Reports 11 5 1 Release Summary Report This report displays all of the releases and iterations defined for the current project in the order they appear in the release iteration hierarchy The release s details are displayed in a summary list form Release Summary Report This report displays all of the releases and iterations defined for the current project in the order they appear in the release iteration hierarchy The release s details are displayed in a summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library General Testing Information Rel Name Version Number Description Creator Creation Date Iteration Active Start Date End Date Failed Passed Blocked Caution Not Run Task Progress Planned Effort 18 Tasks This is the 50 On Library initial Schedule 12 Running eb release of Fred 15 Feb 2004 N 12 M
36. 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 will 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 Tasks Test Cases Custom Props Test Runs Attachments History Display Ea ot Ines nnn ENE Detected in This Release Incident Name Type Status Priority Owned By Detected On Detected By IN000007 W Cannot add a new book to the system Bug Assigned 1 Critical Joe P Smith 4 Nov 2003 Joe P Smith IN000002 RE Not able to add new author Incident New 1 Nov 2003 Joe P Smith IN000001 B Cannot log into the application Incident New 1 Nov 2003 Fred Bloggs Displaying 1 3 of 3 incid
37. displayed with an icon that helps distinguish them from each other and provides additional context on the state of the artifact Icon Artifact Description O O Test Set E Incident Capa oo mm ooo Artifact has an Attachment 3 User Project Management This section outlines how you can log into SpiraTeam 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 SpiraTeam URL provided by your system administrator into your browser you will see the following login screen Please enter your user name We Ico me to and password then click the log in button a User Name spirafeam om we Version v2 0 1 Copyright C 2006 2008 Inflectra Corporation Forgot your password Don t have an account inflectraZ 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 SpiraTeam
38. ests T No Tasks No Tasks 1 Mar 2004 13 Mar 2004 13 Mar 2004 21 Mar 2004 25 Mar 2004 1 Apr 2004 1 Apr 2004 11 Apr 2004 21 Apr 2004 1 Mar 2004 5 Mar 2004 9 Mar 2004 15 Oct 2004 1 Nov 2004 1 Dec 2004 12 Mar 2004 30 Mar 2004 20 Mar 2004 24 Mar 2004 30 Mar 2004 30 Apr 2004 10 Apr 2004 20 Apr 2004 30 Apr 2004 4 Mar 2004 8 Mar 2004 12 Mar 2004 27 Oct 2004 30 Nov 2004 31 Dec 2004 216 0h 176 0h 80 0h 48 0h 64 0h 352 0h 112 0h 112 0h 128 0h 96 0h 24 0h 72 0h 168 0h 336 0h 320 0h 94 0h RL000001 RL000002 RL000011 RL000012 RL000013 RL000003 RL000014 RL000015 RL000016 RL000008 RL000009 RL000010 RL000004 RL000005 RL000007 4 lt Displaying page h Ta of 2 pi The release list will contain all the releases and iterations 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 and iterations to the project The hierarchical organization of releases in the list is configurable so you can organize the various releases in the way 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 start date and end date for the release the number of esti
39. for executing the test cases contained within the test set against a specified release of the system under test To aid in this process the test set name is displayed along with its status the project it belongs to the number of remaining test cases to be executed and the date by which all the tests need to have been run If you click on the test set name hyperlink you will be taken to the details page for this test set see section 5 6 and the project that the test set belongs to will be made your current project If you click on the gt Execute link listed below it will actually launch the test cases contained within the test set in the test case execution module see section 5 4 so that you can easily carry out your assigned testing task 3 2 6 My Pending Test Runs This section lists any test runs that you started executing in the test case module but haven t yet completed Once a test case or test set is executed a pending test run entry is stored in the system so that you can continue execution at a later date Any pending test run can be either deleted or resumed by clicking on the appropriate link 3 2 My Assigned Tasks This section lists all the project tasks that you have been made the owner of across all the different projects you are a member of This typically means that the manager of the project in question has assigned development tasks to you that need to be completed so that a release can be completed and or a r
40. gt Execute Show hide columns Y Clear Filters Displaying 9 out of 13 test case s for this release Display data for All Releases Author Active Test Te amp Functional Tests 5 Fred Bloggs 1 Dec 2003 Fred Bloggs TC000001 Fred Bloggs 1 Dec 2003 Fred Bloggs Tc000002 Fred Bloggs 1 Dec 2003 Fred Bloggs TC000003 Joe P Smith 1 Dec 2003 Fred Bloggs TC000004 2 Ability to edit existing author Joe P Smith 1 Dec 2003 Fred Bloggs TC000005 2 Ability to reassign book to different author Joe P Smith 1 Dec 2003 Fred Bloggs TC000006 amp Regression Tests 2 1 Dec 2003 Joe P Smith TC000007 E Book management 1 Dec 2003 Joe P Smith TC000008 E Author management 1 Dec 2003 Joe P Smith TC000009 amp Scenario Tests 2 Joe P Smith Joe P Smith TC000010 amp Common Tests 2 1 Dec 2003 Fred Bloggs TC000015 E Open Up Web Browser 1 Dec 2003 Fred Bloggs TC000016 E Login to Application 1 Dec 2003 Fred Bloggs TC000017 s Ss rows per page m lt Displaying page a Ya of 1 gt gt dh insert 3 Delete lt gt indent lt Outdent gt Execute amp 2oOoo0oo0oo0oRo RF 0c0000 004g z Once you have the test case folder positioned at the correct place that you want it inserted just release the mouse button and the test case list will be refreshed with the item moved to the desired location 2 Alternatively you can simply select the check boxes of the test cases you want to move and then select the Edi
41. 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 can have the different testing teams correctly assign their testing actions to the appropriate version There are two types of release artifact in SpiraTeam major project releases that are displayed with the blue release icon and represent major versions of the system and release Iterations aka builds that are displayed with a yellow icon and represent intermediate builds iterations of the system Note Iterations can be contained within a Release but not the other way round The main differences between releases and iterations are as follows gt Releases are independent versions of the system being tested and as such you can map a requirement directly to a release indicating the release of the system that the requirement will be fulfilled in gt When you report on a release e g on the project home or in one of the reports any child iterations are automatically taken into account and te
42. list page The top part of the right pane allows you to view and or edit the details of the particular test step You can edit the various fields description expected result and sample data and once you are satisfied with them simply click the lt Save gt button just below the fields to commit the changes If you want to add a new test step to the test case you should click lt Save and News gt instead The lower part of the right pane can be switched between four different views by clicking the appropriate tab Initially the pane will be in Incidents mode but it can be switched to Custom Properties Attachments and History modes if so desired Each of the views is described separately below 5 3 1 Incidents In this mode the main pane displays a list of any incidents that are associated with this test step They can either be linked indirectly due to being logged during a test run or directly linked after the fact Custom Properties Attachments History dp Add 3 Delete 4 Nov 2003 W Cannot add a new book to the system Joe P Smith Test Run Ability to create new book Incident INO00007 Each incident is displayed with its name the name of the person who executed the test run or made the direct association and a comment that describes why the association was made In the case of a test run the comment will simply contain the name of the test run To create a new association between this test st
43. navigation bar consisting of six section tabs My Page Project Home Planning Testing Tracking and Reports that correspond to the main activities that take place in the system as well as three secondary links to My Profile and Log Out and Help Under the various tabs are several secondary menu options that are displayed when you hover the mouse over the appropriate tab as illustrated below gt Project Home gt Project Home described in Section 3 4 gt Documents described in Section 10 gt Planning gt Requirements described in Section 4 gt Releases described in Section 7 gt Iterations described in Section 7 3 gt Testing gt Test Cases described in Section 5 gt Test Sets described in Section 5 6 gt Tracking gt Incidents described in Section 6 gt Tasks described in Section 8 gt Resources described in Section 9 gt Reports described in section 11 Note The main tabs will take you to the appropriate artifact type requirement test case incident etc for the currently selected project However if you haven t selected a project then clicking on any of the tabs will simply take you back to My Page so that you can select a project 3 3 1 Log Out Clicking on the Log Out link will immediately log you out of your current session and return you to the login page illustrated in section 3 1 If you had set the Remember Me option during your prev
44. of test runs is displayed according to the criteria that you specify You can specify the type of data displayed along the x axis and the test run information which is used to group the data When you first open the graph you will be asked to pick the field that you would like to display on the x axis and the field that you would like to group the data by Once you have chosen the appropriate fields and clicked the lt Select gt button the graph will be displayed X Axis Grouped By Test Runs Summary E Automated Manual Caution In this version of the report the x axis represents the test run execution status and the individual bars are grouped by test run type Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 2 10 Test Run Progress Rate Graph The test run progress rate graph shows how many tests have been executed during a period of time and what execution status was recorded The 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 progress rate report loaded with the past 60 days of test run data depicted on a daily basis Release Date Interval Daily Weekly Date Ending Test Runs Progress Rate E
45. of optional parameters that can be set on the task These can be either freetext or drop down lists In the example below you can enter Comments and or the project track that the task is associated with General Custom Properties Attachments History Please edit the follawing custom properties of this artifact and click Update when finished Comments Track Infrastructure Once you are satisfied with the values for the custom properties simply click Update to commit the changes 8 2 3 Attachments In this mode the lower section of the screen displays the list of documents that have been attached to the task The documents can be in any format though SpiraTeam will only display the icon for certain Known types General Custom Properties E Customers_xls 163 KB System Administrator 26 Feb 2008 Upload New Attachment Filename Description Sample data that should be used when developing feature 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 fo
46. 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 SpiralTeam account setup clicking on the Don t have an account link will take you to a form that you need to fill in which will be forwarded to the system administrator who will actually create your account In addition the system will prevent you logging on to the system with the same username at the same time on multiple computers This is to avoid the system getting confused by a user trying to make contradictory 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 spiraTeam ee You can either Log Out and try a different user name or Sian Off The Other Locations to force the other Version v2 0 1 pian EE a locations to la
47. see section 6 You start test case execution in SpiraTeam by either selecting test cases or test sets on their respective page s and clicking the lt Execute gt button or by clicking the Execute link on the test cases test sets listed on your personalized home page under My Test Cases or My Test Sets If you execute a test set then the values of the selected release and custom list properties for the test run are automatically populated from the test set whereas if you directly execute a test case itself those values can be chosen by the tester Regardless of the route taken to launch the test execution module the first screen that will be displayed will look like the following Welcome Fred Bloggs My Profile Log Out L rery information System x spiraTeam My Page Project Home Planning Testing Tracking Test Cases gt Test Case Execution Test Sets Role Manager lt lt Back To Tests Testing New Functionality TX5 Test Execution Wizard Please Choose the Release To Execute Against Release Now enter the following properties for this test run Notes Web Browser Operating System 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 r
48. specify the ending date of the date range Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 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 11 3 5 Cumulative Incident Count Graph The cumulative incident count chart displays the cumulative total number of incidents logged in the system for the current project 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 System Administrator My Profile Administration Log Out Library Information System Help es spiraTeam My Page Project Home Planning Testing Tracking Reporting Reporting gt Incidents Progress Rate Role Project Owner lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Turnaround Time Incident Type All Date Interval Daily Weekly Date
49. step list see above you will be taken to the test step details screen illustrated below a gt Welcome Fred Bloggs My Profile Administration Log Out Lbrary Information System v Help spiraTeam My Page Project Home Planning Testing Tracking Reporting Test Cases gt Test Step Details Test Sets Role Manager lt lt Back to Test Step List Save pSaveandNew 3 Delete Z Ability to create new book Test Step 3 TS 000003 Test Case 1000002 Descripion ra I Step 2 TS000002 Step 3 TS000003 Step 4 TS000004 Step 5 TS000005 4 p To Macbeth William Shakespeare Attachments V Date ArtifactName Created By Comment Artifact Type Artifact Cl dhadi 3 Delete 4 Nov 2003 W Cannot add a new book to the system Joe P Smith Test Run Ability to create new book Incident IN000007 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 step detailed information itself and the bottom part of the right pane contains related information about the test step The navigation pane consists of a link that will take you back to the test step list as well as a list of the peer test steps 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 steps by clicking on the navigation links without having to first return to the test step
50. the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to make the same change to multiple rows e g to change five incidents from Resolved status to Closed you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the lt ESCAPE gt key will cancel the changes Note that in the case of incidents you need to have Project Owner permissions for the project to make bulk changes using the lt Edit gt button as such changes can override the workflow business rules established 6 1 7 Copying Incidents To copy an incident or set of incidents simply select the check boxes of the incidents you want to copy and then click lt Copy gt This will make a copy of the current incident with its name prefixed Copy of to distinguish itself from the original Any file attachments will also be copied along with the incident itself 6 1 8 Exporting Incidents To export an incident or set of incidents from the current project to another project in the system all you need to do is select the check boxes of the incident s you want to export and then click
51. the item from a hierarchical list box and in the case of incidents you can either enter the incident ID or choose from a list of incidents you have recently submitted In either case you can also add a comment that explains the rationale for the association Add New Association Step 2 of 2 Add New Association Step 2 of 2 Please choose the requirement that you want to add an association to Please choose the incident that you want to add an association to Enter Incident Add from history Sample Risk 1 Ability to edit existing books in the system Ability to delete existing books in the system Ability to associate books with different subjects Test Change Request Ability to associate books with different authors Test Change Request Ability to associate books with different editions Test Change Request Ability to completely erase all books stored in the system with one click Test Change Request Test Change Request Test Change Request Comment Finally to delete an existing association except for those due to test runs select the check box next to its name and click the lt Delete gt icon This will only delete the association not the linked artifact itself 5 Test Case Management This section outlines how the use case test case management features of SpiraTest and Spiraleam can be used to develop the business use cases for the system which specify how the different pieces of functionality are expected
52. 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 clicking on the Incident tab and entering a name type priority severity and any custom properties for the new incident before clicking the lt Fail Caution Blocked gt button The screen displays a 404 error message page fee Attachments Please enter the following information to log an incident with this test step Cannot login to the web page correctly Priority 1 Critical we severity 2 High we Also enter the following custom properties for this new incident ee Operating System 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 If you need to attach documents to the test run e g screenshots of the error message you just need to select the Attachments tab and then choose the option to upload the necessary documents or attach the appropriate URLs Note that the entire test run is saved once you first start execution so you can always step away from your
53. the right Similarly the lt 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 SpiraTeam 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 i 35 KB Fred Bloggs 3 May 2006 Upload New Document URL Type File URL 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 choose File as the type and then click the Browse button and select the file from your local comput
54. typically selections from multi valued dropdown lists and date ranges gt Custom Property Filters This allows you to constrain the range of data being reported on based on the custom fields associated with the artifact by your project administrator These filters can be either freetext or drop down lists gt Sort Options This option is only available for the non hierarchical data reports i e for test runs incidents and tasks only and allows you to specify the sort order of the results returned in the report For the hierarchical data based reports the sort order is always the order of the hierarchy gt Report Name If you would like to save the report configuration so that you can quickly re run it at a later date you just need to enter a name for the report and indicate by selecting the checkbox or not whether you want this report to be private or shared by all members of the project 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 11 1 Requirements Reports 11 1 1 Requirements Summary Report This report displays all of the requirements defined for the current project in the order they appear in the requirements list The requirement s details and coverage status are displayed in a summary list form gt Print Report Requirements Summary Report This report displays al
55. whether to use Priority or Severity for the display and also how many rows of data to display 3 6 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 Please review the information listed below and make any changes if necessary Once you have finished click Update to confirm them First Name red Middle Initial Last Name loggs User Name edbloggs Email Address fredbloggs mycompany com LDAP DN N A L Change Password Current Password New Password Confirm Password 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 6 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 i
56. 000018 4 1 0 0 0002 Iteration 002 Active 1 1 0 0 Library System Relea RLO00019 1 1 0 0 0003 Iteration 003 Active O 1 2 0 0 Library System Relea 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 The pane consists of two lists of releases iterations the one on the left being the complete hierarchical list of releases and iterations in the project The right box which will initially be empty contains the list of releases iterations mapped to this test case The releases in this box include columns for their ID name and active status Hovering the mouse over the names of the releases iterations in either box will display a tooltip consisting of the release iteration name place in the hierarchical structure and a detailed description Clicking on the hyperlinks in right hand box will jump you to the details screen for the release iteration in question 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
57. 018 RL000019 RL000006 2o000cgogoo000 0 000 z rows per page id lt Displaying page 1 of 1 gt b gt Gp insert 3 Delete lt gt indent lt Outdent If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to make the same change to multiple rows e g to change five releases from active to inactive you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the lt ESCAPE gt key will cancel the changes 7 1 8 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 9 Show Hide Columns This drop down list allows you to change the fields that are displayed in th
58. 03 5 Library System Release 1 SP2 E iteration 001 E iteration 002 B iteration 003 E iteration 001 E iteration 002 E iteration 003 aO Library System Release 1 1 Select Project 1 0 2 0 0001 1 0 2 0 0002 1 0 2 0 0003 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 1 1 0 0 1 2 0 0 Planning hg gt Export Cancel 5 May 2004 5 Jun 2004 Jun 2004 5 Jun 2004 5 Jun 2004 15 Feb 2004 15 Feb 2004 15 Feb 2004 15 Oct 2004 1 Apr 2005 Welcome Fred Bloggs My Profile Log Out Project Home Tracking Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Reporting Role Manager keraton Releaseld Edit RL Frer RL000001 RL000002 RL000011 RL000012 RL000013 RL000003 RL000014 RL000015 RL000016 RL000008 RL000009 RL000010 RL000004 RL000006 2 Library System Release 2005 cP insert 3 Delete gt indent lt p Outdent Once you have chosen the destination project and clicked the lt Export gt button the releases iterations will be exported from the current project to the destination project Any file attachments will also be copied to the destination project along with the release iteration 7 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 Library information System v Testing a Welcome Fred Bloggs My
59. 1 an optional description and then click the lt Upload gt button to attach the web link 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 5 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 Props Attachments Associations 5 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 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 4 2 6 Associations In this mode the main pane displays a list of any incidents or other requirements that are associated with this requirement Test Coverage Tasks Custom Props Attachments History nr Add Delete 14 Mar 2004 Cannot install system on Oracle 9i Fred Bloggs This bug affects the requirement Incident INO00005 12 Mar 2004 Ability to delete existing books in the syst
60. 1 below Your homepage contains all the information relevant to you consolidated onto a single page for you to take immediate action By default the page lists the information for all projects that you are a member of However you can choose to filter by the current project to get a more focused list Initially the page is loaded in view mode which means that the various widgets on the page are displayed with minimum visual clutter no toolbars or control icons that makes it easy to scan the items on the page and see what work has been assigned To switch the page to edit mode click on Modify Layout Settings hyperlink Welcome Fred Bloggs My Profile Administration Log Out My Page Project Home Planning Tracking Reporting a 3 spiraTeam S My Page Welcome Fred Bloggs to Your Dashboard Return to Normal View Add Items Creation Date Priority Date Opene W Ability to associate multiple authors Library Information Enhancement 17 Nov 2003 W Test System Limitation Library Information Limitation 4 Dec 2003 E Test Training Item Library Information Training 3 Dec 2003 W Editing the date on a book is clunky Library Information Bug 4 Nov 2003 E Test Training Item Library Information Training 3 Dec 2003 E Test Change Request Library Information Change Request 7 Dec 2003 W Ability to import data from excel Library Information Enhancement 25 Nov 2003 E Test System Limitati
61. 1 m o spiraleam spiraPlan we my i spirafest a SpiraTeam User Manual Version 2 3 Inflectra Corporation inflectraZ 7 3 Iteration Planning 86 Contents 8 Task Tracking 88 1 Introduction 2 eae Uden et ee l 8 2 Task Details 91 1 1 Quality Assurance 2 1 2 Project Management 2 9 Resource Tracking 24 2 Functionality Overview 3 10 Document Management 95 2 1 Requirements Management 3 10 1 Document List 95 2 2 Test Case Management 3 10 2 Document Details 96 2 3 Release Planning 3 11 Reports Center 99 2 4 Iteration Planning 4 11 1 Requirements Reports 102 2 5 Incident Tracking 4 11 2 Test Case Reports 105 2 6 Task Management 4 11 3 Incident Reports 110 2 Projects and Users 5 11 4 Task Reports 116 2 7 Miscellaneous 5 11 5 Release Reports 119 3 User Project Management 7 3 1 Login Screen 7 3 2 My Page 9 3 3 Global Navigation 13 3 4 Project Home 16 3 5 Project Group Home 23 3 6 My Profile 26 4 Requirements Management 27 4 1 Requirements List 27 4 2 Requirement Details 32 5 Test Case Management 37 5 1 Test Case List 37 5 2 Test Case Details 43 5 3 Test Step Details 50 5 4 Execute Test Case s 53 5 5 Test Run Details 56 5 6 Test Set List 61 5 7 Test Set Details 64 6 Incident Tracking 67 6 1 Incident List 67 6 2 Incident Details 70 7 Release Management 76 7 1 Release List 76 7 2 Release Details 81 1 Introduction SpiralTeam is an integrated Application Life
62. 13 Name Ability to create new book Book management Adding new book and author to library ink ir Name Ability to delete existing books in the system Associated Incidents Name Cannot install system on Oracle 9i Cannot add a new book to the system Associated Tasks 11 1 3 Requirements Plan 3 Covering 1 Failed 1 Passed 0 Blocked 0 Caution Created By Fred Bloggs Created By Fred Bloggs Joe P Smith Status 42 Tasks 60 On Schedule 6 Running Late 4 Starting Late 29 Not Started 42 Tasks 60 On Schedule 6 Running Late 4 Starting Late 29 Not Started Creation Date Last Modified Planned Effort Task Est Effort Task Actual Effort 01 Dec 2003 01 Dec 2003 Completed 01 Dec 2003 01 Dec 2003 15 hours 0 mins 16 hours 0 mins 15 hours 30 mins Est Duration 0 hours 10 mins 0 hours 4 mins Comment These two requirements are related Comment This bug affects the requirement Test Run Ability to create new book Author Owner Creation Date Test Coverage Task Progress Last Modified Release Planned Effort Task Effort Actual Effort URL 145 hours 0 mins 190 hours 188 hours 0 mins 40 mins 145 hours 0 mins 190 hours 188 hours 0 mins 40 mins Last Execution Date 04 Dec 2003 01 Dec 2003 Date 12 Mar 2004 Date 14 Mar 2004 04 Nov 2003 This report displays a complete work breakdown structure of the project from a requirements perspective in
63. 2004 02 Mar 2004 02 Mar 2004 02 Mar 2004 04 Mar 2004 04 Mar 2004 04 Mar 2004 Release Complete Plan Effort 1 0 0 0 1 0 0 0 0001 1 0 0 0 0001 1 0 0 0 0001 1 0 0 0 1 0 0 0 0001 1 0 0 0 0001 1 0 0 0 0001 1 0 0 0 145 hours 0 mins 145 hours 0 mins 90 hours 0 mins 15 hours 0 mins 15 hours 0 mins 14 hours 0 mins Est Effort 190 hours 0 mins 190 hours 0 mins 96 hours 0 mins 16 hours 0 mins amp hours 0 mins 5 hours 0 mins 3 hours 0 mins 16 hours 0 mins 8 hours 0 mins 5 hours 0 mins 3 hours 0 mins 16 hours 0 mins Actual Effort 188 hours 40 mins 188 hours 40 mins 95 hours 0 mins 15 hours 30 mins 7 hours 20 mins 5 hours 20 mins 2 hours 50 mins 16 hours 50 mins 7 hours 20 mins 6 hours 0 mins 3 hours 30 mins 15 hours 10 mins This report displays a matrix of the requirements in the system with their list of covering test cases and associated mapped requirements Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Requirements Forward Traceability This section displays a list of all the requirements with the associated test cases requirements Status In Progress In Progress Completed Completed Completed Completed Completed Completed Completed Completed In Progress In Progress Req Name Test Traceability Requirements Traceability RQ1 Functional System Requ
64. 4 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 4 Nov 2003 2 Nov 2003 4 Nov 2003 15 Nov 2003 15 Nov 2003 4 Nov 2003 Fred Bloggs IN000017 INO00004 IN000005 Joe P Smith IN000007 Joe P Smith IN000011 Joe P Smith IN000015 Fred Bloggs IN000016 Fred Bloggs IN000012 Fred Bloggs IN000008 INO00006 Joe P Smith INO00009 Joe P Smith IN000013 Fred Bloggs IN000014 Fred Bloggs IN000010 k lt Displaying page fi of 1 gt m Once you have chosen the destination project and clicked the lt Export gt button the incidents will be exported from the current project to the destination project Any file attachments will also be copied to the destination project along with the incidents 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 My Page Project Home Planning ee spiraTeam _ Incidents gt Incident Details Tasks Resources Role Manager lt lt Back to Incident List B sae BSaveandClose dhSaveandNew IN gt Find Workflow Operations Incident Name Cannot add a new book to the system INO000007 gt Resolve Incident Name Cannot add a new book to the system gt Unable to Reproduce gt Duplicate Incident Status gt Assigned Detected By Type Detected In Release 1
65. 7 screen to include delete button Not Started Joe P 01 Dec Smith 2003 07 Mar 08 Mar 2004 2004 5hours 0 01 Dec 2003 1 0 0 0 0002 RQ15 as 2 High 0 Joe P 01 Dec Smith 2003 07 Mar 08 Mar 3hours 0 2004 2004 2 High mins 01 Dec 2003 1 0 0 0 0002 RQ15 0 Not Started Fred 01 Dec 09 Mar 10 Mar 0 6hours 0 Bloggs 2003 01 Dec 2003 1 0 0 0 0003 RQ16 2004 2004 mins 2 High 11 4 2 Task Detailed Report This report displays all of the tasks tracked for the current project The task s details are displayed along with a tabular list of attached documents and the change history Task Detailed Report This report displays all of the tasks tracked for the current project The task s details are displayed along with a tabular list of attached documents and the change history Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Task 23 Write edition object insert queries Requirement ID RQ 12 Status Not Started Release 1 0 0 0 0003 Priority 1 Critical Assigned To Fred Bloggs Created On 01 Dec 2003 Start Date 11 Mar 2004 Last Modified 01 Dec 2003 End Date 12 Mar 2004 Estimated Effort 3 hours 0 mins Complete 0 Actual Effort 11 4 3 Task Summary Chart The task summary graph shows how many tasks are currently in a project The number of tasks is displayed according to
66. Bug Bug Bug Bug Bug sin T Open Open Assigned Resolved Closed Not Reproducible Resolved Assigned Open Assigned Closed Closed Resolved Fred E AN 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 Tracking Fred E E 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 Reporting 21 Nov 2003 20 Nov 2003 21 Nov 2003 Role Manager no IN000017 IN000004 IN000005 IN000007 IN000011 IN000015 IN000016 IN000012 IN000008 IN000006 IN000009 IN000013 IN000014 IN000010 i lt Displaying page fi of1 gt Show rows per page 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 Filter gt or press the lt ENTER gt key 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 There are also several aggregate filters that are used to filter on multiple values at once e g filtering status on All Open will return any incident that is in one of t
67. Change Request HH Enhancement Wj Incident HW Issue M Limitation Risk W Training Assigned Duplicate Not Reproducible In this version of the report the x axis represents the incidents status and the individual bars are grouped by the type of incident Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 3 4 Incident Progress Rate Graph The incident progress rate chart displays the total number of incidents created and closed over a particular date range The 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 progress rate report loaded with the past 60 days of incident discovery closure data depicted on a daily basis Welcome Fred Bloggs My Profile Log Out Library Information System spiraTest My Page Project Home Planning Testing Tracking Reporting Reporting gt Incidents Progress Rate Role Manager lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Tumaround Time Incident Type All Date Interval Daily Weekly Date Ending 9 23 2008 E m d yyyy Incidents Progress Rate Discovered Closed In this version of the report t
68. EPE Date Interval Daily Weekly Date Ending 10 19 2008 mid yyyy Incidents Open Count 1 Critical 2 High 3 Medium 4 Low 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 date interval Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 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 11 3 7 Incident Aging Graph 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 Welcome System Administrator My Profile Administration Log Out
69. Ending 10 19 2008 mids yyyy Incidents Progress Rate Discovered Closed 10 12 2003 10 17 2003 10 22 2003 10 27 2003 11 1 2003 1146 2003 11 11 2003 11 16 2003 11 21 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 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 you can display the past 12 months of cumulative incident count data organized on a weekly basis Welcome System Administrator My Profile Administration Log O a _ og Out L rary information System spiraTeam as My Page Project Home Planning Testing Reporting Reporting gt Incidents Cumulative Count Role Project Owner lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Tumaround Time incident Type Ai x Date Interval Daily O Weekly Date Ending 10719 2008 midi gt Finer L mid yyyy Incidents Cumulative Count Open Total geeecoece 900000 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 rep
70. Item Library Information Training 3 Dec 2003 x i i X Ability to edit existing book Library Information S Test Change Request Library Information Change Request 7 Dec 2003 gt Execute W Sample Risk 3 Library Information Risk 10 Dec 2003 W User expectations from old client app Library Information Training 3 Dec 2003 My Assigned Test Sets W Exporting data to excel Library Information Training 3 Dec 2003 Name Project Due Date Status Exploratory Testing 2 Library Information n a Deferred My Assigned Tasks gt Execute Name Project 3 Testing Lew Functongity 4 Library Information 10 Feb 2007 In Progress 7 Develop new edition entry scre Library Information Z Create edition object insert m Library Information Z Write edition object insert qu Library Information 7 Refactor author screen to incl Library Information 7 Create author object delete me Library Information Z Write author object delete que Library Information Z Develop edit subject details s Library Information W Cannot install system on Oracle 9i Library Information Bug 2 Nov 2003 My Assigned Test Cases Name Project Status Last Executed My Pending Test Runs Name Project Last Update Note that once you have successfully logged in and chosen a project SpiraTeam 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
71. Profle Log Out spiraTeam S Planning Tracking Reporting Requirements Releases gt Release Details Iterations Role Manager lt lt Back to Release List Esae pSaveandNew Delete y Refresh Print D Library System Release 1 Release Name Library System Release 1 RLO00001 a Library System Release 1 SP1 3 Library System Release 1 SP2 E iteration 001 Fot _iw B se m 4 ee G E iteration 002 This is the initial release of the Library Management System E iteration 003 B Library System Release 1 1 f Library System Release 2005 Created By Fred Bloggs v 15 Feb 2004 Version Number StarvEnd Date person days 216 hours 0 minutes Created On Active Yes v Available Effort 122 hours 0 minutes Resources Non Working Iteration Planned Effort Tasks Test Cases Custom Props Test Runs Attachments 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 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 hav
72. Project Home Planning Tracking Reporting Role Manager lt lt Back To Tests Z Testing New Functionality TX5 Person loses book and needs to report loss TC000012 i 2 Ability to create new author TC4 Tests that the user can create a new author record in the system C Z Ability to reassign book to di TC6 2 Person loses book and needs to TC12 Step 1 TC16 Step 1 Please follow the directions outlined in the box below C Step 2 TC17 User opens up browser and enters application URL http Awww libraryinformationsystem com beta C Step 3 C12 C Step 4 112 C Step 5 TC12 C Z Adding new book and author to TC13 pected Result Sample Data The browser loads the login web page http www libraryinformationsystem com beta Actual Result Please enter the actual test result if it differs then click the appropriate button e screen displays a 404 error message page Loggedinci onts Attachments 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
73. System Release 1 1 eo 27 Oct 2004 168 0h RL000004 o o o 7 1 2 Insert Hovering over the lt Insert gt button brings up a secondary menu that allows you to choose whether to insert a release or iteration if you just click Insert it defaults to inserting a release In either case it will insert the new release iteration above the currently selected item i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a release iteration 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 Clicking 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
74. YV Ru ay m T Ability to edit existing book 1 Dec 2003 1 0 0 0 TR000010 a Ability to create new author 1 Dec 2003 Testing Cycle 1 0 0 0 i 1 6 TROO0004 Z Ab ity to edit 1 Dec 2003 Testing Cycle 1 0 0 0 Passed 5 TRO00003 E ability to create new book 1 Dec 2003 1 0 0 0 a Opera Windows 2003 TR000012 a Ability to create new book 1 Dec 2003 Testing Cycle 1 0 Internet Explorer Windows XP TROO0001 Show 15 v rows per page 4 lt 4 Displaying page fi of 1 gt gt 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 You can also filter the results by choosing items from the filter options displayed in the sub header row of each field and clicking the Apply Filter link In addition you can quickly sort the list by clicking on one of the directional arrow icons displayed in the header row of the appropriate field 7 2 6 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 SpiraTeam will only display the icon
75. 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 Note you cannot indent a release or iteration if it is below an iteration as iterations are not allowed to have child items 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 6 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 you should click this button to make sure you are viewing the most current release list for the project 7 1 7 Edit Each release iteration in the list has an lt Edit gt button display in its right most column When you click this button or click on any of the cells in the row you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt bu
76. ality 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 1 2 Project Management As described in the Agile Manifesto traditional waterfall software methodologies and lifecycles have failed to delivery projects on time and on budget In addition many systems built this way will fail to provide the expected business value as there is no ability to quickly refine the requirements as the project progresses Consequently software development has been transformed with these new ideas and concepts with new methodologies such as Extreme Programming XP Scrum DSDM and AUP becoming common However the traditional tools of project management requirements specifications high level project plans GANTT c
77. ameters 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 generic 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 S password Copy To Clipboard Delete Add a new parameter to this test case amet ooo 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 displa
78. ar 3 rr 216 hours 0 elease the Library Bloggs 2004 9 Startin mins 1 Management Late 9 System 26 Not Started i 0 Tasks Libra peck feos ei System soap a ae 30 Mar 0 Running 176 hours 0 Release ug Smith _ 2004 Late mins small 1 SP1 security vulnerability 0 Starting Late 0 Not Started 11 5 2 Release Detailed Report This report displays all of the releases and iterations defined for the current project in the order they appear in the release iteration hierarchy The release s details are displayed along with sub tables containing the list of requirements added mapped test cases test runs executed incidents resolved attached documents scheduled tasks and the change history 1 1 0 0 Library System Release 1 1 This version adds additional reporting functionality to the 1 0 version 1 1 0 0 Fred Bloggs 15 Oct 2004 27 Oct 2004 Version Creator Start Date End Date Active Creation Date 15 Oct 2004 Planned Effort 168 hours 0 mins Available Effort 82 hours 0 mins Task Est Effort 86 hours 0 mins Actual Effort 85 hours 40 mins Resources 3 Non Working Days Notes Operating System Requirements Added Req Name RQ1 Functional System Requirements RQ2 Online Library Management System RQ3 Book Management RQ7 Ability to associate books with different subjects RQ8 Ability to associate books with diferent authors RQ9 Ability to associate books with different editi
79. ary Information W Cannot install system on Oracle 9i W Ability to associate multiple authors Cannot log into the application E Test System Limitation W Sample Risk 1 W Test Training Item E Test Change Request z Support for IBM DB2 H Test System Limitation W Sample Risk 2 E Test Training Item E Test Change Request E Sample Risk 3 Library Information Library Information Sample Application O Library Information Library Information Library Information Library Information Library Information Library Information Library Information Library Information Library Information Library Information Type Incident Incident Issue Bug Enhancement Incident Limitation Risk Training Change Request Enhancement Limitation Risk Training Change Request Risk Date Opene 1 Nov 2003 1 Nov 2003 1 Dec 2003 2 Nov 2003 17 Nov 2003 10 Dec 2003 4 Dec 2003 10 Dec 2003 3 Dec 2003 6 Dec 2003 17 Nov 2003 4 Dec 2003 10 Dec 2003 3 Dec 2003 7 Dec 2003 10 Dec 2003 Name Project Due Date Status Z Exploratory Testing 2 Library Information n a Deferred gt Execute ov My Assigned Tasks a Je n testing New Functionality a z Testing ee Functionality 4 Library Information 10 Feb 2007 In Progress hanes Project Progiess naa Ue Name Project Last Update Progress W User expectations from old client app Library Information Training 3 Dec 2003 W Exporting data to excel Library Information
80. ase 1 0 J Testing Cycle for Release 1 1 z Testing New Functionality Description 3 Exploratory Testing es les G G This tests the functionality introduced in release 1 0 of the library system Owner Creator Release 1 0 0 0 Library System Release 1 Created On 1 2 2007 12 00 00 AM Status Last Executed 12 1 2003 10 45 20 AM Planned Date Last Updated 10 13 2009 3 07 52 PM Test Runs Custom Props Attachments History 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 set detailed information itself and the bottom part of the right pane contains related information about the test set The navigation pane consists of a link that will take you back to the test set list as well as a list of the peer test sets 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 sets by clicking on the navigation links without having to first return to the test sets list page The top part of the right pane allows you to view and or edit the details of the particular test set You can edit the various fields name description etc and once you are satisfied with them simply click either the lt Save gt or lt Save and New gt button at the top of the page to commit the changes In addition you can delete the current artifact by choosing lt Delete gt discard any changes made
81. ave 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 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 any of the bars in the chart will take you to the requirements list page See section 4 1 with the corresponding filters set When you filter the project home by release iteration this widget will filter the requirements coverage graph to only include requirements that are specifically mapped to the selected release iteration This is useful when you want to determine the test coverage of new requirements that are being added to the specific release iteration If instead you want to determine the regression test coverage for a release you should add the separate Requirements Regression Coverage widget to the page instead 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 sorted by the requir
82. ay 2006 7A Graphical Design Mockups psd File 1 009 KB Joe P Smith 1 May 2006 URL to related information URL 0 KB Fred Bloggs 1 May 2006 Book Management Screen Wireframe ai File 392 KB Joe P Smith 2 Mar 2005 Upload New Document URL Type File URL The attachment list includes the filename URL 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 web page 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 choose File as the type and then 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 To attach a web link URL to the requirement you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document
83. bering 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 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 Par
84. bles containing the list of test steps test runs attached documents the change history and a list of any associated open incidents Test 2 Ability to create new book Tests that the user can create a new book in the system Status Failed Author Fred Bloggs Owner Fred Bloggs URL http www libraryreferences org Test Type Functional Test Priority Creation Date Last Execution 1 Critical 01 Dec 2003 04 Dec 2003 Step Description Call Login to Application User clicks link to create book User enters books name and author then clicks Next User chooses book s genre and sub genre from list User clicks submit button Test Runs Run Expected Result Sample Data Last Status Not Run Not Run Not Run Not Run Not Run User taken to first screen in wizard User taken to next screen in wizard User sees screen displaying all entered information Confirmation screen is displayed Macbeth William Shakespeare Play Tragedy Tester Release Version Est Duration Actual Duration Execution Date TR18 TR15 TR13 Fred Bloggs Joe P Smith Fred Bloggs Iteration 003 Iteration 002 iteration 001 1 1 0 0 0003 1 1 0 0 0002 1 1 0 0 0001 2 mins 2 mins 2 mins 70 mins 70 mins 70 mins 04 Dec 2003 03 Dec 2003 02 Dec 2003 TR12 TR2 TR1 Fred Bloggs Fred Bloggs Joe P Smith Library System Release 1 Library System Release 1 SP1 Library System Release 1 1 0 0 0 1 0 1 0 1 0 0 0 10 mins 10 mins 10 min
85. brary System Release 1 1 E 4 1 0 0 0001 Iteration 001 E 1 1 0 0 0002 Iteration 002 E 4 1 0 0 0003 Iteration 003 3 4 8 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 You can also configure in the settings whether to use Priority or Severity for the x axis 3 4 9 Test Execution Status This section consists of a bar graph that displays the aggregated count of test cases in each execution status for the project Note that this graph does not consider past test runs when calculating the totals in each status Passed Failed Not Run etc it simply looks at each test case and uses the
86. button to start adding test folders and 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 test execution bar 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 wasnt run the graph will display 50 green and 50 gray To determine the exact 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 sp
87. by clicking lt Refresh gt or print it by clicking lt Print gt The lower part of the right pane can be switched between five different views by clicking the appropriate tab Initially the pane will be in Test Cases mode but it can be switched to Test Runs Custom Properties 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 Set that allows you to execute all the tests in the set against the release specified in the test set 5 7 1 Test Cases In this mode the main pane displays the list of test cases contained within the test set You can add remove reposition and remove test cases from the list The execution status displayed next to each test case is the most recent execution status of the test case when run in the context of the current test set Custom Props Attachments History padd Remove 4 MoveUp vW MoveDown amp Refresh 2 Ability to create new book g T Critical 10 mins 1 Dec 2003 12 00 AM TC000002 Ability to edit existing book A Critical 5 mins 1 Dec 2003 12 00 AM TC000003 XJ Ability to create new author g M Critical 8 mins 1 Dec 2003 12 00 AM TC000004 Ability to edit existing author 2 High 5 mins 1 Dec 2003 12 00 AM Not Run TC000005 T Ability to reassign book to different author 2 High 8 mins 1 Dec 2003 12 00 AM Not Run TC000006 Z Book management 2 High 4 mins 1 D
88. chical arrangement of the various requirements and functionalities that need to be provided by the system in question The structure is very similar to the Work Breakdown Structure WBS developed in Microsoft Project and users of that software package will find this very familiar to use When you create a new project this list will initially be empty and you will have to start using the lt Insert gt button to start adding requirements Requirements come in two main flavors summary items shown in bold type and detail items shown in normal type with a hyperlink When you indent a requirement under an existing requirement the parent is changed from a detail item to a summary item and when you outdent a child item its parent will return to a detail item assuming it has no other children This behavior is important to understand as only detail items are assigned a status themselves the summary items simply display an aggregate of the worst case assessment of their children s status Also only detail items can be mapped against test cases for test coverage thus only they 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 graphical indicators that represent
89. cluding all requirements and tasks organized by schedule Requirements Plan Report This report displays a complete work breakdown structure of the project including all requirements and tasks organized by schedule Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library ID Name Status In Progress In Progress Type 1 Functional System Requirements Requirement 2 Online Library Management System Requirement 1 Book Management Requirement Completed Critical Ability to add new books to the system Requirement Completed 1 Critical Task Task Task Completed 1 Critical Completed 1 Critical Completed 1 Critical Develop new book entry screen Create book object insert method Write book object insert queries Ability to edit existing books in the system Requirement Completed 1 Critical Task Task Task Critical Critical Critical Develop edit book detais screen Create book object update method Write book object update queries Ability to delete existing books in the system Completed Completed Completed Requirement Completed 1 Critical 11 1 4 Requirements Traceability Matrix Priority Owner Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Start Date 01 Mar 2004 01 Mar 2004 01 Mar 2004 03 Mar 2004 03 Mar 2004 03 Mar
90. computer and then resume testing at a later date by locating the test run on your My Page under My Pending Test Runs and choosing to resume testing 5 5 Test Run Details As described in section 5 2 4 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 Ru 0 m 0 Ability to create new book 4 Dec 2003 1 1 0 0 0003 TROO0018 Ability to create new book 3 Dec 2003 11000002 Passed TR000015 a o o T Ability to create new book 2 Dec 2003 1 1 0 0 0001 Passed TROO0013 a Ability to create new book 1 Dec 2003 Testing Cycle 1 0 1 0 Passec Mozilla Firefox Windows 2000 TROO0002 for Release 1 1 Ability to create new book 1 Dec 2003 Failed Opera Windows 2003 TROO0012 a p Ability to create new book 1 Dec 2003 Testing Cycle internet Explorer Windows XP TR000001 for Release 1 0 Show 15 rows per page m lt Displaying page of 1 gt gt 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 Welcome Fred Bloggs My Profile Administration Log Out My Page Project Home Planning Testing Tracking Reporting e spiraTeam Test Cases gt Test Run Details Test Sets Role Manager Save Delete Refresh Print lt lt Back to Test
91. crete activities that each member of the development team would need to carry out for the requirement to be fulfilled Each task can be assigned to an individual user as well as associated with a particular release or iteration The system can then be used by the project manager to track the completion of the different tasks to determine if the project is on schedule 2 7 Projects and Users Spiraleam 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 7 Miscellaneous 2 7 1 Artifact Relationships The sections above have outlined the different features and functions a
92. cycle Management ALM system that manages your project s requirements releases test cases issues and tasks in one unified environment SpiraTeam contains all of the features provided by SpiraTest our highly acclaimed quality assurance system and SpiraPlan our agile enabled project management solution With integrated customizable dashboards of key project information SpiraTeam allows you to take control of your entire project lifecycle and synchronize the hitherto separate worlds of development and testing This user manual outlines the features and functionality available in SpiralTeam and demonstrates how to use the application for managing the quality assurance and project management processes on a typical project 1 1 Quality Assurance Quality Assurance is a key component of the Software Development Life Cycle SDLC which needs to be integrated into the planning and management of a program or project from its inception Too often though QA is implemented as Quality Control whereby testing that the required functionality works as expected is performed at the end when it is most costly to make corrections and changes To manage QA across a project from day one it is imperative that 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 function
93. d by the currently logged in user or those reports created by other members of the project that have been marked by that user as shareable gt The right hand main pane displays a list of the reports and graphs available in the system categorized by the artifact they primarily relate to requirements test cases incidents and releases Clicking on any of the report hyperlinks will take you to the configuration page for the report in question The configuration page for each report differs slightly but the general format is illustrated below Welcome Fred Bloggs My Profile Administration Log Out Help e spiraTeam My Page Project Home Planning Testing Tracking Reporting Reporting gt Requirements Detailed Report Role Manager lt lt Back to Reports Home lt lt Back to Reports Home Requirements Detailed Report gt Requirements Summary i i l 7 Please choose from the various options below to specify how you would like this report to appear gt Requirements Detailed You can filter the results displayed by various parameters as well as choose which elements of the report are displayed gt Requirements Plan Report Format gt Requirements Traceability Format HTML MS Word 2003 XML 2 Report Elements Requirements Details C Artifact Change History C Associated Tasks O Linked Incidents C Linked Requirements C List of Attached Documents C Test Case Coverage Requirements De
94. default set of values The task will be associated with the current requirement gt Remove removes the task from this requirement without actually deleting the task gt Delete deletes the task Itself 4 2 3 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 properties 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 Attachments History Please edit the following custom properties of this artifact and click Update when finished URL http www libraries org Difficulty Requirement Type Once you are satisfied with the values for the custom properties simply click Update to commit the changes 4 2 4 Attachments In this mode the main pane displays the list of documents or web links URLs that have been attached to the requirement The documents can be in any format though SpiraTeam will only display the icon for certain known types Test Coverage Tasks Custom Props History Associations W Book Management Functional Spec doc File 285 KB Fred Bloggs 2 M
95. dit existing author Regression Testing for Windows Visia 090 2003 Fred Bloggs TC000005 z Ability to reassign book to different author Testing New Functionality Dec 2003 Fred Bloggs TC000006 amp Regression Tests 2 L Dec 2003 Joe P Smith TC000007 1 Dec 2003 Joe P Smith TC000008 1 Dec 2003 Joe P Smith TC000009 1 Dec 2003 Fred Bloggs TC000015 Role Manager Displaying 7 out of 7 test case s for this release Functional Tests 5 2003 Testing Cycle for Release 1 0 Testing Cycle for Release 1 1 pec 2003 E Book management z Author management amp Common Tests 0 Gp Insert 3 Delete gt Indent lt p Outdent gt Execute Once you have chosen the destination release test set clicking lt Add gt will add the selected test cases to the destination release test set 5 1 14 Viewing the Test Status for a Release By default when you view the list of test case cases it will display an aggregate status for all releases of the project l 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 Fr
96. 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 7 5 History In this mode the main pane displays the list of changes that have been performed on the test set artifact since its creation 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 6 Incident Tracking This section outlines how the incident defect tracking features of SpiraTeam 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 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 sy
97. e 1 0 1 0 Type Incident Status New Opened By Assigned To Detected In Release 1 0 0 0 Resolved In Release 1 0 1 0 Notes Operating System Fred Bloggs Associations Artifact Type Test Run Incident Requirement File Attachments Filename Bug Stack Trace txt Error Logging in Screen shot gif Name Sample Test The book listing screen doesn t sort Ability to create new users in the system Description Created By Fred Bloggs Joe P Smith Joe P Smith Comment Test Run Sample Test This incident and bug are related Test Run Sample Test Captured screen shot of the error that was raised when attempting to log in to the library application Date 01 Nov 2006 16 Mar 2004 01 Dec 2003 Author Joe P Smith Fred Bloggs Artifact Id TRY IN 6 RQ 26 Date Uploaded 04 May 2006 24 Apr 2006 11 3 3 Incident Summary Graph The incident summary graph shows how many incidents are currently in a project The number of incidents is displayed according to the criteria that you specify You can specify the type of data displayed along the x axis and the incident information which is used to group the data When you first open the graph you will be asked to pick the field that you would like to display on the x axis and the field that you would like to group the data by Once you have chosen the appropriate fields and clicked the lt Select gt button the graph will be displayed Incidents Summary E Bug WW
98. e drop down list or enter a free text phrase depending on the type of field then click lt Filter gt or press the lt ENTER gt key 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 set numbers In the screen shot above we are filtering on test sets that contain at least one failed test case In addition if you have a set of filters that you plan on using on a regular basis you can choose the option Filter gt Save Filter to add the current filter to the list of saved filters that appear on your My Page The list of saved filters can also be retrieved by clicking Filter gt Retrieve Filter 5 6 10 Copying Test Sets To copy one or more test sets simply select the check boxes of the test sets you want to copy and then select the Edit gt Copy menu option This will copy the current test set selection to the clipboard Then you should select the place where you want the test sets to be inserted and choose the Edit gt Paste option The test sets will now be copied into the destination location you specified The name of the copied test sets will be prefixed with Copy of to distinguish them from the originals 5 6 11 Moving Test Sets To move test sets in the hierarchy there are two options 1 Click on the ic
99. e Planning Testing Requirements gt Requirement Details Releases Iterations Role Manager lt lt Back to Requirements List B Save op Save and New 3 Delete i B Refresh Print Book Management Requirement Ability to add new books to the system RQ 000004 ke 3 Ability to add new books to the system Name Ability to add new books to the system Ability to edit existing books in the sy Ability to delete existing books in the Ability to associate books with differen The ability to add new books into the system complete with ISBN publisher and other related information Ability to associate books with differen OQ Ability to associate books with differen jee Ability to completely erase all books st Description Importance Author Status Completed v Release Created On 12 1 2003 12 00 00 AM Owner Last Updated 12 1 2003 12 00 00 AM Planned Effort is hours fo minutes Tasks Attachments History Associstions 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 co
100. e 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 choose File as the type and then 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 incident To attach a web link URL to the incident you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link 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 perform
101. e new book z Ability to edit existing book 2 Ability to create new author amp Fred Bloggs Joe P Smith Joe P Smith amp Ability to edit existing author 2 Ability to reassign book to different author a amp Regression Tests 2 Joe P Smith amp Exception Scenario Tests 1 Joe P Smith z Person loses book and needs to report loss z Adding new book and author to library amp Common Tests 2 E Open Up Web Browser z Login to Application 1 Dec 2003 4 Dec 2003 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 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 Yes Yes Yes Yes Yes TC000001 TC000002 TC000003 TC000004 TC000005 TC000006 TC000007 TC000010 TC000011 TC000012 TC000013 TC000015 TC000016 TC000017 2oo0oo0o0o0o0R00 000004 rows per page 1 lt Displaying page i of 1 gt The test case list consists of a hierarchical arrangement of the various test folders and test cases that the system being developed needs to be able to demonstrate The structure is very similar to the folder structure in Microsoft Windows Explorer and users will find this very familiar and intuitive to use When you create a new project this list will initially be empty and you will have to use the lt Insert gt
102. e rationale for the association Add New Association Step 2 of 2 Please choose the incident that you want to add an association to wl Sample Risk 1 Sample Risk 2 Sample Risk 3 Test Change Request Test Change Request Test Change Request Test Change Request Test Change Request Test Change Request Add New Association Step 2 of 2 Please choose the requirement that you want to add an association to Enter Incident 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 in the system with one click Add from history Comment Comment Finally to delete an existing association except for those due to test runs select the check box next to its name and click the lt Delete gt icon This will only delete the association not the linked artifact itself 7 Release Management This section outlines how to use the Release Management features of SpiraTeam 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
103. e 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 the built in fields or any of the custom properties set up by the project owner 7 1 10 Copying Releases Iterations To copy a release iteration or set of releases iterations simply select the check boxes of the release iteration you want to copy and then select the Edit gt Copy menu option This will copy the current release iteration selection to the clipboard Then you should select the place where you want the releases iterations to be inserted and choose the Edit gt Paste option The releases iterations will now be copied into the destination location you specified The name of the copied releases iterations will be prefixed with Copy of to distinguish them from the originals Note that copied releases iterations will also include the test mapping information from the originals 7 1 11 Moving Releases Iterations To move a release iteration in the hierarchy there are two options 1 Click on the icon the release iteration you want to move and then drag the icon to the location you want it moved The border bet
104. e software system under development These incidents can be categorized into bugs enhancements issues training items limitations change requests and risks and each type has its own specific workflow and business rules Typically each incident is raised initially as a New item of type Incident Following the review by the project manager and customer they are changed to one of the other specific types given a priority critical high medium or low and status changed to Open Once it is assigned to a developer for fixing it is changed to status Assigned The developer now works to correct the incident after which time its status changes to Fixed or Not Reproducible depending on the actions taken or not taken Finally the project manager and customer verify that it has indeed been fixed and the status is changed to Closed SpiraTeam 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 6 Task Management As described above in addition to storing the requirements for a project SpiraTeam includes the capability of drilling each lowest level requirement down further into a series of work items called Tasks These tasks are the dis
105. e the same change to multiple rows e g to change the owner of five test cases from Fred Bloggs to Joe Smith you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the lt ESCAPE gt key will cancel the changes 5 1 7 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 8 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 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
106. ec 02 Dec Passed JUnit book Bloggs mins mins 2003 2003 Ability to edit existing TC3 1 1 0 0 0001 Fred Ohours 5 1 hours 10 02 Dec 02 Dec book Bloggs mins mins 2003 2003 Passed JUnit 11 2 7 Test Run Detailed Report This report displays all of the test runs defined for the current project in date order most recent first The test run s details and execution status are displayed along with sub tables containing the list of test run steps and a list of any associated open incidents Test Run 1 Ability to create new book Tests that the user can create a new book in the system Test Case TC2 Release 1 0 0 0 Status Failed Tester Joe P Smith Execution Date 01 Dec 2003 Type Manual Test Set Testing Cycle for Release 1 0 Est Duration 0 hours 10 mins Actual Duration 1 hours 15 mins Notes Web Browser Intemet Explorer Operating System Windows XP Step Description Expected Result Sample Data ActualResult Status 1 User logs in to application User taken to main menu screen Passed 2 User clicks link to create book se to first screen in Passed 3 User enters books name and author then clicks User taken to next screen in Macbeth William An error page is displayed No such object or with block variable at line i 473 Next wizard Shakespeare Failed Associated Incidents Inc Type Status Priority Severity Name Owned By Detected On 7 Bug Assigned 1 Critical 3 Medium Cannot add a new book to the system
107. ec 2003 Show fis Y rows per page dp inset 3 Delete gt indent lt Outdent gt Execute 5 1 10 Copying Test Cases Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Role Manager TC000001 TC000006 TC000007 TC000008 TC000009 TC000015 TC000016 To copy one or more test cases simply select the check boxes of the test cases you want to copy and then select the Edit gt Copy menu option This will copy the current test case selection to the clipboard Then you should select the place where you want the test cases to be inserted and choose the Edit gt Paste option The test cases will now be copied into the destination location you specified The name of the copied test cases will be prefixed with Copy of 5 1 11 Moving Test Cases To move test cases in the hierarchy there are two options to distinguish them from the originals 1 Click on the icon the test case folder you want to move and then drag the icon to the location you want it moved The background of the destination location will change as the icon is dragged over it to illustrate where it will be inserted Welcome System Administrator My Profile Administration Log Out Library Information System eee gt spiraTeam i Project Home Planning Testing Tracking Reporting Test Cases Test Sets Role Project Owner GP insert 3 Delete g gt indent lt p Outdent Show Level v Refresh Tools
108. ec 2003 12 00 AM Not Run TC000008 X Author management 2 High 4 mins 1 Dec 2003 12 00 AM Not Run TC000009 5 7 2 Test Runs This view displays the list of all the test runs executed against the test set 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 Custom Props Show hide columns vi A st Run Nami Execution Dat 5 te y Status 4 ur Act Dur Jeb Bro i erating System lu A wJ Ability to create new author 1 Dec 2003 Testing Cycle 1 0 0 0 TR000004 for Release 1 0 Ability to edit existing book 1 Dec 2003 Testing Cycle TROO0003 for Release 1 0 1 Dec 2003 Testing Cycle Internet Explorer Windows XP TROO0001 for Release 1 0 8 a Ability to create new book Show 15 rows per page 4 lt Displaying page of 1 gt p 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 colum
109. ecific user 5 1 1 Insert Hovering over the lt Insert gt button brings up a secondary menu that allows you to choose whether to insert a test case or a test folder if you just click Insert it defaults to inserting a test case In either case it will insert the new test folder test case above the currently selected item 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 item below it If you insert a new test folder 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 folder 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 Indent Outdent Clicking on the lt Indent gt button indents all the test folders test cases whose check boxes have been selected You cannot indent a test case or folder if it is below a test case as test cases are not allowed to have child items Clicking on the lt Outdent gt button de indents all the test folders test cases whose check boxes have been selected 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
110. ecord 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 To streamline the assignment and tracking of multiple test cases SpiraTeam allows users to select groups of test cases and arrange them into test sets Each test set can contain test cases from a variety of different folders and can be associated with a specific release of the system being tested 2 3 Release Planning Spiral eam provides the ability to track different versions releases of the application being tested Each 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 From a project planning perspective the releases are the major milestones in the project which are further sub divided into iterations which are separate mini projects with associated project scope and tasks The project s requirements are scheduled at a high level against the releases and the detailed tasks are scheduled against specific iteration within the release In addition all i
111. ect manager to determine how many critical vs low priority enhancements are waiting to be implemented vs actually being implemented In addition it makes a distinction between those requirements simply requested and those actually planned for implementation so the project manager can see what the backlog is between the customer s demands and the plan in place Clicking on the View Details link at the top of the table simply brings up the project requirements list See section 4 1 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 h
112. ed This is considered a Late Starting Task Task has started and is approximately 25 complete The scheduled end date is still in the future Task has started and is approximately 25 complete However the scheduled end date has elapsed already This is a considered a Late Finishing Task Task has been 100 completed Essentially the gray section of the bar indicates the of the task yet to be completed and the green red section of the bar indicates the of the task that has already been completed If the bar changes from green to red it means that the end date has been reached and the task is not yet complete and if the background changes from gray to yellow it means that the task has not yet started but the scheduled start date has passed 8 1 1 Sorting and Filtering You can easily filter and sort the list of tasks as illustrated in the screen shot below Welcome System Administrator My Profile Administration Log Out E spiraTeam My Page Project Home Planning i Tracking Incidents Tasks dp NewTask 3 Delete Refresh Qhcopy Epot Showhide columns v Y Fiter aa 1 4 out of 4 task s for this project Z Create edition object insert method In m Fred Bloggs 1 0 0 0 0003 TK000022 Z Develop new edition entry screen In Progress Fred Bloggs 1 0 0 0 0003 TK000021 Z Write author object delete query In Progress Fred Bloggs 1 0 0 0 0003 TK000029 Z Create author r object delete me
113. ed Bloggs My Profile Administration Log Out Project Home Planning Testing Tracking Reporting spiraTeam _ Test Cases Test Sets demet 3 Dote d gt intent lt gt Outset Sonis Y ahem heat fhos Sone coume Y Y Eier Ao v e ee Fred Bloggs TC000001 Fred Bloggs TC000002 Role Manager Displaying 7 out of 7 test case s for this release 1 Dec 2003 amp Functional Tests 5 Fred Bloggs _ z Ability to create new book Passed Fred Bloggs z Ability to edit existing book Not Run Fred Bloggs Ability to create new author Not Run Joe P Smith Fred Bloggs TC000004 1 Dec 2003 1 Dec 2003 ra Ability to edit existing author Blocked Joe P Smith z Ability to reassign book to different author Passed Joe P Smith amp Regression Tests 2 Es 4 Book management Author management Not Run Show fis rows per page 1 Dec 2003 OO ooo oa0gang y N og dp insert 3 Delete gt indent lt Outdent gt Execute Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith TC000005 TC000006 TC000007 TC000008 Eat Fred Bloggs TC000003 Peme TC000009 H lt Displaying page 1 ja ofie 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 relea
114. ed as a tooltip 4 1 1 Insert Clicking on the lt Insert gt button inserts a requirement above the currently selected requirement i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a requirement below a summary item you 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 chi
115. ed on the incident artifact since its creation An example incident change history is depicted below General Custom Properties Attachments Associations 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 6 2 7 Associations In this mode the main pane displays a list of any requirements test runs test steps or other incidents that are associated with this incident Custom Props Attachments qpAdd 3 Delete Ability to associate books with different editions 19 Mar 2004 19 Mar 2004 17 Mar 2004 1 Dec 2003 1 Dec 2003 Ability to create new book Step 2 2 The book listing screen doesn t sort 7 Ability to create new book Ability to add new books to the system History Joe P Smith Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs This incident is related to the test step Test Run Ability to create new book Test Run Ability to create new book Requirement Test Step Incident Test Run Requirement RQ000009 TS000002 INO00006 TROO0001 RQ000004 i The incidents in this list are ones that a user has decided are relevant to the curr
116. efined 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 Web Browser Testing with IE v5 5 5P1 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 and web browser 5 5 6 Attachments In this mode the lower section of the screen displays the list of documents that have been attached to the test run The documents can be in any format though SpiraTeam will only display the icon for certain known types Test Run Steps Stack Trace Custom Properties i Document Name Type Size UploadedBy Upload ate Y Gb Error Logging in Screen shot_gif File 48 KB Fred Bloggs 24 Apr 2006 Delete Attach New Document URL Type File URL Filename 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 pos
117. eful 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 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 6 1 6 Edit Each incident in the list has an lt Edit gt button display in its right most column When you click this button or just click on any of the cells in the row 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 Welcome System Administrator My Profile Administration Log Out My Page Project Home Planning Tracking a spiraTeam E Incidents Tasks Role Project Owner Pp New incident Delete Refresh h Copy Exot Show hide columns v Y Filter Displaying 1 14 out of 14 incident s for this project Of foe d ee d e a a eae Fred Bloggs 15 Nov 2003 Fred Blogg
118. elease of the system and that the test runs are mapped to the appropriate custom properties e g operating system platform browser etc 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 If the test run was launched from a test set the release and list custom properties will be pre populated from the test set itself and will not be changeable on this screen Once you have chosen the appropriate release name and or custom properties click the lt Next gt button to begin executing test steps Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing a gt spiraTeam S Test Cases gt Test Case Execution Test Sets Role Manager lt lt Back To Tests Z gt Testing New Functionality TX5 Ability to create new author TC000004 C 4 Ability to create new author TC4 Tests that the user can create a new author record in the system T Step 1 TC16 C Step 2 TC17 Step 3 TC4 Step 1 Please follow the directions outlined in the box below a User opens up browser and enters application URL http wwew libraryinformationsystem com beta M Step 6 TC4 C Z Ability to reassign book to di TC6 C Person loses book and needs to TC12 Expected Result Sample Data C Z Adding new book and author to ___ TC 13 The browser l
119. em The effort is shown for tasks and incidents as well as a total of the two together You can display the workload for the project as a whole for a specific release including all child iterations or for a specific iteration If any project resources have been assigned more work that they have time to complete during the length of the release iteration the background color of the effort value will be colored in red indicating that you need to offload some of the work to other project resources 10 Document Management This section outlines the document management features of SpiraPlan and SpiraTeam that can be used to upload manage and share documents between the different members of the project This module includes support for uploading files and URLs versioning of documents the ability to organize into folders and categorize and search using meta tags In addition the document management features are fully integrated into the rest of the system so that documents attached to other artifacts e g requirements test cases etc are automatically connected to the project documentation repository 10 1 Document List When you click on the Project Home gt Documents link on the global navigation bar you will initially be taken to the project documents list screen illustrated below Welcome Fred Bloggs My Profile Log Out Project Home i Testing Tracking Reporting Project Home Documents Role Manager Document Folde
120. em Fred Bloggs These two requirements are related Requirement RQ000006 4 Nov 2003 Cannot add a new book to the system Joe P Smith Test Run Ability to create new book Incident INO00007 The requirements in this list are ones that a user has decided are relevant to the current one and has created a direct link between them In the case of incidents the association can be either due to the creator of an incident directly linking the incident to the requirement or it can be the result of a tester executing a test run and creating an incident during the test run In this latter case the check box to the left of the association will be unavailable as the link is not editable Each association is displayed with the type of artifact requirement vs incident name of the artifact being linked to the name of the person who created the association and a comment that describes why the association was made In the case of an indirect association due to a test run the comment will contain the name of the test run To create a new association simply click the lt Add gt icon and then choose the type of artifact you want to create an association to Add New Association Step 1 of 2 Please choose the artifact that you want to add an association to Requirement Incident Once you have selected the appropriate artifact type you will then be able to choose the specific artifact you want to link to In the case of requirements you choose
121. ements that have the most open incidents first 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 You can configure in the settings whether to include requirements with no open incidents and also how many rows of data to display 3 4 5 Top Open Issues This section displays a breakdown of the top 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 You can configure in the settings whether to use Priority or Severity for the display and also how many rows of data to display 3 4 6 Top Open Risks This section displays a breakdown of the top risks logged against the project in order of decreasing priority Note that items not given a priority are listed at the top since critical risks could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the risk item hyperlink will take you to the
122. ent from the list provided and supply any meta tags that you want to search on separated by commas Then click lt Upload gt to complete the operation or lt Cancel gt to abort 10 1 2 View Document Information When you hover the mouse pointer over any of the documents displayed in the document list an information panel will be displayed that contains the name description version document type and meta tags of the document Welcome Fred Bloggs My Profile Log Out Project Home Testing Tracking Reporting Project Home Documents Role Manager ieia a oc S spiraTfeam S amp Design Documents Misc Documents Screen Captures Specifications Filename Test Results Document Type a4 File Type Sequence Diagram for Book Mat pdf UML Diagram Acrobat D 10 May 2006 1 May 2006 23 Apr 2006 2 Apr 2006 1 Apr 2006 Fred Bloggs DC000007 Joe P Smith Fred Bloggs Joe P Smith Joe P Smith DC000013 DC000012 DC000008 DC000011 id lt Displaying page h of 1 gt Pm Operations Description Sequence diagram in UML format that provides additional detail surrounding the book managament dP Add Document use case test case 3 Delete Document Version 1 2 amp Refresh Documents Tags sequence diagram book management Created By Fred Bloggs 5 3 2006 12 00 00 AM Edited By Joe P Smith 5 10 2006 12 00 00 AM Document ID DC000007 Y Apply Curent Filter x Clear All Filte
123. ent one and has created a direct link between them In the case of requirements and test cases the association can be either due to the creator of an incident directly linking the incident to the requirement or test step or it can be the result of a tester executing a test run and creating an incident during the test run In this latter case the check box to the left of the association will be unavailable as the link is not editable Each association is displayed with the type of artifact requirement test step test run incident the name of the artifact being linked to the name of the person who created the association and a comment that describes why the association was made In the case of an indirect association due to a test run the comment will contain the name of the test run To create a new association simply click the lt Add gt icon and then choose the type of artifact you want to create an association to Add New Association Step 1 of 2 Please choose the artifact that you want to add an association to Requirement Incident Once you have selected the appropriate artifact type you will then be able to choose the specific artifact you want to link to In the case of requirements you choose the item from a hierarchical list box and in the case of incidents you can either enter the incident ID or choose from a list of incidents you have recently submitted In either case you can also add a comment that explains th
124. ents Show 15 rows per page 1 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 Tasks In this mode the lower part of the right pane displays the list of project tasks that need to be completed for the release iteration to be completed Incidents Test Cases Custom Props Test Runs Attachments History cp NewTask 3 Remove Delete Refresh Est Effort 32 0h Actual Effort 31 2h 2 Refactor book screen to include delete button X Create book object delete method W Write book object delete query w Develop edit author details screen Create author object update method Completed Completed Completed Not Started Not Started 1 0 0 0 0002 1 0 0 0 0002 1 0 0 0 0002 1 0 0 0 0002 1 0 0 0 0002 Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith TKO000007 TKO000008 TKO000009 TK000024 TK000025 TK000026 2 Write author object update queries Not Started 1 0 0 0 0002 Each of the tasks is displayed together with its name description by hovering the mouse over the name progress indicator priority current owner estimated effort actual effort and numeric task identifier Clicking on the task name will bring up the Task Details page which is described in more detail in section 8 2 This allows you to edit the details of an existing task You can perform the foll
125. ep and an existing incident simply click the lt Add gt icon and then choose the incident you want to link to this test step Add New Association Step 2 of 2 Please choose the incident that you want to add an association to Enter Incident IN Add from history Sample Risk 1 sample Risk 2 sample Risk 3 Test Change Request Test Change Request Test Change Request Test Change Request Test Change Request Test Change Request Finally to delete an existing incident association except for those due to test runs select the check box next to its name and click the lt Delete gt icon This will only delete the association not the linked incident itself 5 3 2 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for test steps 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 step These can be either freetext or drop down lists Incidents Attachments History Please edit the following custom properties of this artifact and click Update when finished Step Type Step Type 1 bd Once you are satisfied with the values for the custom properties simply click Update to commit the changes 5 3 3 Attachments In this mode
126. equirement can be fulfilled The tasks are listed in ascending date order so that the items with the oldest due dates are displayed first In addition each task is displayed with a progress indicator that graphically illustrates its completion against schedule See section 8 task management for details of the different progress indicators Clicking on the task name hyperlink will take you to the task details page This page will describe the task in more detail illustrate which requirement and release it is associated with and also allow you to view the change log of actions that have been performed on it 3 2 8 My Assigned Incidents This section lists all the open incidents you are the owner of across all the different projects you are a member of This typically means that the project manager has assigned you to be responsible for resolving the incident In the case of a bug this can mean actually fixing the problem whereas for other incident types e g training item it may mean simply documenting a workaround In either event this section highlights the open incidents you need to manage ranked by importance priority and categorized by type with the open date displayed to give you a sense of the age of the incident Clicking on the incident name hyperlink takes you to the incident details page See section 6 2 that describes the incident in more detail and allows you to add new information or change its status to indicate action
127. er optionally enter a detailed description then click the lt Upload gt button The document will be copied from your computer and attached to the test case To attach a web link URL to the test case you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link 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 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 Req Coverage Custom Props Test Runs 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 Test Step Details When you click on one of the hyperlinks next to a test step in the test
128. er page l lt Displaying page 1 of 1 gt amp 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 You can also filter the results by choosing items from the filter options displayed in the sub header row of each field and clicking the Apply Filter link In addition you can quickly sort the list by clicking on one of the directional arrow icons displayed in the header row of the appropriate field 5 2 5 Release Mapping This view 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 History Available Releases Mapped Releases E RL000001 1 0 0 0 Library System Relea Active RL000002 101 0 Library System Relea Active 1 0 2 0 Library System Relea RL000003 1 0 20 Library System Relea Active O E 1 0 0 0 0001 Iteration 001 RL000004 1 1 0 0 Library System Relea Active 1 E 1 0 0 0 0002 Iteration 002 ae RL000017 1 1 0 0 0001 Iteration 001 Active 1 E 1 0 0 0 0003 Iteration 003 a RL
129. ered for the current project in a filterable sortable grid The grid displays the task number together with fields such as priority name assigned owner start date end date scheduled release etc The choice of columns displayed is configurable per user per project giving extensive flexibility when it comes to viewing and searching tasks In addition you can view a more detailed description of the task by positioning the mouse pointer over the task name hyperlink and waiting for the popup tooltip to appear If you click on the task name hyperlink you will be taken to the task details page described in section 8 2 Clicking on any of the pagination links at the bottom of the page will advance you to the next set of tasks 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 One special column that is unique to tasks is the progress indicator This illustrates graphically both the percentage completion of the task and also if the task is either starting late or finishing late The following table illustrates the different type of status that can be conveyed by the indicator Indicator Display Progress Description Task has not yet started but the scheduled start date is still in the future Task has not yet started and the start date has elaps
130. escribed 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 Releases Attachments History cp insertStep op insertLink Delete 4 MoveUp Wy Move Down Refresh E Parameters Step 1 E S Call Login to Application TC 17 N A N A B Z uU e oA B Z uU e oA B Z uU e oA T5000002 User clicks link to create book User taken to first screen in wizard Step 3 C B Z uU e mom BiUR e gom B Z uU e gom TS000003 WW User enters books name and User taken to next screen in wizard Macbeth William Shakespeare uthor then clicks Next Step 4 C BirURlegom BirURlegom BirURlegom TS000004 User chooses book s genre and User sees screen displaying all Play Tragedy sub genre from list ntered information Step5 E BlU kl egom BlU Rl egom B Z uU e oA T5000005 User clicks submit button onfirmation screen is displayed Note Test steps that are marked with a hyperlink a
131. eted In Progress Requested In this version of the report the x axis represents the requirements status and the individual bars are grouped by requirement importance Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph gt Hide Data Grid 1 Critical 3 Medium Completed In Progress Planned Requested This feature is available on all the various graphs in the system 11 1 6 Requirements Coverage Graph The requirements coverage graph shows how many requirements are currently in a project according to their test coverage status Requirements Coverage E Critical 2 High D 3 Medium O 4 Low Caution Not Run Not Covered The x axis of the report represents the various test execution statuses that a requirement can have as its coverage status plus the Not Covered status and the individual bars are grouped by the requirements importance Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 2 Test Case Reports 11 2 1 Test Case Summary Report This report displays all of the test cases defined for the cur
132. first one 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 This tab also displays any pre existing incidents that were associated with the test step being viewed gt The second tab displays a list of attachments that are related to the current test case and or test step This list initially contains any documents that have been attached to either the test case in general or the test step in particular However as you perform the testing you can attach additional documents to this list that are relevant to the test results e g screenshots of an error page these attached documents will be associated with both the test run itself and any incidents that are created 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 or if all the steps have passed you can click lt Pass All gt to pass all the steps at once This is illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing Test Cases gt Test Case Execution Test Sets lt lt Back To Tests Pass Passy Biockea Caution
133. for certain known types Incidents Tasks Test Cases Custom Props Test Runs History Related Information System Administrator 19 Oct 2008 Upload New Document URL Type File URL Filename Browse 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 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 choose File as the type and then 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 To attach a web link URL to the release you need to choose URL as the type and then enter the fully qualified URL e g hitp mywebsite com Document 1 an optional description and then click the lt Upload gt button to attac
134. g out Copyright C 2006 2008 Inflectra Corporation inflectra You have two choices you can either click the Log Out link and try logging in as a different user or if you want to log off any other active sessions e g you closed the browser and the session is still listed as active simply click the Sign Off The Other Locations link and you will be logged in to the application Since SpiralTeam 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 ee spiraTteam we Change License Details Return to Login page Version v2 0 1 Copyright C 2006 2008 Inflectra Corporation inflectra This means that one of the other users who is already logged in needs to click the Log Out button so that one of the concurrent licenses is freed for your use If the user has logged out by closing the browser 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
135. ggs My Profile Administration Log Out spiraTteam Project Home Planning Requirements Releases Iterations Role Manager Displaying the iteration plan for the selected release To move items use drag and drop Iteration 1 0 0 0 0002 3 5 2004 3 8 2004 Planned Estimated 24 0h 32 0h lt a iteration 1 0 0 0 0001 3 1 2004 3 4 2004 Planned Estimated Available 96 0h 64 0h 7 Create book object delete method lt Write book object delete query C 4 Develop edit author details screen C 4 Create author object update method O 4 Write author object update queries Z Refactor author details page to include contact in a Update author select query to include contact info a Update author update insert queries to include con Z Make sure that testing environment ready Show rows per page Any y Not Started Not Started Not Started Not Started e 0 o o o This screen is divided into two sections lt Refactor book screen to include delete button Selected Release L000 Lenn srienasmse T Iteration 1 0 0 0 0003 3 9 2004 3 12 2004 Planned Estimated 72 0h 30 0h 8 01 C Z Refactor author screen to include delete button 0h Create author object delete method 3 0h White author object delete query 8 0h 7 Develop new edition entry screer 5 0h lt Cre athoc C Z Write edition object insert queries Available 42 0h ate edition object insert method Ary TK000030
136. gs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Role Project Owner RQ000004 FP Edit RQ000005 gt Edit RQ000006 gt Edit RQ000007 PEt RQ000008 PEt RQ000009 F Egk RQ000010 P Edit RQ000011 gt Edit RQ000013 gt Edit RQ000019 gt Edit RQ000022 Edit 1 lt Displaying pagefji of1 gt gt Once you have the requirement positioned at the correct place that you want it inserted just release the mouse button and the requirement list will be refreshed with the requirement moved to the desired location Alternatively you can simply select the check boxes of the requirements you want to move and then select the Edit gt Cut menu option This will cut the current requirements selection to the clipboard Then you should select the place where you want the requirements to be inserted and choose the Edit gt Paste option The requirements will now be moved into the destination location you specified To export a requirement or set of requirements from the current project to another project in the system all you need to do is select the check boxes of the requirement s you want to export and then click the lt Export gt button This will then bring up a list of possible destination projects Welcome Fred Bloggs My Profile Log Out Planning Tracking Reporting spiraTest Requirements Releases Role Manager T indent Retesh Copy G Epot Showhidecoimns gt Y Gear Fimer
137. gs Smith 2007 07 Feb 2007 13 Oct 2009 01 Dec 2003 3 2 0 of the library system 11 2 4 Test Set Detailed Report This report displays all of the test sets defined for the current project in the order they appear in the test set list The test set s details and execution status are displayed along with sub tables containing the list of test cases test runs attached documents and the change history Test Set 1 Testing Cycle for Release 1 0 This tests the functionality introduced in release 1 0 of the library system Owner Joe P Smith Creator Fred Bloggs Release 1 0 0 0 Creation Date 02 Jan 2007 Status In Progress Last Execution 01 Dec 2003 Planned Date 05 Feb 2007 Last Updated 13 Oct 2009 Notes Operating System Name Priority Status Last Execution Date Ability to create new book 1 Critical Failed 01 Dec 2003 Ability to edit existing book Critical Passed 01 Dec 2003 Ability to create new author Critical Failed 01 Dec 2003 Ability to edit existing author High Not Run Ability to reassign book to different author High Not Run Book management High Not Run Author management High Not Run Tester Release Status Est Duration Actual Duration Execution Date Joe P Smith Library System Release 1 Failed 8 mins 90 mins 01 Dec 2003 Fred Bloggs Library System Release 1 Passed 5 mins 90 mins 01 Dec 2003 Joe P Smith Library System Release 1 Failed 10 mins 75 mins 01 Dec 2003 11 2 5 Printable Test Scripts T
138. gt discard any changes made by clicking lt Refresh gt or print it by clicking lt Print gt The lower part of the right pane can be in one of four possible modes that can be selected Schedule Custom Properties Attachments and History Each of the different views is described separately below 8 2 1 Schedule In this mode the main pane displays the general schedule and completion status of the specific task You can enter edit the start date end date i e the due date estimated and actual effort and the completion status percentage Custom Properties Attachments History Status Estimated Effort hours minutes Complete Actual Effort hours minutes Note that if this task is currently assigned to a release or iteration the start date and end date of the task must lie within the date range of the parent release iteration If your task looks like it will not be completed in the available timeframe you will need to contact the project manager to get them to either extend the date range of the task or consider moving the task to the next iteration 8 2 2 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for tasks 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
139. h 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 eS Welcome Fred Bloggs My Profile Administration Log Out Ubrary Infomation System v Help spiraTeam lt My Page Project Home Planning Testing Tracking Reporting Reporting Role Manager gt v1 0 Release List Report Requirement Reports Test Case Reports Incident Reports Task Reports Release Reports EEE gt Requirements Summary gt Test Case Summary gt Incident Summary gt Task Summary gt Release Summary gt Requirements Detailed gt Test Case Detailed gt Incident Detailed gt Task Detailed gt Release Detailed gt Requirements Plan gt Test Set Summary gt Release Plan gt Requirements Traceability gt Test Set Detailed gt Printable Test Scripts gt Test Run Summary gt Test Run Detailed Requirements Graphs Test Case Graphs Incident Graphs Task Graphs gt Requirements Summary gt Test Case Summary gt Incident Summary gt Task Summary gt Requirements Coverage gt Test Run Summary gt Incident Progress Rate gt Task Velocity gt Test Run Progress Rate gt Incident Cumulative Count gt Task Bumup gt Incident Open Count gt Task Burndown gt Incident Agin gt Incident Turnaround Time This page consists of two main areas gt The left hand pane displays a list of any reports that have either been save
140. h the web link 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 7 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 Test Runs Custom Properties 5 2 2006 12 00 00 AM 3 4 2005 12 00 00 AM Library System v1 0 0 1 0 0 Library System Release 1 1 0 0 0 Fred Bloggs Version Number 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 3 Iteration Planning As well as being able to assign tasks and incidents to releases and iterations individually through the Release Iteration details page see above when you are first assigning tasks and incidents to the iterations in the release it is usually more convenient to use the Iteration Planning screen instead To access this screen go to Planning gt Iterations choose the current release and the following screen will be displayed A m Welcome Fred Blo
141. harts white board schedules and top down task management are too cumbersome and not well suited Spiraleam provides a complete Agile Project Management System in one package that can manages your project s requirements releases iterations tasks and issues in one environment fully synchronized 2 Functionality Overview This section outlines the functionality provided by SpiraTeam in the areas of requirements management test case management release planning iteration planning incident tracking task management and project user management 2 1 Requirements Management Spiraleam 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 At the same time from a development perspective the team begins initial estimation of the lowest level requirements in the requiremen
142. he 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 Administration Log Out Help spiraTeam My Page Project Home Planning Testing Tracking Reporting Project Group Home ProjectHome Documents Role Manager Library Information System PR000001 Modify Layout Settings Add Items Display data for Al Rekases Y Project Overview Top Open Issues View All Sample application that allows users to manage books authors and lending records for a typical branch Description Priority Owned By Date Opened libra _ rrr rev _OON LL i Cannot install system on Windows ME 1 Dec 2003 Group Internal Projects Web Site www libraryinformationsystem org Ability to be accessed by Mozilla Joe P Smith 1 Dec 2003 Owner s System Administrator Management of children s loans Joe P Smith 1 Dec 2003 System may require process changes 1 Dec 2003 Requirements Summary View Details Status 1 Critical 2 High 3 Medium 4 Low None TOTAL Top Open Risks view All Requested i 3 1 5 Sad 0 Description Priority Owned By Date Opened Rejected 0 Sample Risk 1 10 Dec 2003 Accepted 0 Sample Risk 2 10 Dec 2003 Planned 1 2 3 Sample Risk 3 Fred Bloggs 10 Dec 2003 In Progress 1 1 2 Completed 7 1 8 T E lon S TOTAL g 4 5 1 18 est Execution Status View Details 3 Total Runs 19 j Daily R
143. he 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 Bo Custom Properties NUnit Assert Count 1 Expected 1 but 2 was found Test Name _01_TestCreateBook Runner Name Message 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 _ MonthCheck MonthCount amp gt MonthCount amp lt option gt amp vbCrLf Line 216 Else Line 217 Response Write lt option value _ MonthCheck MonthCount amp gt amp MonthCount amp lt option gt amp vbCrLf Line 218 End If Line 219 Details on how to use SpiralTeam in conjunction with an automated testing tool are provided in the SpiraTeam Automated Testing Integration Guide which can be downloaded from the Inflectra website 5 5 5 Custom Properties In this mode the tab displays any custom properties that the project owner has d
144. he open statuses new open assigned reopen To change the column that is sorted or to change the direction of the current sort simply click on the up down arrow icon in the appropriate column The currently sorted column is indicated by the larger white arrow with the back border In the screen shot above we are filtering on type bug and sorting by decreasing priority Clicking on Filter gt Clear Filter removes any set filters and expands the incident list to display all incidents for the current project and clicking on Filter gt Save Filter allows you to save the filter to your My Page for use in the future The list of saved filters can also be retrieved by clicking Filter gt Retrieve Filter 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 us
145. he 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 Similarly by clicking on the weekly radio button you can display the past 12 months of incident discovery data organized on a weekly basis SpiraTest Welcome Fred Bloggs My Profile Log Out Library information System Help My Page Project Home Planning Testing Tracking Reporting Reporting gt Incidents Progress Rate Role Manager lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Tumaround Time Incident Type All Date Interval Daily Weekly Date Ending 9 23 2008 midlyyyy Incidents Progress 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
146. his 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 Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Test 2 Ability to create new book Tests that the user can create a new book in the system Test Steps Step Description Expected Result Sample Data Status Actual Result User opens up browser and enters application URL The browser loads the login Cl Passed C Failed http www libraryinformationsystem com beta web page http www Roraryintormationsystem comibeta Cl Blocked C Caution User taken to main menu Login ibrarian Paseword pasewond Cl Passed C Failed screen i Cl Blocked C Caution User taken to first screen in Cl Passed C Failed wizard El Blocked C Caution User taken to next screen in 7 LiPassed C Failed Macbeth Wiliam Shakespeare wizard me E Biocked C Caution User sees screen displaying 5 Traged C Passed C Failed all entered information ay a Cl Blocked C Caution Confirmation screen is Cl Passed C Failed displayed Cl Blocked C
147. idents 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 Associations Please edit the following custom properties of this artifact and click Update when finished Notes May be an array bounds issue Operating System Windows XP m 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 SpiraTeam will only display the icon for certain known types Resolution Schedule Custom Props History Associations W Error Stacktrace doc File 24 KB Fred Bloggs 11 May 2006 Web Page capture htm File oo KB Fred Bloggs 25 Apr 2006 Upload New Document URL Type File URL 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 th
148. ific task progress for that project using the same coloring convention as the main graph That way you can see both the aggregate task progress and also the relative progress for each project You can configure in the widget settings whether you want to see the aggregate bar graph and or the project specific task progress 3 5 5 Test Execution Status This section consists of a bar graph that displays the aggregated count of test cases by execution status for the entire project group The Passed Failed Blocked Caution and Not Run bars indicate the total count of test cases that are in that category for all the projects in the group Under the main bar graph is displayed a table containing each project in the group and a colored bar illustrating the specific test case execution status for that project using the same coloring convention as the main graph That way you can see both the aggregate test status and also the relative status for each project You can configure in the widget settings whether you want to see the aggregate bar graph and or the project specific test status 3 5 6 Incident Aging This section displays the number of days incidents have been left open in the system The chart is organized as a histogram with the count of incidents on the y axis for all projects in the group and different age intervals on the x axis Under the main bar graph is displayed a table containing each project in the group and a colored bar i
149. ified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link 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 3 4 History In this mode the main pane displays the list of changes that have been performed on the test step artifact since its creation An example test step change history is depicted below Incidents Custom Properties Attachments 2 May 2006 12 00 AM Expected Result User taken to first screen User taken to next screen in wizard Fred Bloggs 4 Mar 2005 12 00 AM Expected Result User taken to first screen 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 4 Execute Test Case s This section describes how a tester can follow the steps defined for a series of test cases and record what actually happened in the process In addition recorded failures of test cases can be used to automatically generate new incidents that will be added to the incident tracking module
150. ill 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 Releases Attachments History Choose the test 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 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 login 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 num
151. ill now appear in your home page in bold type with a yellow background see above screen shot To change the currently selected project simply click on the link of another project name 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 If you are a project group member the name of the project group will also be displayed as a hyperlink In which case clicking on the project group hyperlink will take you to the Project Group dashboard see section 3 5 3 2 2 My Saved Searches This section lists any filters searches you have saved from the various artifact list screens throughout the application This allows you to store specific combinations of searches that you need to perform on a regular basis e g display all newly logged incidents display all requirements that are completed but have no test coverage The name of the saved search is displayed along with an icon that depicts which artifact it s for and the project it refers to Clicking on the name of the saved search will take you to the appropriate screen in the project and set the search parameters accordingly Clicking the Delete link next to the saved search will delete it 3 2 3 My Assigned Requirements This section lists all the requirements you have been made owner of across all the different projects you are a member of This typically means that
152. in fields or any of the custom properties set up by the project owner 5 1 9 Filtering You can easily filter the list of test cases as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing Tracking spiraTeam i Test Cases Test Sets dp insert 3 Delete g gt indent lt Outdent ShowLevel v Refresh hedt Tools Show hide columns Y Fiter Display data for All Releases v Displaying 7 out of 7 test case s for this release gE SEE cee amp Functional Tests 5 Bloggs 1 Dec 2003 4 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 2 Ability to create new book amp Regression Tests 2 z Book management 4 Author management amp Scenario Tests 2 amp Exception Scenario Tests 1 z Person loses book and needs to report loss z Adding new book and author to library amp Common Tests 2 Joe P Smith Joe P Smith 1 Dec 2003 1 Dec 2003 1 Dec 2003 z Open Up Web Browser z Login to Application rows per page gp insert Delete gt indent lt p Outdent i g 00000000 000g Last Executed Reporting Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Yes Yes Yes Yes Yes TC000002 TC000007 TC000008 TC000009 TC000010 TC000011 TC000012 TC000013 TC000015 TC000016
153. in the requirements hierarchy there are two options a 4 spiraTeam 1 Click on the icon the requirement you want to move and then drag the icon to the location you want it moved The border between the destination requirements will change as the icon is dragged over it to illustrate where it will be inserted Requirements Releases Iterations Gp inset 3 Delete lt gt indent lt p Outdent Show Level v Refresh hCopy K Export 00000000000000 rm z 4 1 12 Exporting Requirements ja Ability to add new books to the system Q Ability t it existin ks in the 5 Ability to delete existing books in the system Ability to associate books with diferent subjects Bi cL Ability to associate books with different authors he a a J Edition Management T Author Management Subject Management Administration Functions os per page 2 o 2 Project Home Not Covered Not Covered Not Covered Not Covered Not Covered Not Covered Planning Welcome System Administrator My Profile Administration Log Out Lirary information System Reporting In Progress In Progress Completed Completed Completed Completed Completed Completed Completed Completed In Progress In Progress Planned Requested _ Show hide columns x Y Clear Fitters Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Blog
154. incident details page for the risk in question See section 6 2 You can configure in the settings whether to use Priority or Severity for the display and also how many rows of data to display 3 4 7 Release Test Summary This widget allows you to quickly ascertain the test execution status of each of the active releases that make up the current project in one snapshot Each release is displayed together with a graphical display that illustrates the execution status with different colored bars In addition if you hover the mouse over the graphical display it will display a tooltip that provides a more detailed description of the number of tests in each status Release Test Summary vi Release Iteration Tests Execution Status 1 0 0 0 Library System Release 1 1 0 1 0 Library System Release 1 5P1 B 1 0 2 0 Libra y oystem Release 1 SP 1 1 0 0 Library System Release 1 1 1 1 1 0 Library System Release 1 1 SP 1 1 2 0 0 Library System Release 2005 aes e N N N Each release will display the aggregate status of any test cases directly assigned to itself together with the test status of any child iterations that are contained within the Release Clicking on one of the releases will drill you down one level further and display the test execution status for the parent release as well as each of the child iterations separately Release Test Summary View Details Release Iteration Tests Execution Status 1 1 0 0 Li
155. ing 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 either the lt Save gt or lt Save and New gt button at the top of the page to commit the changes In addition you can delete the current artifact by choosing lt Delete gt discard any changes made by clicking lt Refresh gt or print it by clicking lt Print gt When you make changes to the release iteration s start date end date number of project personnel resources or number of non working person days the system will automatically calculate how many hours of effort planned effort are available in the release iteration for assigning tasks As you begin assigning tasks either through the Tasks tab or the Iteration Planning screen the total estimated effort of the tasks is subtracted from this planned effort to give the available effort The lower part of the right pane can be in one of six possible modes that can be selected Incidents Tasks 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
156. into folders you can also create separate groupings of test cases called test sets which can then be assigned to testers as a package To view the list of test sets for a project click on Testing gt Test Sets in the global navigation Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing Tracking Reporting B spiraTeam Planned Date Last Executed Owner Status amp Functional Test Sets 5 Feb 2007 In Progress E Testing Cycle for Release 1 0 7 5 Feb 2007 1 Dec 2003 Joe P Smith In Progress TX000001 2 7 Feb 2007 1 Dec 2003 Joe P Smith Not Started TX000002 Testing New Functionality 4 10 Feb 2007 1 Dec 2003 Fred Bloggs In Progress Tx000005 E gt Exploratory Testing 2 22 Jan 2009 Fred Bloggs Deferred TX000006 E Regression Test Sets Completed TX000009 z Regression Testing for Windows XP 2 1 Dec 2003 Completed TX000003 o o O o o o 0o o o z Regression Testing for Windows Vista 2 1 Dec 2003 Completed TX000004 Edit ow is rows per page id lt Displaying page h of 1 gt gt 77 7 gp inset 3 Delete gt Indent lt p Outdent gt Execute The test set list consists of hierarchical list of all the test sets in the current project organized into folders 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 test sets to the system Each test set is listed along with the numbe
157. ious 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 http sandman 7helpUrl User Manual xml section 4 1 Requirements List SpiratTeam Online Help Windows Internet Explorer Table of Contents 4 1 Requirements List 1 Introduction 2 Functionality Overview 3 User Project Management El 4 Requirements Management 4 1 Requirements List 4 1 1 Insert A Tn Wekoms Fred Bloggs Ahy Prefis Log at utri riemen enr se 4 1 2 Delete wy Hs ving iin Irca Hansen 4 1 3 Indent Qom Pree Stowrkecshms w Y Choe nms 4 1 4 Outdent 4 1 5 Refresh D e Brreeme Binvrener 4 1 6 Edit In Progress l 4 1 7 Show Level In Progress 4 1 8 Filtering s 4 1 9 Show Hide Columns pode 4 1 10 Copying Requirements Come mad 4 1 11 Moving Requirements 4 1 12 Exporting Requirements 4 2 Requirement Details Taiaaiislia detente diient ciate 4 2 1 Test Coverage ES 4 2 2 Tasks EO peba tampame 4 2 3 Custom Properties Sri aa a 4 2 4 Attachments Shan monn pAr paap PEPEE a E 4 2 5 History i 4 2 6 Associations Dimi fosu pisi G wan When you click on the Planning gt Requirements link on the global navigation bar you will initially be taken to the requirements list screen illustrated below rat HE i gi 2 4 a
158. ir contact informati lot Covered Requested RQ000017 D Administration Functions Not Covered No Tasks Requested RQ000022 re Ability to completely backup the database lot Covered No Tasks Requested RQ000023 Data Import Functionality Not Covered No Tasks Requested satan OQ Ability to import from legacy system x lot Covered No Tasks Requested RQ000025 2 Ability to create new users in the system No Tasks Requested RQ000026 Ability to modify existing users in the system lot Covere No Tasks Requested RQ000027 Show fis rows per page i4 lt Displaying page a of 1 gt gt 0000 0 000000 GP inset 3 Delete gt indent lt 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 or press the lt ENTER gt key 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 In addition if you have a set of filters that you plan on using on a regular basis you can choose the option Filter gt Save Filter to add the current filter to the list of saved filters that appear on your My Page The lis
159. irements RQ2 Online Library Management System RQ3 Book Management RQ4 Ability to add new books to the system RQ5 Ability to edit existing books in the system RQ6 RQ7 RQ8 RQ9 RQ10 RQ11 RQ12 Importance Critical TC2 TC8 TC13 TC3 TC8 TC8 TC12 TC4 TC8 TC6 TC13 TC4 TC8 TC12 TC4 TC8 TC12 Critical Critical Critical Ability to associate books with different subjects Ability to associate books with different authors Critical Critical Critical 1 Critical 1 Critical Ability to associate books with different editions Ability to completely erase all books stored in the system with one click Edition Management Ability to create different editions 1 1 1 Ability to delete existing books in the system 1 Critical 1 1 1 1 11 1 5 Requirements Summary Graph The requirements summary graph shows how many requirements are currently in a project The number of requirements is displayed according to the criteria that you specify You can specify the type of data displayed along the x axis and the requirement information which is used to group the data When you first open the graph you will be asked to pick the field that you would like to display on the x axis and the field that you would like to group the data by Once you have chosen the appropriate fields and clicked the lt Select gt button the graph will be displayed Requirements Summary M1 Critcal J 2 High M 3 Medium M 4 Low Compl
160. ison 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 Iteration No Clicking on lt Clear Filters gt clears all the set filters and displays all the releases for the project In addition if you have a set of filters that you plan on using on a regular basis you can choose the option Filter gt Save Filter to add the current filter to the list of saved filters that appear on your My Page The list of saved filters can also be retrieved by clicking Filter gt Retrieve Filter Welcome Fred Bloggs My Profile Log Out Library Information System Y Project Home Planning Testing Tracking b spiraTeam Requirements Releases iterations Role Manager End Date Iteration Release Id RL e Fier 5 Library System Release 1 12 Mar 2004 216 0h Retrieve Filter RLO00001 5 Library System Release 1 SP1 30 Mar 2004 176 0h Save Filter RL000002 Library System Release 1 SP2 30 Apr 2004 352 0h RL000003 D Library System Release 1 1 SP1 No Tasks 1 Nov 2004 30 Nov 2004 336 0h RL000005 Library System Release 1 1 SP2 lo lests No Tasks 1 Dec 2004 31 Dec 2004 320 0h RL000007 Library System Release 2005 1 Apr 2005 2 Apr 2005 16 0h RL000006 Show f1s rows per page 4 4 Displaying page fi of 1 gt o o O o Library
161. ition 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 run simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the test run you need to choose File as the type and then 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 test run To attach a web link URL to the test run you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link 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 6 Test Set List As well as being able to organize test cases
162. k Save 5 5 2 Deleting the Test Run If you need to delete a test run that was erroneously captured all you need to do is click on the link to access the invalid test run and then click the lt Delete gt button to remove it from the system This will then force the system to update the status of the test case itself from the other logged test runs 5 5 3 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 TS000019 menu screen RS000002 User clicks link to create book User taken to first TS000002 screen in wizard RS000003 User enters books name and User taken to next Macbeth William TS000003 An error page is displayed No such object author then clicks Next screen in wizard Shakespeare or with block variable at line 473 gt View Incidents Each test step is displayed along with the description expected result suggested sample data a link back to the current version of the test step in question the actual result and the execution status for this step in this particular test run Where an actual result was recorded you will have an additional hyperlink View Incidents displayed This allows you to view any incide
163. l of the requirements defined for the current project in the order they appear in the requirements list The requirement s details and coverage status are displayed in a summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Req Name Description Priority Status Functional System Requirements In Fred Progress Bloggs Online Library Management System In Fred Progress Bloggs 01 Dec 2003 01 Dec 2003 11 1 2 Requirements Detailed 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 linked incidents requirements associated tasks attached documents and the change history Req 4 Ability to add new books to the system 0 Covering 0 Failed 0 Passed 0 Blocked 0 Caution 0 Covering 0 Failed 0 Passed 0 Blocked 0 Caution The ability to add new books into the system complete with ISBN publisher and other related information 1 Critical Fred Bloggs Priority Author Coverage Owner Release Joe P Smith 1 0 0 0 URL Difficulty Requirement Type http www libraries org Moderate Test Coverage Test TC2 TC8 TC
164. 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 five 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 any of the bars will bring up the project test case list see section 5 1 with the appropriate filter applied 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 4 10 Release Task Progress This widget allows you to quickly ascertain the task progress of each of the active releases that make up the current project in one snapshot Each release is displayed together with a graphical display that illustrates the completion percentage and status with different colored bars In addition if you hover the mouse over the graphical display it will display a tooltip that provides a more detailed description of the number of tasks in each status Release Task Progress view Details Release Iteration t Actual Task Progress 1 0 0 0 Library System Release 1 1 0 1 0 Library System Release 1 SP1 No Tasks 1 0 2 0 Library System Release 1 SP2 No Tasks 1 1 0 0 Library System Release 1 1 1 1 1 0 Library S
165. ldren it will be changed from a detail item into a summary item 4 1 4 Outdent Clicking on the lt Outdent gt button de indents all the requirements whose check boxes have been selected If any of the items were the only children of a Summary requirement item then that item will be 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 or just click on any of the cells in the row 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 n spiraTeam Project Home Requirements Releases Iterations Gp insert 3 Delete gt indent lt Qutdent v Not Covered D Functional System Requirements 5 A Online Library Management System Not Covered 5 2 Book Management i 5 Ability to add new books to the system if Q Ability to edit existing books in the system 7 2 Ability to delete existing books in the syste E
166. llustrating the distribution of open incidents by priority for that project That way you can see both the aggregate aging for the group and also the relative priority of open incidents for each project You can configure in the widget settings whether you want to see the aggregate aging histogram and or the project specific incident count by priority 3 5 7 Top Open Issues This section displays a breakdown of the top issues logged against any of the projects in the group 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 You can configure in the settings whether to use Priority or Severity for the display and also how many rows of data to display 3 5 8 Top Open Risks This section displays a breakdown of the top risks logged against any of the projects in the group in order of decreasing priority Note that items not given a priority are listed at the top since critical risks could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the risk item hyperlink will take you to the incident details page for the risk in question see section 6 2 You can configure in the settings
167. lt ESCAPE gt key will cancel the changes 8 1 7 Copying Tasks To copy a task or set of tasks simply select the check boxes of the tasks you want to copy and then click lt Copy gt This will make a copy of the current task with its name prefixed Copy of to distinguish itself from the original Any file attachments will also be copied along with the task itself 8 1 8 Exporting Tasks To export a task or set of tasks from the current project to another project in the system all you need to do is select the check boxes of the task s you want to export and then click the lt Export gt button This will then bring up a list of possible destination projects Welcome System Administrator My Profile Administration Log Out Library information System x S spiraTeam S Project Home Planning Tracking Incidents Tasks Role Project Owner dp NewTask 3 Delete Refresh Copy Export Showjhidecolumns Y Filter Displaying 1 4 out of 4 task s for this project Z Create edition object insert method Fred Bloggs 1 0 0 0 0003 TK000022 a Develop new edition entry screen Fred Bloggs 1 0 0 0 0003 TK000021 Z Write author object delete query gt Export Cancel Fred Bloggs 1 0 0 0 0003 TK000029 ZI Create author object delete method et Fred Bloggs 1 0 0 0 0003 TK000028 gt Edit Show fis Y rows per page 1 lt 4 Displaying page i of 1 gt gt Once you have chosen the destination project and clicked
168. mated project personnel working on that release the planned effort for the release the total effort currently scheduled as tasks the available effort for new tasking the release id and a set of custom properties defined by the project owner For those releases that have test cases mapped against them the execution status of the various test cases associated with the release is displayed in aggregate for each item as a graphical bar diagram If you position the mouse over the execution status indicator you will see the detailed execution information displayed as a tooltip For those releases that have at least one task associated with them they will display a block graph that illustrates the relative numbers of task that are on schedule green late starting yellow late finishing red or just not started grey These values are weighted by the effort of the task so that larger more complex tasks will be change the graph more than the smaller tasks To determine the exact task progress information position the mouse pointer over the bar chart and the number of associated tasks along with the details of how many are in each status will be displayed as a tooltip Clicking on a release s hyperlink will take you to the release details page for the item in question see section 7 2 7 1 1 Filtering You can easily filter the list of releases as illustrated in the screen shot below Welcome System Administrator My Profile
169. n initial set of information You can click on the name of the task to edit its information 8 1 3 Delete Clicking on the lt Delete gt button deletes the tasks whose check boxes have been selected in the task list 8 1 4 Refresh Clicking on the lt Refresh gt button simply reloads the list of tasks this is useful when new tasks are being added by other users and you want to make sure you have the most up to date list displayed 8 1 5 Show Hide Columns This drop down list allows you to change the fields that are displayed in the task 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 8 1 6 Edit Each task in the list has an lt Edit gt button display in its right most column When you click this button or just click on any of the cells in the row 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 SpiraTeam Welcome System Administrator My Profile Administration
170. n list allows you to change the fields that are displayed in the test set 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 5 6 9 Filtering You can easily filter the list of test sets as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out L rary Information System ae spiraTeam My Page Project Home Planning Testing Tracking Test Cases Test Sets Role Manager inset 3 Delete o gt indent lt gt Oudent Showlevei v aReten est D gt Beate Test Set Name Execution Status Planned Date LastExecuted Owner EE Cvs _ g amp Functional Test Sets 5 Feb 2007 In Progress TX000008 o 35 Testing Cycle for Release 1 0 7 5 Feb 2007 1 Dec 2003 Joe P Smith In Progress Tx000001 D E Testing New Functionality 4 iH 10 Feb 2007 1 Dec 2003 Fred Bloggs In Progress TX000005 gt Edit Show is rows per page id 4 Displaying page Fe ma of 1 gt gt To filter the list by any of the displayed columns you either choose an item from the appropriat
171. n names The displayed columns can be any standard field or custom property You can also filter the results by choosing items from the filter options displayed in the sub header row of each field and clicking the Apply Filter link In addition you can quickly sort the list by clicking on one of the directional arrow icons displayed in the header row of the appropriate field 5 7 3 Custom Properties In this mode the main pane displays any custom properties that the project owner has defined for test sets To learn more about how to setup and configure custom properties for a project please refer to the SpiraTest Administration Guide Test Runs The following are the custom properties of this artifact Notes Operating System Windows 2003 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 set These can be either freetext or drop down lists If you want any of the custom list properties to prepopulate the corresponding value of the test run e g you want all test runs to be marked with Operating System Windows XP make sure that both the test set and the test run are configured to use the same custom list 5 7 4 Attachments In this mode the main pane displays the list of documents that have been attached to the test set The documents can be in any format though SpiraTeam will only display the icon for certain know
172. n 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 management features of SpiraTeam 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 Planning gt Requirements link on the global navigation bar you will initially be taken to the requirements list screen illustrated below Welcome Fred Bloggs My Profile Log Out Help es spiraTeam My Page Project Home Planning Testing Tracking Reporting Requirements Releases Iterations Role Manager dp insert 3 Delete gt indent lt Outdent ShowLevel v Refresh hedt Export Show hidecolumns Y Filter
173. n types Test Runs Custom Props 0 KB Fred Bloggs 22 Jan 2009 Attach New Document URL Type URL 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 a test set simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the test set you need to choose File as the type and then 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 test set To attach a web link URL to the test set you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link Note If you are using a non Windows computer e g Macintosh that
174. ncidents 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 4 Iteration Planning As described in section 2 3 in addition to high level project releases SpiraTeam can also track the individual iterations that comprise a release giving the project manager the option to manage agile methodology projects within the SpiraTeam environment Unlike the release planning stage where high level requirements are estimated and scheduled the iteration planning phase involves assigning each of the tasks in the project backlog against a specific iteration until the available effort in the iteration has been completely allocated When you first create iterations you specify the start and end dates together with the notional number of project resources assigned to the iteration and any non working days SpiraTeam uses this information to calculate the planned effort available to the iteration from which it will subtract the estimated task effort values to determine how much effort is available to schedule 2 5 Incident Tracking Spiraleam provides the ability to create edit assign track manage and close incidents that are raised during the testing of th
175. nd 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 In addition if you click on the hyperlink displayed below the step number e g TS00003 you will be taken to the test step details page which allows you to perform additional editing of a specific test step as well as attach documents view the change history etc 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 w
176. nt 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 set of 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 eT spiraTeam S Incidents Tasks Welcome Fred Bloggs My Pro le Log Out My Page Project Home Planning Testing SP New Incident Delete Refresh J copy Export Show hide columns Y Fiter Displaying 1 14 out of 14 incident s for this project Cannot add a new book to the system 2 Database not backing up correctly Cannot install system on Oracle 9i Cannot add a new book to the system Validation on the edit book page Session handling E The homepage hangs whilst loading Permissions not updatin o o o o o o o o o o o o 0 o 2 Quote handling issues throughout y Editing the date on a book is clunky The book listing screen doesn t sort Editing the date on an author is clunky The tables get cutoff on low res modes when change w Doesn t let me add a new category d CE
177. nts that are associated with this particular test run step i Stack Trace Custom Properties RS000001 User logs in to application User taken to main TS000019 menu screen RS000002 User clicks link to create book User taken to first TS000002 screen in wizard RS000003 User enters books name and User taken to next Macbeth William TS000003 An error page is displayed No such object author then clicks Next screen in wizard Shakespeare or with block variable at line 473 gt View Incidents Incidents List for Step 3 Test Run Step RS000003 IN000007 Cannot add a new book to the system Bug ASsigmed 1 Critical Joe P Smith 4 Nov 2003 Joe P Smith Clicking on the link will change the background color of the test case to gray and display a list of all the associated test steps in a grid below the test step list Each of the incidents listed will reflect the most up to date information regarding that incident including its type status priority name assigned owner detection date and who first detected it Clicking on the incident number hyperlink will take you to the details page for that incident which is described in section 6 2 5 5 4 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 t
178. oad a new version you need to provide a description of the changes made a new version number and whether the new version should be made the active one Note If the original document was a file instead of a URL then all revisions will need to be files similarly if the original document was a URL all revisions will need to be URLs 10 2 2 Edit Document Associations This view displays a list of the artifacts in the current project that are associated with the current document If you originally uploaded the document as an attachment to a requirement test case etc then an initial association will be already listed otherwise it will be empty Versions 1 Dec 2003 Ability to create new book2 Fred Bloggs Test Case TC000002 gt Delete Add New Association Please choose the artifact that you want to add an association to Artifact Type Artifact ID e gt Add From this screen you can either delete an existing artifact association or add a new association from the current document to an pre existing artifact in the system To add the association you just need to select the type of artifact being associated requirement test case incident etc and the numeric ID of the artifact For example to add an association to Requirement RQ00005 you would choose Artifact Type Requirement and Artifact ID 5 11 Reports Center This section describes the reporting features of SpiraTeam including an overview of eac
179. oads the login web page http www libraryinformationsystem com beta Actual Result Please enter the actual test result if it differs then click the approp The screen is divided up into four main elements gt The left hand navigation pane contains the list of test cases and test steps for the currently executing test case You can click on the various links to move between the test cases and or test steps In addition each test case and 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 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 test case together with the current test step As the tester you would read the name and description of the test case then read the description of the test step carry out the instructions on the system you are testing and then compare the results with those listed as expected As described below depending on how the actual system responds you will use the buttons on the page to record what actually happened gt Below the main pane there are two optional sections The
180. object insert quenes Z Create edition object insert method a Develop new edition entry screen Z Create author object delete method Z Write author object delete query 2 Modify book insert update queries to include autho Z Refactor book details screen to include author dro A Create book subject mapping queries O Create book subject mapping delete method A Create book subject mapping insert method Z Develop book subject association screen 2 Modify book insert update queries to include editi Z Refactor book details screen to include edition dr Show rows per page In Progress In Progress In Progress Completed Completed Completed Completed Completed Completed Completed Completed OOOO000CO0OOO000OR000g Welcome System Administrator My Profile Administration Log Out Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Role Project Owner 1 0 0 0 0002 1 0 0 0 0003 1 0 0 0 0003 1 0 0 0 0003 1 0 0 0 0003 1 0 0 0 0003 1 0 0 0 0003 1 1 0 0 0001 1 1 0 0 0001 1 1 0 0 0001 1 1 0 0 0001 1 1 0 0 0001 1 1 0 0 0001 1 1 0 0 0002 1 1 0 0 0002 m TK000026 TK000027 TK000023 TK000022 TK000021 TK000028 TK000029 TK000015 TK000014 TK000013 TK000012 TK000011 TK000010 TK000017 TK000016 H lt Displaying page ofl gt hb The task list screen displays all the tasks ent
181. on 9 out of 11 test case s for this release Display data for EEE aw T amp Functional Tests 5 Fred Bloggs 1 Dec 2003 Fred Bloggs toa ee eee Ie EJ Ayo eat ensing book Caution Dee 2003 E Ability to create new author FREI 202 P smith 1 Dec 2003 Fred Bloggs Yes Tc000004 Eai E Ability to edit existing author Blocked Joe P Smith 1 Dec 2003 Fred Bloggs Yes TC000005 Pede E Ability to reassign book to different author Passed Joe P Smith 1 Dec 2003 Fred Bloggs Yes TC000006 Edit Regression Tests 2 E 1 Dec 2003 Joe P Smith Yes TC000007 P Edk amp Scenario Tests 2 Joe P Smith Joe P Smith Yes Tc000010 P Edi amp Exception Scenario Tests 1 Joe P Smith Joe P Smith Yes TC000011 E Person loses book and needs to report loss Joe P Smith Yes TC000012 E Adding new book and author to library Joe P Smith Yes TC000013 Edit amp Common Tests 2 1 Dec 2003 Fred Bloggs Yes TC000015 Edit E Open Up Web Browser Passed 1 Dec 2003 Fred Bloggs Yes TC000016 z Login to Application 1 Dec 2003 Fred Bloggs Yes TC000017 Show rows per page 14 lt 4 Displaying page 1 a of 1 gt bm o o 0 a 0 o 0 0 0 0 0 m m 0 If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to mak
182. on Library Information Limitation 4 Dec 2003 E Sample Risk 3 Library Information Risk 10 Dec 2003 Project Name Group Library Information System Sample lication One ntemal Projects 1 Dec 2005 Sample Application Two Internal Projects 1 Dec 2005 Extemal Projects 1 Dec 2005 Name Project Critical Not Covered Requirements Library Information System gt Delete Z Failed Active Test Cases Library Information System gt Delete W New Unassigned Incidents Library Information System gt Delete W All Reopened Incidents Library Information System gt Delete Z High Priority Late Tasks Library Information System gt Delete Z Not Executed Test Sets Library Information System gt Delete Project Importance Status T Ability to create different editions Library Information T Ability to link authors to their contact Library Information T Ability to edit existing authors in the Library Information T Ability to delete existing authors in th Library Information T Ability to create new users in the syste Library Information F Ability to import from legacy system x Library Information Name Project Status Last Executed z Ability to create new book gt Execute E Ability to edit existing book gt Execute Library Information Library Information W Cannot log into the application W Clicking on link throws fatal error Project Library Information Library Information E Cannot install system on Windows ME Libr
183. on the left being the hierarchical list of the test cases belonging to the project arranged in test folders The right box which will initially be empty contains the list of test cases mapped to this release iteration The test cases in this box include columns for their ID and name Hovering the mouse over the names of the test cases in either box will display a tooltip consisting of the test case name place in the folder structure and a detailed description Clicking on the hyperlinks in right hand box will jump you to the test case details screen for the test case in question see section 5 2 9 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 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 Set from This Release link to create a new test set from this release that will include all of the test sets associated with this release This is useful in regression testing when you have created a new release and want to be able to quickly assign a tester to ensure that all the functionality in the release works as expected 7 2 4 Custom Proper
184. on the test set folder you want to move and then drag the icon to the location you want it moved The background of the destination location will change as the icon is dragged over it to illustrate where it will be inserted Once you have the test set folder positioned at the correct place that you want it inserted just release the mouse button and the test set list will be refreshed with the item moved to the desired location 2 Alternatively you can simply select the check boxes of the test sets you want to move and then select the Edit gt Cut menu option This will cut the current test set selection to the clipboard Then you should select the place where you want the test sets to be inserted and choose the Edit gt Paste option The test sets will now be moved into the destination location you specified 5 7 Test Set Details When you click on a test set item in the test set list described in the previous section you are taken to the test set details page illustrated below Welcome Fred Bloggs My Profile Administration Log Out My Page Project Home Planning Testing Tracking Reporting e spiraTeam Test Cases Test Sets gt Test Set Details Role Manager lt lt Back to Test Set List Sae pSaveandNew 3 Delete Refresh gt Execute Print Functional Test Sets Test Set Testing Cycle for Release 1 0 TX 000001 amp aT for Rel i a i prac ar riar ts Name Testing Cycle for Rele
185. ons RQ13 Author Management RQ17 Ability to link authors to their contact information Status In Progress In Progress Completed Completed Completed Completed In Progress Requested Priority 1 Critical 1 Critical 1 Critical 1 Critical 2 High 2 High Mapped Test Cases Test Name Status TC4 Ability to create new author Failed TC2 Ability to create new book Failed TC5 Ability to edit existing author Blocked Last Execution Date 01 Dec 2003 04 Dec 2003 01 Dec 2003 11 5 3 Release Plan Report This report displays a complete work breakdown structure of the project from a release perspective including all releases iterations requirements tasks and incidents organized by schedule Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library RL1 1 0 0 0 Library System Release 1 RQ4 RQS RQ6 RQ12 RQ15 RQ16 Abiy to add new books to the system Ability to edit existing books in the system Ability to delete existing books in the system Ability to create different editions Ability to edit existing authors in the system Ability to delete existing authors in the system Type Status Release Requirement Requirement Requirement Requirement Requirement Requirement Priority Owner Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs End Date Complete Plan Effort
186. or the name of the project group in the My Page project list you will be taken to the homepage of the specific project group in question Welcome Fred Bloggs My Profile Administration Log Out Help a e spiraTeam S My Page Project Home Planning Testing Tracking Reporting Project Group Home Project Home Documents Role Manager Project Group Internal Projects PG000002 Modify Layout Settings Add Items Group Overview Project List Contains the library project and sample application one Project Name Web Site Creation Date Web Site www libraryinformationsystem org Library Information System http www libraryinformationsystem_org 1 Dec 2005 Owner s Fred Bloggs System Administrator Sample Application One http Awww tempuri org 1 Dec 2005 Requirements Coverage 10 Test Execution Status 4 0 Passed Failed Blocked Caution Not Run Not Covered Project Reqs Coverage Failed Passed Not Run Blocked Caution TA E E EE 18 E Project Tests Runs Execution Status s 7 E Sample Application One 1 me Library Information System 11 19 D Sample ication One 1 1 Task Progress aa Incident Aging 35 On Schedule Late Finish Late Start Not Started 0 Project Tasks Est Actual Task Progress 0 15 16 30 3145 46 60 61 75 76 90 Library Information System 39 190 0h 188 71 B ote prec tam Library Information System 34 i Sample Application One 1 Sample Application One 0 0 0h 0 0h No Tasks
187. ose to filter by a specific release to get the homepage for just that release and any child iterations In a similar manner to the My Page the Project Home dashboard is initially loaded in view mode which means that the various widgets on the page are displayed with minimum visual clutter no toolbars or control icons that makes it easy to scan the items on the page and see the health of the status of the project at a glace To switch the page to edit mode you should click on Modify Layout Settings hyperlink Once in edit mode each of the widgets displayed on the project homepage can be minimized by clicking on the arrow icon in the top left of the window or closed by clicking on the cross icon x in the top right of the window In addition the widgets allow you change their settings by clicking on the settings icon This allows you to customize your view of the project to reflect the types of information that are relevant to you If you have closed a widget that you subsequently decide you want to reopen you can rectify by clicking the Add Items hyperlink at the top of the page and locating the closed item from the list of Closed Widgets When you load your Project Home for the first time it will consists of the following main elements v Project Overview Requirements Summary Requirements Coverage Release Task Progress Late Finishing Tasks Late Starting Tasks Top
188. owing actions on a task from this screen gt New Task inserts a new task in the task list with a default set of values The task will be associated with the current release iteration gt Remove removes the task from this release iteration without actually deleting the task gt Delete deletes the task itself 7 2 3 Test Case Mapping This mode displays the test case mapping information for the release in question Incidents set Cases Custom Props Test Runs Attachments History Available Test Cases Test Coverage E Functional Tests Tcoo0004 Ability to create new author Ej Ability to create new book Adda TC000002 Tj Ability to create new book Tj Ability to edit existing book E TC000005 E Ability to edit existing autho 5 Ability to create new author Remove lt Tcoo0003 3 Ability to edit existing book E Ability to edit existing autho Remove All TC000006 Ability to reassign book to di 2j Ability to reassign book to di TcC000009 4 Author management O G Regression Tests 7000008 Book management O G Scenario Tests Create Test Set From This Release 42 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 The pane consists of two lists of test cases the one
189. ows of documents to display on the page at one time gt The bottom left hand pane contains all the Operations that can be performed on the document list You can use the various icons to add documents to the current folder delete existing documents from the project refresh the list of documents export documents to another project and options to apply the selected filter 10 1 1 Add New Document To add a new document to the project you just need to click on the lt Add Document gt icon in the Operations list and the Add New Document dialog box will be displayed Welcome Fred Bloggs My Profile Log Out Planning Project Home Documents amp Root Folder B Design Documents amp Misc Documents Screen Captures Specifications Type Filename Add New Document File URL Library information System v Testing 10 May 2006 1 May 2006 23 Apr 2006 2 Apr 2006 Fred Bloggs Joe P Smith Fred Bloggs Joe P Smith Role Manager oe DC000007 DC000013 DC000012 DC000008 Test Results ee ft te 1 Apr 2006 Joe P Smith DC000011 Operations pa deal hace Document Type Delete Document Tags h Refresh Documents gt Upload Cancel Y Apply Current Filter 3 Clear All Filters g Export Documents From here you need to either browse to the file being uploaded or enter in its URL and then enter the description optional choose the type of docum
190. quently decide you want to reopen you can rectify by clicking the Add Items hyperlink at the top of the page and locating the closed item from the list of Closed Widgets When you load the Project Group Home for the first time it will consists of the following main elements gt Group Overview Requirements Coverage Task Progress Project List VV V V Test Execution Status gt Incident Aging However these are not the only widgets available If you click on the Add Remove items hyperlink it will display the list of any additional widgets that are available Add Remove Items Close Select the catalog you would like to browse Closed Widgets 0 Available Widgets 2 Available Widgets F Top Open Bsues L Top Open Risks Add to Left Side v You can add the additional widgets by selecting the appropriate checkbox choosing the destination location left side vs right side and then click the Add button The additional widgets available in the Project Group Home dashboard are gt Top Open Issues gt Top Open Risks Each of the different widgets listed is described in more detail below 3 5 1 Group Overview This section displays the name of the project group together with a brief description the web site that points to any additional information about the project group and the names of the owners of the project group 3 5 2 Project List This section lists all the active projects tha
191. r Windows Vista 2 1 Dec 2003 Completed TX000004 gt Edit ow rows per page id lt Displaying page i a of 1 p oO o 0 o o o o o w 7 dp insert 3 Delete gt indent lt p Outdent gt Execute If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all the editable rows and then update the changes by clicking the one lt Update gt button Also if you want to make the same change to multiple rows e g to change the owner of five test sets from Fred Bloggs to Joe Smith you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the lt ESCAPE gt key will cancel the changes 5 6 7 Show Level Choosing an indent level from the Show Level drop down box allows you to quickly and easily view the entire test set list at a specific indent level For example you may want to see all test set drilled down to the third level of detail To do this you would simply choose Level 3 from the list and the test sets will be expanded accordingly 5 6 8 Show Hide Columns This drop dow
192. r a place to save it on your local computer To delete an existing attachment from a task simply click the lt Delete gt button and the attachment will be removed from the list To attach a new document to the task you need to choose File as the type and then 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 task To attach a web link URL to the task you need to choose URL as the type and then enter the fully qualified URL e g http mywebsite com Document 1 an optional description and then click the lt Upload gt button to attach the web link 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 8 2 4 View History In this mode the main pane displays the list of changes that have been performed on the task artifact since its creation An example task change history is depicted below General Custom Properties Attachments 2 26 2008 12 49 04 PM Release Id System Administrator 2 26 2008 12 48 59 PM Release Id 8 9 System Administrator 2 26 2008 12 48 51 PM Task Priority 1 Critical 2 High
193. r of test cases contained in parenthesis the aggregate execution status of the contained test cases using a graphical bar chart the date that the test set has been scheduled to be executed planned date the date that it was last executed the person currently assigned to execute the test set the status and the test set id Clicking on a test set s hyperlink will take you to the test set details page for the item in question 5 6 1 Insert Clicking on the lt Insert gt button inserts a new test set before the currently selected by means of the check box test set Clicking the lt Insert gt button without selecting a test set will insert a new test set at the end of the list 5 6 2 Indent Outdent Clicking on the lt Indent gt button indents all the test folders test sets whose check boxes have been selected You cannot indent a test set or folder if it is below a test set as test sets are not allowed to have child items Clicking on the lt Outdent gt button de indents all the test folders test sets whose check boxes have been selected 5 6 3 Delete Clicking on the lt Delete gt button deletes the currently selected test sets It will delete the association between the test set and its contained test cases but it will not delete the test cases themselves 5 6 4 Execute Clicking on the lt Execute gt button executes all the test sets selected The test execution functionality of SpiraTeam is explained in more de
194. red Bloggs E 10 Mar 2004 Open 3 4 2 2 4 15 Reopen 0 Late Starting Tasks View Al TOTAL a 7 1 i ina Name Owner Priority Start Date 7J Write edition object insert quenes Fred Bloggs 11 Mar 2004 Incident Open Count view Details 7 Refactor author screen to include delete Fred Bloggs 9 Mar 2004 Z Write author object update queries Joe P Smith 7 Mar 2004 7 Create author object update method Joe P Smith 7 Mar 2004 71 Develop edit author details screen Joe P Smith 7 Mar 2004 0 None 1 Critical 2 High 3 Medium 4 Low Requirement Incident Count Requirement Name Ability to add new books to the system Ability to associate books with different editions T Ability to edit existing books in the system Ability to associate books with different subjects Ability to associate books with different authors Ability to completely erase all books stored in the system w Ability to create new users in the system Open M A AD Be This page summarizes all of the information regarding the project into a comprehensive easily digestible form that provides a one stop shop for people interested in understanding the overall status of the project at a glance It contains summary level information for all types of artifact requirements test cases incidents etc that you can use to drill down into the appropriate section of the application In addition to viewing the project home page you can cho
195. rent project in the order they appear in the test case list The test case s details and execution status are displayed in a summary grid form with the test steps optionally displayed Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Test Name Functional Tests Description Priority Test Step Test Step Description Test Step Expected Result Test Step Sample Data Status Author Owner Est Duration Created On Last Modified N A Fred Fred 01 Dec 13 Oct 2009 Bloggs Bloggs 2003 15 07 47 Tests that the user can create a new book in the system Ability to create new book Fred Fred 01 Dec 2003 13 Oct 2009 Critical 15 07 47 Bloggs Bloggs 10 Call Login to Application User clicks link to create book User enters books name and author then clicks Next User chooses book s genre and sub genre from list User clicks submit button Not Run User taken to first screen Not Run in wizard User taken to next screen Macbeth William in wizard Shakespeare Not Run User sees screen displaying all entered information Play Tragedy Not Run Confirmation screen is displayed Not Run 11 2 2 Test Case Detailed Report This report displays all of the test cases defined for the current project in the order they appear in the test case list The test case s details and execution status are displayed along with sub ta
196. resents 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 on the Display Data Grid link will display the underlying data that is being used to generate the graph Clicking the Back to Project Home hyperlink will take you back to the Project Home dashboard 11 3 6 Open Incident Count Graph 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 incident 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 Welcome System Administrator My Profile Administration Log Out Library information System f Help ee gt spiraTeam My Page Project Home Planning Testing Tracking Reporting Reporting gt Incidents Open Count Role Project Owner lt lt Back to Reports Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Turnaround Time Incident Type
197. right hand box will jump you to the requirement details screen for the requirement in question see section 4 2 To change the coverage for this test case you use the buttons Add Remove Remove All positioned between the two list boxes The lt Add gt button will move the selected requirements from the list of available on the left to the list of mapped on the right Similarly the lt Remove gt and lt Remove All gt buttons will remove either the selected or all the requirements from the right list box and add them back to the left list box 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 History
198. rs E Export Documents u gt View Details Cancel You can click on the document URL to actually open the document itself in a new window click on the meta tag links to find related documents that contain the same meta tag or click on View Details to see more information regarding the document including an ability to edit its meta information and see the different versions of the document 10 2 Document Details When you click on a test case item in the document list described above you are taken to the document details page illustrated below Welcome Fred Bloggs My Profile Log Out Library information System Y Help My Page Project Home Planning Testing Tracking Reporting _ _ s spiraTeam Project Home Documents gt Document Details Role Manager lt lt Back to Document List 8 Save Delete E Refresh Design Documents Document Sequence Diagram for Book Mat pdf DC000007 E Sequence Diagram for Book Mgt pdf Graphical Design Mockups psd Filename Sequence Diagram for Book Matpdf Use Case Diagram vsd Description 2 Author Management Sereen Wuellame vad Sequence diagram in UML format that provides additional detail surrounding the book managament use case test w Book Management Screen Wireframe ai case Document Folder Created By Document Type UML Diagram v Edited By Joe P Smith v Tags sequence diagram book management Created On 5 3 2006 12 00 00 AM File Type
199. rs Refresh v DocumentName AY Type AW Size AYO Uploaded By AY Doc AY Biriani O ar el O e je __ Design Documents be Sequence Diagram for Book Mat pdf UML Diagram Joe P Smith 10 May 2006 Fred Bloggs DC000007 Misc Documents TA Graphical Design Mockups psd Screen Layout 1009 Joe P Smith 1 May 2006 Joe P Smith DC000013 Screen Captures Use Case Di agram vsd UML Diagram 43 Fred Bloggs 23 Apr 2006 Fred Bloggs DC000012 Specifications E Author Management Screen Wireframe ved Screen Layout 533 Fred Bloggs 2 Apr 2006 Joe P Smith DC000008 Test Results C Book Management Screen Wireframe ai Screen Layout 392 Fred Bloggs 1 Apr 2006 Joe P Smith DC000011 Ly Show fis Y rows per page id lt 4 Displaying page a of 1 pi P Add Document 3 Delete Document R Refresh Documents a spiraTeam o O oO o Y Apply Current Filter 3 Clear All Filters EZ Export Documents This screen consists of three main sections gt The top left hand pane displays a hierarchical list of the various folders that have been setup for the current project Clicking on the expand icon will expand the child folders and clicking on the name of the folder will display the list of documents in the folder in the main pane to the right gt The main right hand pane displays a list of all the documents contained within the currently selected folder This list can be filtered and sorted and you can choose how many r
200. s 70 mins 90 mins 75 mins 01 Dec 2003 01 Dec 2003 01 Dec 2003 Testing Cycle for Release 1 1 Testing Cycle for Release 1 0 R ir n ver e Req RQ4 Name Ability to add new books to the system Status Completed Priority 1 Critical 11 2 3 Test Set Summary Report This report displays all of the test sets defined for the current project in the order they appear in the test set list The test set s details and execution status are displayed in a Summary list form Test Set Summary Report This report displays all of the test sets defined for the current project in the order they appear in the test set list The test set s details and execution status are displayed in a summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Test Set Name Description Status Release Creator Owner Created On Planned Date Last Modified Last Executed Passed Failed Caution Blocked Not Run Notes Functional In Fred 02 Jan TX8 Test Sets Progress Bloggs 2007 05 Feb 2007 13 Oct 2009 0 0 0 0 0 This tests the functionality introduced in Fred JoeP 02Jan in release Progress Bloggs Smith 2007 1 0 of the library system This tests the functionality introduced Not Fred JoeP 03 Jan Testing Cycle for Release 1 0 05 Feb 2007 13 Oct 2009 01 Dec 2003 1 Testing Cycle for Release 1 1 in release Started Blog
201. s Joe P Smith Joe P Smith Joe P Smith 3 Dec 2003 10 Dec 2003 IN000025 IN000029 IN000035 IN000040 IN000045 IN000046 IN000050 INO00055 IN000059 IN000026 IN000022 gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit gt Edit E Quote handling issues throughout Bug Resolved Fred Bloggs Fred Bloggs IN000012 Edit 2 Editing the date on a book is clunky Bug Assigned Joe P Smith Fred Bloggs IN000008 Edit Show rows per page ia lt Displaying page 2 of 4 gt pi 000000000000000 W Support for IBM DB2 Enhancement Fred Bloggs IN000019 gt Edit 2 The homepage hangs whilst loading Bug Not Joe P Smith Fred Bloggs IN000016 Edit 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 over the incident name hyperlink and waiting for the popup tooltip to appear If you click on the incide
202. s IN000017 Edit Joe P Smith 2 Nov 2003 IN000004 reoeo JED 282009 how YE tor 208 2 Cannot add a new book to the system Bug Duplicate Database not backing up correctly Bug Open Cannot install system on Oracle 9i E Sug v E Open vE Cannot add a new book to the system W Validation on the edit book page Bug E session handling Bug The homepage hangs whilst loading Bug E Quote handling issues throughout Bug x Editing the date on a book is clunky W The book listing screen doesnt sort Bug Editing the date on an author is clunky The tables get cutoff on low res modes E Permissions not updating when changed 0000o 0o mo oO Oog E Doesn t let me add a new category Show rows per page Resolved Closed Resolved Assigned Open Assigned Closed Closed Resolved Fred Bloggs Joe P Smith 15 Nov 2003 15 Nov 2003 15 Nov 2003 15 Nov 2003 4 Nov 2003 2 Nov 2003 4 Nov 2003 15 Nov 2003 15 Nov 2003 4 Nov 2003 Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs IN000011 IN000015 IN000016 IN000012 IN000008 IN000006 IN000009 Edit IN000013 IN000014 IN000010 4 lt Displaying page i a of 1 gt mi If you click lt Edit gt on more than one row the lt Update gt and lt Cancel gt buttons are only displayed on the first row and you can make changes to all
203. s its test coverage status and its task progress For those requirements that have no test cases covering them i e validating that the requirement works as expected the indicator consists of a white 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 display a green bar 50 passed and an equal length gray bar 50 not run 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 blocked caution not run breakdown will be displayed as a tooltip For those requirements that have at least one task associated with them they will display a block graph that illustrates the relative numbers of task that are on schedule green late starting yellow late finishing red or just not started grey These values are weighted by the effort of the task so that larger more complex tasks will be change the graph more than the smaller tasks To determine the exact task progress information position the mouse pointer over the bar chart and the number of associated tasks along with the details of how many are in each status will be display
204. s 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 2 9 My Detected Incidents This section lists all the open incidents that you have detected across all the different projects you are a member of These incidents are not necessarily ones that you need to take an active role in resolving but since you were the originator either by executing a test case or just logging a standalone incident you can watch them to make sure that they are resolved in a timely manner 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 2 10 My Saved Reports This section lists any reports you have saved from the reports center This allows you to store specific combinations of report elements format filters and sorts See the section on Reporting for more details on how to configure a report for reports that you need to run on a regular basis My Saved Reports Name Project v1 0 Release List Report Library Information System gt Delete 3 3 Global Navigation Regardless of the page you are on SpiralTeam will always display the global
205. s the aggregated count of requirements test coverage for the project in a similar fashion to the Requirements Coverage widget Requirements Regression Coverage View Details 9 Passed Failed Blocked Caution Not Run Not Covered However unlike the Requirements Coverage widget when you filter the project home by release iteration this widget will filter the requirements coverage graph to include all requirements regardless of release iteration but only considering covering test cases that are associated with the selected release iteration This is useful when you want to determine the regression requirements test coverage of a specific release i e does running all the tests relevant to this release cover all the necessary requirements not just new requirements 3 4 14 Test Set Status This section consists of a bar graph that displays the aggregated count of test cases in each execution status for each test set in the project Test Set Status View Details 20 Overdue Test Sets TXO00001 5 Feb 2007 TX000002 7 Feb 2007 TXOOO005 10 Feb 2007 Failed Passed Not Run Blocked Caution Therefore if you have the same test cases stored in multiple test sets then this widget will display the total test case count for all combinations of test set This is useful if you have the same test cases being executed in different environments represented by different test sets and you need to make sure that the tests pas
206. se and any child iterations if applicable 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 Tools gt Execute menu option 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 Administration Log Out My Page Project Home Planning Testing Tracking Reporting g spiraTeam Test Cases gt Test Case Details Test Sets Role Manager Pak O Taie _ Sae PSaveandiNew 3 Delte h Refresh gt Execute Print Functional Tests Test Case Ability to create new book TC 000002 amp 2 Ability to create new book aaa Alias io anato neerboak z Ability to edit existing book F Abi ility to create new author ee M pae E Ability to edit existing autho J ma C aw TT 24 Abilit tn a book to lt i Tests that the user can create a new book in the system Author Estimated Time o hours minutes Owner Creation Date 12 1 2003 12 00 00 AM Priority v Execution Status Failed Active Yes v Execution Date 12 4 2003 9 40 01 AM Req Coverage Custom Props Test Runs Releases
207. sed successfully in all environments If you position the mouse pointer over any of the five 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 any of the bars brings up the project test set list see section 5 6 page with the appropriate filter applied In addition to the bar chart there is a also a display of the five most overdue test sets in the project 3 4 15 Incident Aging This section displays the number of days incidents have been left open in the system The chart is organized as a histogram with the count of incidents on the y axis and different age intervals on the x axis 3 4 16 Incident Test Coverage This section displays a bar graph that illustrates the execution status of any test cases that previously failed and resulted in the generation of an incident that has subsequently been resolved This is very useful when a test case was executed in Release 1 0 and an incident was logged That incident has now been resolved in Release 1 1 and is in a closed status but we need to know that the test case that caused the failure has been successfully re run Any test cases listed as Blocked Caution Not Run or Failed in this graph need to be executed to verify that all resolved bugs in the release have truly been fixed 3 5 Project Group Home When you click on either the Project Group Home tab in the global navigation
208. st runs and incidents that are related to the child iterations will get included in the release reports Child releases on the other hand are not aggregated up into the parent release 7 1 Release List When you click on the Planning gt Releases global navigation link you will initially be taken to the release list screen illustrated below Help Welcome System Administrator My Profile Administration Log Out spiraTeam a Project Home Testing Tracking Reporting Show hide columns Y Fiter My Page Show Level m amp Refresh Dy Eat A Export Planning Requirements Releases Iterations Role Project Owner dp insert 3 Delete gt indent lt Outdent vV Release Name Version E ad I C ee el O o o o o o o O Oo o o O O O Oo O 50 Library System Release 1 39 Library System Release 1 SP1 E iteration 001 E iteration 002 E iteration 003 5 amp Library System Release 1 SP2 2 iteration 001 E iteration 002 E iteration 003 E iteration 001 E iteration 002 iteration 003 Library System Release 1 1 a Library System Release 1 1 SP1 a Library System Release 1 1 SP2 Show rows per page dp insert 3 Delete gt Indent 1 0 0 0 1 0 1 0 1 0 1 0 0001 1 0 1 0 0002 1 0 1 0 0003 1 0 2 0 1 0 2 0 0001 1 0 2 0 0002 1 0 2 0 0003 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 1 1 0 0 1 1 1 0 1 1 2 0 lt Qutdent p lests No Tests 10
209. stem 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 Tracking gt Incidents global navigation link you will initially be taken to the incidents list screen illustrated below Welcome Fred Bloggs My Profile Log Out Help My Page Project Home Planning Testing Tracking Reporting n spiraTeam S Incidents Tasks dh New Incident 3 Delete Refresh h Copy K Expot Show hide columns v Y Fiter Displaying 16 30 out of 60 incident s for this Sy es He Ay mo l Role Manager 2 Ability to generate customized reports Enhancement Ability to associate multiple authors Enhancement W Section 508 compliance Issue Test Training tem Training ba Test System Limitation Limitation Test System Limitation Limitation Test System Limitation Limitation Change Request amp Test Change Request 2 Sample Risk 1 Risk Enhancement bal Confiqurable meta data columns integration of security with NTLM PKI Enhancement Resolved Duplicate Closed Assigned Open Assigned Duplicate Closed Open Resolved Joe P Smith Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Fred Blogg
210. sts gt Create Test Case From This Requirement S 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 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 The right box which will initially be empty contains the list of test cases mapped to this requirement The test cases in this box include columns for their ID name and execution status Hovering the mouse over the names of the test cases in either box will display a tooltip consisting of the test case name place in the folder structure and a detailed description Clicking on the hyperlinks in right hand box will jump you to the test case details screen for the test case in question 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
211. t gt Cut menu option This will cut the current test case selection to the clipboard Then you should select the place where you want the test cases to be inserted and choose the Edit gt Paste option The test cases will now be moved into the destination location you specified 5 1 12 Exporting Test Cases To export a test case or set of test cases from the current project to another project in the system all you need to do is select the check boxes of the test case s you want to export and then click Tools gt Export Tests This will then bring up a list of possible destination projects Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning Testing Tracking Reporting ee spiraTest Test Cases Test Sets Role Manager dhimet f Dele gt indent Outlet ShowLevel gt Retresn FTos D gt Dece Show hide columns Y Clear Fier Displaying 7 out of 7 test case s for this release Display data for Author Active Test Te amp Functional Tests 5 Fred Bloggs TC000001 Ability to create new book k Fred Bloggs Tc000002 EJ Ability to edit existing book gt Export Cancel F Fred Bloggs TC000003 2 Ability to create new author dan Ue UEC Fred Bloggs TC000004 E Ability to edit existing author Blocked Joe P Smith 1 Dec 2003 Fred Bloggs TC000005 2 Ability to reassign book to different author Passed Joe P Smith 1 Dec 2003 Fred Bloggs TC000006 Regression Tests 2 m 1 Dec 2003 Joe
212. t make up the group together with the name description project group 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 3 5 3 Requirements Coverage This section consists of a bar graph that displays the aggregated count of requirements test coverage for the entire project group 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 Under the main bar graph is displayed a table containing each project in the group and a colored bar illustrating the specific requirements coverage distribution for that project That way you can see both the aggregate coverage and also the relative coverage for the projects You can configure in the widget settings whether you want to see the aggregate bar graph and or the project specific requirements coverage 3 5 4 Task Progress This section consists of a bar graph that displays the aggregated count of tasks by progress category for the entire project group The On Schedule Late Finish Late Start and Not Started bars indicate the total count of tasks that are in that category for all the projects in the group Under the main bar graph is displayed a table containing each project in the group and a colored bar illustrating the spec
213. t of saved filters can also be retrieved by clicking Filter gt Retrieve Filter Welcome Fred Bloggs My Profile Log Out Project Home Planning Testing Tracking Reporting spiraTeam Requirements Releases Iterations Role Manager Outen Satan ea G egot Y Ee Status V Apply Fiter Req Edit v clear Fitter 5 Functional System Requirements In Progress gt Retrieve Filter RQ000001 gt Edit Online Library Management System In Progress A save Fitter RQ000002 gt Edit D Book Management Completed RQ000003 gt Edit 2 Ability to add new books to the system gt Save Cancel Completed Moderate RQ000004 gt Edit Ability to edit existing books in the system Completed RQ000005 gt Edit Q Ability to delete existing books in the system Completed RQ000006 gt Edit 2 Ability to associate books with different subjects Completed RQ000007 gt Edit Q Ability to associate books with different authors Completed RQ000008 gt Edit QO Ability to associate books with different editions Completed RQ000009 gt Edit Qo Ability to completely erase all books stored in th Completed RQ000010 gt Edit D Edition Management Not Covered In Progress RQ000011 gt Edit 2 D Author Management Not Covered In Progress RQ000013 Edit D Subject Management Not Covered Planned RQ000019 Edit D Administration Functions Not Covered Requested RQ000022 gt Edit Show 1s Y
214. t time it will consists of the following main elements gt My Projects My Saved Searches My Assigned Requirements My Assigned Test Cases My Assigned Test Sets VV VV y My Pending Test Runs gt My Assigned Incidents My Detected Incidents gt My Assigned Tasks However these are not the only widgets available If you click on the Add Remove items hyperlink it will display the list of any additional widgets that are available Add Remove Items Close Select the catalog you would like to browse Clozed Widgets 0 Available Widgets 1 Available Widgets L My Saved Reports Add to Left Side iw You can add the additional widgets by selecting the appropriate checkbox choosing the destination location left side vs right side and then click the Add button The additional widgets available in the My Page are gt My Saved Reports 3 2 1 My Projects This section lists all the projects you have been given access to together with the name description project group 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 w
215. tail in section 5 3 5 6 5 Refresh Clicking on the lt Refresh gt button simply reloads the list of test sets This is useful if other people are making changes to the test set list and you want to make sure that you have the most current version 5 6 6 Edit Each test set in the list has an lt Edit gt button display in its right most column When you click this button or just click on any of the cells in the row 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 Welcome Fred Bloggs My Profile Log Out L rary information System x My Page Project Home Planning Testing Tracking 7 spiraTeam ee Test Cases Test Sets Role Manager Gp insert 3 Delete g gt indent lt Outdent a D gt Beane Showihide columns v Y Fiter 5 amp Functional Test Sets aa In Progress TX000008 Edit amp Testing Cycle for Release 1 0 Eg 2 5 2007 ff 1 Dec 2003 jJoePSmth YE in Progress V ED d Testing Cycle for Release 1 1 a 2 7 2007 1 Dec 2003 JoePSmth Y Not Started Y E Testing New Functionality 4 10 Feb 2007 1 Dec 2003 Fred Bloggs In Progress Tx000005 P Edt 3 Exploratory Testing 2 22 Jan 2009 Fred Bloggs Deferred TX000006 ij Regression Test Sets Completed Tx000009 Peat z Regression Testing for Windows XP 2 1 Dec 2003 Completed TX000003 Edit amp Regression Testing fo
216. tails Standard Field Filters Author All Importance Owner Status Created On Last Modified Requirement Task Progress Test Coverage Requirement Name Actual Effort Plan Effort Task Effort Release Requirements Details Custom Property Filters URL Difficulty Requirement Type If would like to save this report for future use please give it a name below before clicking the Create Report button Report Name C would like to share this report with other members of the project You can configure the reports in the following ways gt Report Format This allows you to specify the display format of the report Depending on the specific report they can be displayed as a web page HTML downloaded as a Microsoft Word document downloaded as a Microsoft Excel spreadsheet or downloaded as a Microsoft Project file In addition there is a raw XML format that allows you to export the underlying report data into any external reporting system that supports XML import 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 attachments test steps coverage history etc gt Standard Field 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
217. ted By Owned By Detected On Last Modified Closed On Detected Release Resolved Release application with a valid username incident 01 Nov and password 2003 the system throws a fatal exception When try and click on the button to add a new author the incident 01 Nov system simply 2003 displays the main screen and does nothing When click on the logout link instead of 01 Nov logging out get scenes 2003 an ASP session not valid error Cannot log into the application 01 Dec 2003 Not able to add new author 01 Dec 2003 Clicking on link throws fatal error 01 Dec 2003 11 3 2 Incident Detailed 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 linked requirements incidents and the change history Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Inc 1 Cannot log into the application When trying to log into the application with a valid usemame and password the system throws a fatal exception Priority Severity Opened On 01 Nov 2003 Last Modified 01 Dec 2003 Closed On Verified In Releas
218. ted effort for the iteration will increase and the available effort will decrease by the same amount Note The system will allow you to assign more tasks incidents to an iteration than is possible to complete however this will result in a negative value for available effort If this happens you need to rebalance the items extend the iteration length or add project personnel resources to the iteration 7 3 2 Rescheduling Tasks Incidents To move tasks incidents from one iteration to another you either position the mouse pointer over a single task incident icon dragging it to the desired new iteration or you select several checkboxes in the existing iteration and then drag all the selected items to the destination iteration in one go To remove a task incident from an iteration you should just drag and drop it from the iteration panel back to the task incident task list at the bottom of the page This will return the task incident to the list of unplanned items at the bottom of the page Note Once a task has changed status from not started to any of the other statuses its checkbox will be disabled and you will need to return it to the not started status before attempting to reassign it This is a safety feature that prevents you from accidentally rescheduling a task that is currently being worked on 7 3 3 Task Assignment Rules When you move a task from one iteration to another or assign a new task to the iteration the s
219. the lt Export gt button This will then bring up a list of possible destination projects Welcome System Administrator My Profile Administration Log Out Library information System v Help My Page Project Home Planning Testing Tracking Reporting es spiraTteam i Incidents Tasks dp New Incident 3 Delete Refresh J Copy Export Show hide columns Y Filter Displaying 1 14 out of 14 incident s for this project vV IncidentName AY of C aaam Role Project Owner Owned By AY Inc BAY Edt m Export Items Detected On AY OOO00O00O0O000800 W Cannot add a new book to the system H Database not backing up correctly W Cannot install system on Oracle 9i H Cannot add a new book to the system u Validation on the edit book page W Session handling u The homepage hangs whilst loading W Quote handling issues throughout u Editing the date on a book is clunky u The book listing screen doesn t sort H Editing the date on an author is clunky u The tables get cutoff on low res modes u Permissions not updating when changed 2 Doesnt let me add a new catego Show is Y rows per page dp New Incident 3 Delete amp Refresh Resolved Closed Not Reproducible Resolved Assigned Open Assigned Closed Closed Resolved 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 15 Nov 2003 2 Nov 2003 2 Nov 2003
220. the lt Export gt button the tasks will be exported from the current project to the destination project Any file attachments will also be copied to the destination project along with the tasks 8 2 Task Details When you click on a task item in the lists displayed on either the main task list page or on the requirement release details pages you are taken to the task details page illustrated below Welcome Fred Bloggs My Profile Log Out a Wes spiraTeam My Page Project Home Planning Testing Tracking Reporting Requirements Releases gt Task Details Iterations Role Manager id Finck to Tak Lit E Sae pSaveandNew 3 Delte amp Refresh Print E iteration 002 Task Name Refactor book details screen to include edition drop down TK000016 1 Refactor book details screen to include i i 1 i Name JM odify book insert update queries to inc Refactor book details screen to include edition drop down 4 4 r Z Develop author subject association scree Description CO Create author subject mapping insert met Z Create author subject mapping delete met Z create author subject mapping quenes Priority Owner Requirement Ability to associate books with different editions Last Updated 12 1 2003 12 00 00 AM Release Iteration 1 1 0 0 0002 teration 002 Created On 12 1 2003 12 00 00 AM 10 19 2004 10 23 2004 Custom Properties Attachments This page is made up of three areas the left pane is the naviga
221. the criteria that you specify You can specify the type of data displayed along the x axis and the task information which is used to group the data When you first open the graph you will be asked to pick the field that you would like to display on the x axis and the field that you would like to group the data by Once you have chosen the appropriate fields and clicked the lt Select gt button the graph will be displayed i spiraTeam S My Page Project Home Planning Reporting gt Tasks Summary lt lt Back to Reports Home Task Graphs Task Summary Task Velocity Task Bumup Task Burndown X Axis Priority x Grouped By Status m Tasks Summary Completed J In Progress W Not Started 3 Medium Welcome System Administrator My Profile Administration Log Out Library information System Role Project Owner In this version of the report the x axis represents the tasks priority and the individual bars are grouped by the status of task Each data value can be viewed by positioning the mouse pointer over the bar and a tooltip will pop up listing the actual data value Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 4 4 Task Velocity Chart The Task Velocity graph shows the total estimated and actual effort delivered in each project release and or iteration Welcome System Administrator My Profile Administration
222. the first fifteen entries will be shown Above this navigation list is a highlighted box that displays the list of any workflow transitions that the current user can execute on the incident This is described in more detail below In addition to the left hand navigation you can enter a specific incident number in the text box in the toolbar and click the lt Find gt button In the same toolbar there is also a shortcut for creating a new incident without having to first return to the incident list page In addition the lower section of the incident details page can be switched been four different views Resolution Custom Properties Attachments History and Associations These are described later 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 depend on how your project administrator has setup the system for you Administrators should refer to the SpiraTeam Administration Guide for details on configuring the incident workflows to meet their needs Depending on the user s role and whether they are listed as the owner or detector of the incident or not displayed in the left hand side of
223. the page above the navigation list is a set of allowed workflow operations gt Resolve Incident Status gt Assigned gt Unable to Reproduce gt Duplicate Incident These workflow transitions allow the user to move the incident from one status to another For example when the incident is in the Assigned status you will be given the options to gt Resolve the Incident changes status to Resolved gt Unable to Reproduce changes the status to Not Reproducible gt Duplicate Incident changes the status to Duplicate After changing the status of the incident by clicking on the workflow link you can then fill in the additional fields that are now enabled and or required Once you ve made the changes to the appropriate incident fields you can either click lt Save gt lt Save and Close gt or lt Save and New gt to commit the changes or lt Refresh gt to discard the changes and reload the incident from the database In addition you can print the current incident by clicking lt Print gt which will display a printable version of the page in a separate window 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
224. the project manager has assigned you to be responsible for either developing the supporting test cases or decomposing the requirement into its detailed work breakdown structure of project tasks The requirement name is displayed along with its status requested accepted in progress etc and its importance 3 2 4 My Assigned Test Cases 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 4 so that you can easily retest failed cases 3 2 5 My Assigned Test Sets This section lists all the test sets groups of 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
225. thod In Progress Fred Bloggs 1 0 0 0 0003 TK000028 ow fis Y rows per page id lt 4 Displaying page Ton ha of 1 gt dp NewTask 3 Delete y Refresh To filter the list by progress status priority owner or release you simply choose an item from the appropriate drop down list and for the other fields you enter a free text phrase then click lt Filter gt or press the lt ENTER gt key 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 task numbers To change the column that is sorted or to change the direction of the current sort simply click on the up down arrow icon in the appropriate column The currently sorted column is indicated by the larger white arrow with the back border In the screen shot above we have filtered on tasks that are finishing late sorted in order of decreasing priority Clicking on Filter gt Clear Filter removes any set filters and expands the incident list to display all incidents for the current project and clicking on Filter gt Save Filter allows you to save the filter to your My Page for use in the future The list of saved filters can also be retrieved by clicking Filter gt Retrieve Filter 8 1 2 New Task Clicking on the lt New Task gt button creates a new task in the grid with a
226. ties 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 Incidents Test Cases Test Runs Attachments 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 5 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 name of the test set if applicable 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 Cases Custom Props fest Runs Attachments mA
227. tion window the upper part of the right pane contains the task detailed information itself and the bottom part of the right pane displays different information associated with the task The navigation pane consists of a link that will take you back to the task list as well as a list of the other related tasks Depending on which page you came from this navigation list will be different gt If you arrived at the screen from the requirement details page the navigation pane will display the parent requirement together with a list of all the tasks that are associated with the requirement gt If you arrived at the screen from the release iteration details page the navigation pane will display the parent release iteration together with a list of all the tasks that are associated with the release iteration gt If you arrived at the screen from the main task list page the navigation pane will display a list of the other tasks that match the currently selected sort and filter option If the number of tasks exceeds fifteen only the first fifteen entries will be shown The top part of the right pane allows you to view and or edit the details of the particular task You can edit the various fields name description etc and once you are satisfied with them simply click either the lt Save gt or lt Save and New gt button at the top of the page to commit the changes In addition you can delete the current artifact by choosing lt Delete
228. 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 gt 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 Finally the tests are grouped into test sets so that they can be assigned to users in batches for execution and tracking However when migrating existing projects into SpiraTeam 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 Testing gt Test Cases link 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 Help My Page Project Home Planning Testing Tracking Reporting m spiraTeam Test Cases Test Sets dp insert 3 Delete gt Indent lt Outdent Q Refresh hedt Tools Show hide columns Y Fitter Display data for All Releases v rc Ermer Role Manager Displaying 9 out of 11 test case s for this release amp Functional Tests 5 Fred Bloggs z Ability to creat
229. ts Home Incident Graphs Summary Progress Rate Cumulative Count Open Count Aging Tumaround Time incident Type All x Date Interval Date Ending 10 19 2008 _ mid yyyy Incidents Turnaround Time 1 Critical 2 High 3 Medium 4 Low 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 Clicking on the Display Data Grid link will display the underlying data that is being used to generate the graph 11 4 Task Reports 11 4 1 Task Summary Report This report displays all of the tasks tracked for the current project The task s details are displayed ina summary list form Project 1 Library Information System Sample application that allows users to manage books authors and lending records for a typical branch library Task Name Description Status Priority Owned By Created On Last Modified Release Requirement Start Date End Date Complete Est Effort Actual Effort Write edition object Not 1 Fred 01 Dec 11 Mar 12 Mar n 3hours 0 _ 23 insert queries Started Critical Bloggs 2003 OHUeo20i3 10 0 0 003 RON 2004 2004 mins Develop edit author Not Joe P 01 Dec 07 Mar 08 Mar 8 hours 0 _ 2004 24 details screen Started Smith 2003 2004 mins 2 High 01 Dec 2003 1 0 0 0 0002 RQ15 0 Create author 25 object update method 26 Write author object Not update queries Started Refactor author 2
230. ts matrix to determine the complexity and associated resourcing Once the high level release schedule has been determined the requirements can then be prioritized and scheduled against the appropriate release according to their business priority Once the release is underway the requirements are further decomposed into their constituent low level project tasks that can be assigned to the project team The system will track the progress and revised estimates for the tasks and display them against the requirements so that risks to the schedule can be quickly determined 2 2 Test Case Management Spiraleam 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 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 r
231. ttons are displayed in the last column Welcome Fred Bloggs My Profile Log Out Help My Page Project Home gt spiraTeam Planning Testing Tracking Reporting Requirements Releases Iterations dp inset Delete gt indent lt p Outdent ShowLevel wv Retesh Ty Copy export Show hidecolumns Y Clear Fitters a Start Date End Date Plan Effort ae a aw Y _ ie FE Library System Release 1 1 0 0 0 1 Mar 2004 12 Mar 2004 216 0h RLO00001 A fLibrary System Release 1 SP1 Eg 1 0 1 0 EJ 3 13 2004 ED 3 30 2004 EA EN 176 0h B Library System Release 1 SP2 352 0h Role Manager No Tasks 4 1 2004 S E iteration 001 E iteration 002 E iteration 003 3 Library System Release 1 1 a Library System Release 1 1 SP1 a Library System Release 1 1 SP2 2 iteration 001 E iteration 002 2 iteration 003 lie Library System Release 2005 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 1 1 0 0 1 1 1 0 1 1 2 0 1 1 0 0 0001 1 1 0 0 0002 1 1 0 0 0003 1 2 0 0 2 2z z Glo at a 1 Mar 2004 5 Mar 2004 9 Mar 2004 15 Oct 2004 1 Nov 2004 1 Dec 2004 15 Oct 2004 19 Oct 2004 24 Oct 2004 1 Apr 2005 4 Mar 2004 8 Mar 2004 12 Mar 2004 27 Oct 2004 30 Nov 2004 31 Dec 2004 18 Oct 2004 23 Oct 2004 27 Oct 2004 2 Apr 2005 96 0h 24 0h 72 0h 168 0h 336 0h 320 0h 24 0h 72 0h 72 0h 16 0h RLO00008 RLO00009 RLO00010 RLO00004 RL000005 RL000007 RL000017 RL000
232. ty Task Bumup Task Burndown Display data for 1 0 0 0 Library System Release 1 Tasks Burnup E On schedule E Late Finishing Late Starting Not Started 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 The y axis of the graph displays the cumulative increase in work for the project broken down by progress on schedule late finishing later starting or not started and the x axis can be configured to display three different levels of granularity gt All Releases This shows the increase in work for each of the releases in the project gt Specific Release This shows the increase in work for each of the iterations in the selected release gt Specific Iteration This shows the increase in work for each working day in the date range covered by the selected iteration 11 4 6 Task Burndown Chart The Task Burndown graph shows the remaining work that needs to be done for each release iteration in the project a Welcome System Administrator My Profile Administration Log Out Lbrary information System spiraTeam My Page Project Home Planning Testing Reporting gt Tasks Burndown Role Project Owner m Task Graphs Task Summary Task Velocity Task Burnup Task Burndown Display data for 1 0 0 0 Library System Release 1 x Tasks Burndown C Remaining Ettort 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 The y axis of the graph displays the total remaining work that needs to be done
233. un Count Requirements Coverage View Details apriete 9 gt 12 3 2003 3 gt 12 2 2003 2 gt 12 1 2003 11 Failed Passed Not Run Blocked Caution i Passed Failed Blocked Caution Not Run Not Covered Release Test Summary View Details Release Iteration Tests Execution Status Release Task Progress view Details 1 0 0 0 Library System Release 1 I Fiskcane lescalion Tesks Est Actual Task Progress 1 0 1 0 Library System Release 1 SP1 7 T 1 0 0 0 Library System Release 1 18 94 0h 935h 0 1 0 20 Library System Release 1 SP2 co 1 0 1 0 Library System Release 1 SP1 0 z z No Tasks 1 1 0 0 Library System Release 1 1 2 1 020 Library System Release 1 SP2 0 No Tasks 1 1 1 0 Library System Release 1 1 SP1 T BD 1 1 0 0 Library System Release 1 1 18 86 0h 3857h ME G1 1 2 0 0 Library System Release 2005 1 1 1 0 Library System Release 1 1 SP1 0 7 No Tasks T 1 2 0 0 Library System Release 2005 3 10 0h 95h M Incident Summary View Details Displaying for incident Type A Y Late Finishing Tasks view Al Status 1 Critical 2 High 3 Medium 4 Low None TOTAL Name Owner Progress End Date Sasa Z Create edition object insert method Fred Bloggs 12 Mar 2004 Duplicate 2 1 3 6 Z Develop new edition entry screen Fred Bloggs E 12 Mar 2004 New 3 3 Z Write author object delete query Fred Bloggs E 10 Mar 2004 Not Reproducible i p 1 Z Create author object delete method F
234. v Requirement Name _CsTTest Coverage Task Progress Importance Status Req Edit ee A a peT ET So E lt Ra Filter Functional System Requirements Not Covered In Progress RQ000001 gt Edit In Progress RQ000002 gt Edit Completed RQ000003 gt Edit Completed Moderate RQ000004 PEt Completed RQ000005 Edit Completed RQ000006 Pen Completed RQ000007 Edit Completed RaQ000008 reat Completed RQ000009 Edit Completed RQ000010 PEt In Progress RQ000011 Edit a Author Management Not Covered In Progress RQ000013 gt Edit Subject Management Not Covered Planned RQ000019 gt Edit amp D Administration Functions Not Covered No Tasks Requested RQ000022 Edit Show rows per page 4 lt Displaying page fi of 1 gt gt 4 Online Library Management System Not Covered amp Book Management ual Ability to add new books to the system T i Ability to edit existing books in the system T L Ability to delete existing books in the system Pe L Ability to associate books with different subjects 3 ial Ability to associate books with different authors L Ability to associate books with different editions ial Ability to completely erase all books stored in th D Edition Management Not Covered OOOO00K 00000 0000700 dp insert 3 Delete gt Indent lt p Outdent The requirements list consists of a hierar
235. vailable 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 diagrams illustrates the relationships between the different artifacts and entities Figure 1 The main entities that comprise a SpiraTest project Figure 2 The relationships between the various SpiraTest entities With these overall concepts in mind the rest of this help manual will outline the functionality in each of the Spiraleam screens and provide specific information on how to manage each of the artifacts illustrated above Note that this manual does not explain the Administration level functionality of the system for that please refer to the SpiraTeam Administration Guide 2 7 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 SpiralTeam uses a system of two letter prefixes which help identify the type of artifact being displayed The current prefixes used by the system are Projet PR Project Group incident Type Requirement Ra ncident Priority Inci i IV acident Severity IV Workflow Test Step Workflow Transition In addition certain artifacts in the system are
236. verage 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 can edit the various fields name description etc and once you are satisfied with them simply click either the lt Save gt or lt Save and News gt button at the top of the page to commit the changes In addition you can delete the current artifact by choosing lt Delete gt discard any changes made by clicking lt Refresh gt or print it by clicking lt Print gt In addition the bottom part of the right pane can be switched between six views Test Coverage Tasks Custom Properties Attachments History and Associations 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 Props Attachments Available Test Cases Test Coverage O amp G Functional Tests TC000002 4 Ability to create new book z Ability to create new book C TC000008 2 Book management z Ability to edit existing book TC000013 24 Adding new book and author to Not Run z Ability to create new author z Ability to edit existing autho z Ability to reassign book to di amp G Regression Tests O G Scenario Te
237. ween the destination releases iterations will change as the icon is dragged over it to illustrate where it will be inserted Welcome System Administrator My Profile Administration Log Out Library information System Help Wi spiraTeam My Page Project Home Planning Testing Tracking Reporting Requirements Releases Iterations dh insert 3 Delete 2 indent lt gt Outdent I a Role Project Owner Y Clear Fitters End Date PlanEffort Task ffort Release Id Co C oC def Show hide columns Show Level 2 Refresh Th Copy amp Export 5 Library System Release 1 G Library System Release 1 SP1 aG Library System Release 1 SP2 8 iteration 001 8 iteration 002 et Iteration 003 gt J Library System Release 1 SP2 coray Syste Blegse S 2 Iteration 001 E iteration 002 iteration 003 0000000000000 1 0 0 0 1 0 1 0 1 0 2 0 1 0 0 0 0001 1 0 0 0 0002 1 0 0 0 0003 1 1 0 0 1 1 1 0 1 1 2 0 1 1 0 0 0001 1 1 0 0 0002 1 1 0 0 0003 1 2 0 0 N ete NO esis No Tests No Tasks No Tasks l amp w amp 1 Mar 2004 13 Mar 2004 1 Apr 2004 41 Mar 2004 5 Mar 2004 9 Mar 2004 15 Oct 2004 1 Nov 2004 1 Dec 2004 15 Oct 2004 19 Oct 2004 24 Oct 2004 1 Apr 2005 12 Mar 2004 30 Mar 2004 30 Apr 2004 4 Mar 2004 8 Mar 2004 12 Mar 2004 27 Oct 2004 30 Nov 2004 31 Dec 2004 18 Oct 2004 23 Oct 2004 27 Oct 2004 2 Apr 2005 216 0h 176 0h 352 0h 96 0h
238. you can click on the fill icon to the right of the editable item which will propagate the new value to all editable items in the same 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 Alternatively pressing the lt ENTER gt key will commit the changes and pressing the lt ESCAPE gt key will cancel the changes 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 filter the list of requirements as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out My Page Project Home Planning spiraTeam Requirements Releases Iterations Role Manager 3 Delete indent lt Outdent Refresh Theat export Show hidecolumns Y Fiter a am Y recone v aw v aw T nof erie RQ000001 RQ000002 T Functional System Requirements Not Covered In Progress 1 Online Library Management System Not Covered In Progress Author Management Not Covered In Progress RQ000013 5 Ability to link authors to the
239. ys the name of the test case together with the requirements coverage information for the test case in question Test Steps teq Coverage Custom Props Test Runs Attachments History Available Requirements Requirements Coverage CO amp Functional System Requirements amp l Yy Completed atus E E Online Library Management Syst E El Book Management rie Ability to add new books to th T Ability to edit existing books ri Ability to delete existing boo Abil ity to associate books wit l 5 Ahilitw ta accnarmiato hank wat 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 The pane consists of two lists of requirements the one on the left being the complete hierarchical list of requirements in the project The right box which will initially be empty contains the list of requirements mapped to this test case The requirements in this box include columns for their ID name and status Hovering the mouse over the names of the requirements in either box will display a tooltip consisting of the requirement name place in the hierarchical structure and a detailed description Clicking on the hyperlinks in
240. ystem Release 1 1 SP1 No Tasks 1 2 0 0 Library System Release 2005 E o5h D Each release will display the aggregate progress of any tasks directly assigned to itself together with the task progress of any child iterations that are contained within the Release Clicking on one of the releases will drill you down one level further and display the task progress for the parent release as well as each of the child iterations separately Release Task Progress vien Release Iteration ash st Actual Task Progress 1 0 0 0 Library System Release 1 1o 93 5h E 1 0 0 0 0001 Iteration 001 32 3h E 1 0 0 0 0002 Iteration 002 5 31 2h EJ 1 0 0 0 0003 Iteration 003 30 0h 3 4 11 Late Finishing Tasks This section displays the list of any project tasks that have not yet been completed but whose scheduled end date has already elapsed A graphical progress bar is included with each task in the grid so that you can easily see which tasks are nearest completion 3 4 12 Late Starting Tasks This section displays the list of any project tasks that have not yet started but whose scheduled start date has already elapsed Each task is listed along with its owner priority and due date so that you quickly ascertain how many days late it will be starting how important it is to the project and who needs to be contacted to get more information 3 4 13 Requirements Regression Coverage This section consists of a bar graph that display
241. ystem makes the following changes to the task automatically gt The release iteration that the task is assigned to is updated gt The start date and end date of the task is changed to match that of the iteration if the dates lie outside the bounds of the iteration This means that the task may change from being on schedule to late starting depending on whether the iteration is already in progress 7 3 4 Editing the Task Incident List As well as being able to schedule the incidents and tasks with the various iterations in the upper portion of the screen the incident and task lists displayed on the bottom half of the screen include the same editing functions found in the Task List page and the Incident List page You can insert edit delete filter sort and change the displayed columns for the lists For more details see section 6 1 for the Incident List and section 8 1 for the Task List 8 Task Tracking 8 1 Task List When you click on the Tracking gt Tasks global navigation link you will initially be taken to the tasks list screen illustrated below spiraTeam Project Home Planning Tracking incidents Tasks dp New Task 3 Delete Refresh J Copy export Show hidecolumns Y Filter Displaying 16 30 out of 43 task s for this project Not Started Not Started Not Started In Progress Z Write author object update quenes Z Refactor author screen to include delete button Z Write edition

Download Pdf Manuals

Related Search

Related Contents

PGPS Manual 3D-1 - PRO    Édition 2014 - Communauté de Communes de la Rive Gauche du  3. Dans - Support  Hands-On-SDR    環境装置① - 日本産業機械工業会  取扱説明書 - シャープ    Mode d`emploi pour demander un raccordement photovoltaïque de  

Copyright © All rights reserved. Failed to retrieve file