Home

SpiraTest v1.0.2 User Manual

Contents

1. ew Copynght C 2006 infect Corporation Speatest v1 0 inflectra The screen is divided up into three main elements gt The top navigation bar with a gray background contains a link back to the test case list together with the navigation that allows you to move between the different test cases being executed You can either directly select the test case from the drop down list and click lt Select gt or use the movement buttons that look like the buttons on a music player from left to right they move to first move to previous move to next and move to last test case Regardless of the method chosen when the test case is changed the list of test steps available in the left hand pane is refreshed gt The left hand navigation pane contains the list of test steps for the currently executing test case You can click on the test step link to move between the test steps in the current test case In addition each test step has a colored square next to the name that indicates its status green Passed red Failed gray Not Run in the current test run The overall test case also has an execution status If any of the steps are marked as Failed then the overall test case Failed if 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
2. 2 1 Requirements Management SpiraTest provides the ability to create edit and delete project scope requirements in a hierarchical organization that resembles a typical scope matrix Each requirement is associated with a particular importance level ranging from critical to low and a status identifier that designates where the requirement is in the development lifecycle requested planned in progress and completed In addition each requirement is mapped to one or more test cases that can be used to validate that the functionality works as expected This mapping is called the Requirement Test Coverage since the test cases cover the requirement so that if all the tests can be executed successfully then the requirement is validated 2 2 Test Management SpiraTest provides the ability to create edit and delete project test cases that are stored ina hierarchical folder structure that resembles Windows Explorer Each test case consists of a set of test steps that represent the individual actions a user must take to complete the test These test steps also contain a description of the expected result and any sample data elements that the tester should use when performing the action When a user executes a test case the results are stored in a test run that contains the success failure status of each test step as well as the actual observed result that the tester experienced In addition each test case is mapped to on
3. however my changing the drop down list to a specific incident type e g bug enhancement issue etc the project manager can filter the summary table to just items of that type 3 4 8 Test Execution Status This section consists of a bar graph that displays the aggregated count of test cases in each execution status for the project Note that this graph does not consider past test runs when calculating the totals in each status Passed Failed or Not Run it simply looks at each test case and uses the last run status as the best health indicator Thus if a test case that previously passed has subsequently failed upon re execution it will be considered a failure only If you position the mouse pointer over any of the three bars the color of the bar changes slightly and the underlying raw data is displayed as a tooltip together with the percentage equivalent Clicking on the View Details link at the top of the table simply brings up the project test case list see section 5 1 In addition to the bar chart there is a also a display of the total number of test runs recorded for the project and a list of the five most recent days of recorded test runs together with the daily count 3 5 My Profile When you click on either the My Profile link in the global navigation you will be taken to the page in the system that allows you to view and edit your personal profile eicome Fired Biegga My Profile og Okt T e spi
4. lt New Incident gt button takes you to the new incident screen This is essentially the same screen as the incident details screen shown in section 6 2 except that the lt Update gt button is replaced by an lt Insert gt button and some of the fields are disabled type status owner since all incidents are initially created as type incident and status new 6 1 3 Delete Clicking on the lt Delete gt button deletes the incidents whose check boxes have been selected in the incident list 6 1 4 Clear Filters Clicking on the lt Clear Filters gt button removes any set filters and expands the incident list to display all incidents for the current project 6 1 5 Refresh Clicking on the lt Refresh gt button simply reloads the list of incidents this is useful when new incidents are being added by other users and you want to make sure you have the most up to date list displayed 6 1 6 Edit Each incident in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information This is useful for making simple changes to an incident it avoids having to first go to the incide
5. 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 button this is illustrated in the screen shot below N s Welcome Fred Blogga My Profle Log Qui spiraTest al Library nbormation Saleen gt Tee Casni Teel Coase Execibon ee Back to Test Lisi Curent Test Case Abdity to create new author a sa m m BE Ability to creato naw author Plasse follow the directions outlined ia the box below Ws ooo Taer clicks link to Clare Buthor W Step OW Stes 000 CI Step ses Expected Raoul Stes 0005 Uae taken te Firat screen ia wifes Please enter the seban test rasul d it defers ihan chck the appropriate butbors Acia Resu E Log an incident tor thee Hep The screen displays a 404 error page Name Create Author Page Miter Copyright Cp 2006 intectra Cospesation Srinat wi n inflectra Unlike the lt Pass gt button if you don t enter a description of the actual result the system will display an error message and re prompt you again for input In the case of a failure both the individual test step and the overall test case will be marked with a red square containing a cross You will now have the option of moving to the next test step by clicking the lt Next Test gt button if it is the last test case being executed the l
6. light yellow background and the screen will prompt you to choose the destination for the copy move Welcome Fred Bloggs My Profile Log Out Incidents Role Manager Ch copy OChMowe Refresh Y Clear Fiters ay l B Functional System Requirements Fred Bloggs Online Library Management System Fred Bloggs Completed Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs ooooos Fred Bloggs oooo07 Fred Bloggs Oo000s iT Completed iE tf Completed EEEEEE Completed tf Completed PT i ft n Completed Bawa Book Management Ability to add new books to the system Abily to edit existing books in the system Aldy to delete existing books in ihe 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 th Edition Management amp Author Management H Subject Management H Administration Functions hnst Delete gt indent eh uident Completed Completed In Progress In Progress Planned Requested Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith ooo0og o00010 e 000011 000073 o00013 Choose the destination location for the copied moved requirements by selecting the checkbox of the requirement you want to copy move in front of and then clicking the Copy Requirements or Move Requirements link If you want to copy move t
7. lt Update gt button at the bottom right of the screen If you want to discard the changes you have made simply click either the lt Cancel gt button or the Back to Test List link and you will be returned to the Test Case List page 5 3 Execute Test Case s When you select test cases on the test case list page and click the lt Execute gt button or click the Execute link on the test cases listed under My Tests on your personalized home page you are launching the test execution module with the selected test cases This section describes how a tester can follow the steps defined for a series of test cases and record what actually happened in the process In addition recorded failures of test cases can be used to automatically generate new incidents that will be added to the incident tracking module see section 6 Regardless of the route taken to launch the test execution module the screen that will be displayed will look like the following Welker Fred Boggs fie Poefile Leg Gut spiraTest 2 Bock to Test List Curent Test Case Abihty to create new book oa a o gt m Ability to croaie new book Flaga dsllery the destana gullin off the Bete Eia Sinp 0001 Weer lcge im to application Bien Oi mip OOS Sei Expected Result Siap iHi Daer tAken TO MAID BEMI SOTEEN Please mie h acha lest remat fa defers then click the appropriate bution Actual Regul C Log an incident for this step
8. of the current test step for the current test case As the tester you would read the description of the test step carry out the instructions on the system you are testing and then compare the results with those listed as expected As described below depending on how the actual system responds you will use the buttons on the page to record what actually happened If the expected results are indeed observed then you simply need to click the lt Pass gt button to mark the test step as passed and advance to the next test step This is illustrated in the screen shot below Welcome Feed Biegga biy Profle Leg Cul spiraTest Tow Comirt Librar Inforrmaiban Saaiem gt Tea Cos Dow Caan Execution se Bock t Ten Lind Current Test Case Abdty to create new book Select pa a 1 i M Ability to create mow book Pigusa follow the directions outhned in the box below Zz Step Gh mex Clicks submit button We Sten oo E Stee ra Step ood Expected Me Stop Diti Confirmation Screen is displayed Please aniar the actual test resul ft dhea then chek the aporcorte batti Actual Reauh O Log an incident for this step Copyright C 2006 infectra Conporation SperaTest v1 0 in flectra 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
9. projects users requirements tests etc To aid in understanding how the information is related the following diagram illustrates the relationships between the different artifacts and entities Test Step O a 2 6 Application Site Map The following diagram illustrates overall application site map and how a user can navigate from one page to another Project Home La Test Coase Details With these overall concepts in mind the rest of this help manual will outline the functionality in each of the SpiraTest screens and provide specific information on how to manage each of the artifacts illustrated above Note that this manual does not explain the Administration level functionality of the system for that please refer to the SpiraTest Administration Guide 3 User Project Management This section outlines how you can log into SpiraTest view your personalized home page that lists the key tasks that you need to focus on and drill down into each of your assigned projects in a single dashboard view In addition to your personal homepage each of your projects has its own dashboard that depicts the overall project health and status in a single comprehensive view 3 1 Login Screen Upon entering the SpiraTest URL provided by your system administrator into your browser you will see the following login screen a Please enter your user name Welcome to and password then click the log in button a Us
10. 000011 e Hoon oo0013 E inflectraZ The test case list consists of a hierarchical arrangement of the various test folders and test cases that the system being developed needs to be able to demonstrate The structure is very similar to the folder structure in Microsoft Windows Explorer and users will find this very familiar and intuitive to use When you create a new project this list will initially be empty and you will have to use the lt New Folder gt and lt New Test gt buttons to start adding test cases to the system The list consists of test folders shown with a folder icon and in bold type and test cases that are shown with a document icon and a hyperlink You can nest test folders and test cases under an existing test folder but you cannot nest anything under a test case All of the items in the list have a name together with the most recent execution status passed failed or not run and owner author execution date creation date and test case number In addition if you position the mouse pointer over the name of the test case folder a more detailed description is displayed as a tooltip Clicking on a test case s hyperlink will take you to the test case details page for the item in question see section 5 2 It is important to understand that only test cases are assigned a status themselves the test folders simply display an aggregate of the worst case assessment of their children s status Also only test
11. 03 e 000019 000022 f cp insert Delete o gt indem h Outdent Copyright C 2006 2007 Inflectra Corporation SpiraTest v1 0 2 inflectraZ The requirements list consists of a hierarchical arrangement of the various requirements and functionalities that need to be provided by the system in question The structure is very similar to the Work Breakdown Structure WBS developed in Microsoft Project and users of that software package will find this very familiar to use When you create a new project this list will initially be empty and you will have to start using the lt Insert gt button to start adding requirements Requirements come in two main flavors summary items shown in bold type and detail items shown in normal type with a hyperlink When you indent a requirement under an existing requirement the parent is changed from a detail item to a summary item and when you outdent a child item its parent will return to a detail item assuming it has no other children This behavior is important to understand as only detail items are assigned a status themselves the summary items simply display an aggregate of the worst case assessment of their children s status Also only detail items can be mapped against test cases for test coverage thus only they have hyperlinks the summary items simply display an aggregate coverage status of their children Each requirement is displayed along with its importance prior
12. 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 Profile Log Gut Choose Project gt My Page Project Home 9 Requirements Tesi Cases spiraTest a My Page gt Fred Bloggs Project Name Web Site Creation Date crip Project Type Priarity Date Opened Library Information System waew libraryinformationsystem ong 11 Dec 2005 Ability to associa iple a Library Information System Enhancement Tema 17 Mow 2003 Sample Application Ome www Jempun on 1 Dec 2005 Library Information System Limitation 4 Dec 2003 Sample Application Two 14 Dec 2005 Test Training Item Library Information System Training 3 Dec 2003 Editing the date on a book ig clunky Library Information System Bug 2 High 4 Mow 2003 Test Training ltem Library Information System Training 3 Dec 2003 Name Project Status Last Executed Test Change Request Library Information System Change Request rao 7 Dec 2003 Ability to create new book Library Information pem 1 Dec 2003 Abslity to impon data
13. Low None TOTAL ew 3 3 Open 2 d 15 Assigned Fixed Closed Moi Reproducible Duplecate Failed Nat Run Not Covered TOTAL Requirement Incident Count Open Total Total Runs Functional System Requirements Daily Run Count Online Library Management System gt 12 1 2003 8 Book Management Ability to add mew books to th Ability to associate books with diferent subjects ebay io associate books mith different aditiona Failed Not Run Ability to completely erase all books stored in the system with one click Edition Management Author Management Ability to add new authors to the system Subject Management Administration Functions Data Import Functionality Ability lo create new users in ihe system TOTAL 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 Each of the sections that make up the homepage is described below 3 4 1 Project Overview This section displays the name of the project together with a brief description the web site that points to any additional information about the project the names of the owners of the project and a link to the all available r
14. Not Run Joe P Smith Joe P Smith 41 Dec 2003 000010 B amp Exception Scenario Tests Not Run Joe P Smith Joe P Smith 1 Dec 2003 000011 T Person loses book and needs to report loss Met Run Joe P Smith 11 Dec 2003 Oooo Joe P Sraith 14 Dec 2003 000013 epe iee ie pge ie e e e T Adding new book and author to library Not Run db NewTest ch NewFolter 3 Delete gt Execute Copyright C 2006 2007 Inflectra Corporation SpiraTest v1 0 2 i nflectraZ Choose the destination location for the copied moved test cases folders by selecting the checkbox of the test case folder you want to copy move in front of and then clicking the Copy Test Cases or Move Test Cases link If you want to copy move the test cases folders to the end of the list you just click the link without selecting a destination To abort the copy or move all you need to do is click the Cancel link and the operation will be aborted Note that copied test cases folders will also include the requirements coverage and test step information from the Originals 5 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 fy Profile Log Out Library efor Sy Help spiraTest Library Information System gt Test Cases gt Test Case Details Role Manager lt lt Back to Test List Rr insertStep 3 Delete q Move Up Move Down R
15. Rater Test Case Ability to create new book View Test Steps View Test Runs C View Coverage spiraTest 1 Dec 2003 Abiity to coaie nea book Fred Bloggs PDec 2003 Ability to orale nee book Joe F Smah Copyrigh 0 AS infect Comoration SpraTest wii inflectraz When you click on any of the individual test runs in the list you are taken to the Test Run details page not to be confused with the Test Case details page This page lists all the steps of the test case as they appeared during the test run in question this means that if the test steps were changed after running the test the list here will reflect the original information Welcome Fred Bloggs fy Profile Log Cut spiraTest Teal C aiaa Libary Information System gt Toe Casos Tosi Hun Details ze fack fo Test Run Lisi Test Case Abiity lo create mew book Tem Aun 2209 Execution Date 1 Dec 2003 wap aili pete Postal Ghigi User logs in io apphcation User takan bo main menu acmon Deh User cliches ink io create book User baken bo frst screen ii wizard OOOO Leer anthers becky mit bed guii Laer taken bo nent screen Miscbeth Vidhan Aa eon pga i dipplayed Tha duch objeti of wih Block ihan clock Mest ii wead Shakeigenare varable M lee df gt Vie ana Copyright C 2006 Infiectrs Corporation SpiraTest v1 0 inflectra Each test step is displayed along with the description expected result suggested sample data actual result and the ex
16. aan SoraTest v1 0 in flectra This page is made up of two areas the left pane is the navigation window and the right pane contains the requirements test coverage information The navigation pane consists of a link that will take you back to the requirements list as well as a list of the peer requirements to the one selected This latter list is useful as a navigation shortcut you can quickly view the coverage information of all the peer requirements by clicking on the navigation links without having to first return to the requirements list page The main right pane contains the test coverage information for the requirement in question The pane consists of two lists of test cases the one on the left being the hierarchical list of the test cases belonging to the project arranged in test folders denoted by their gray color The right box which will initially be empty contains the list of test cases mapped to this requirement The test cases in this box are color coded according to their most recent execution status red for failed green for passed and gray for not run Double clicking on items in this box will jump you to the test case details screen for this test case see section 5 2 9 To change the coverage for this requirement you use the buttons Add Remove Remove All positioned between the two list boxes The lt Add gt button will move the selected test cases from the list of available on the left to the list of mapped on
17. ally fixing the problem whereas for other incident types e g training item it may mean simply documenting a workaround In either event this section highlights the open incidents you need to manage ranked by importance priority and categorized by type with the open date displayed to give you a sense of the age of the incident Clicking on the incident name hyperlink takes you to the incident details page see section 6 2 that describes the incident in more detail and allows you to add new information or change its status to indicate actions taken In addition if you position the mouse pointer over the name of the incident a more detailed description is displayed as a tooltip 3 3 Global Navigation Regardless of the page you are on SpiraTest will always display the global navigation bar consisting of five section tabs My Page Project Home Requirements Test Cases and Incidents that correspond to the five main parts of the system as well as three secondary links to My Profile and Log Out and Help Each of the main sections is described separately in this manual however it is worth noting that the section you re currently accessing will always be displayed in a darker color blue that matches the horizontal bar The main tabs will take you to the appropriate artifact type requirement test case incident etc for the currently selected project However if you haven t selected a project then clicking on a
18. and status by the project manager Note that the mandatory fields are listed in bold type with asterisks Once you ve filled out the appropriate incident fields you can either click lt Insert gt to commit the new item or lt Cancel gt to discard the insertion and return back to the incident list 6 3 Incident Discovery Report When you click on the Incident Discovery Rate report from the Project Home dashboard see section 3 4 1 you will be taken to the incident discovery report for that project The incident discovery report displays the total number of incidents created and closed over a particular date range The report can either be displayed for the past 60 days of data daily or for the past 12 months of data weekly The screen shot below illustrates the discovery report loaded with the past 60 days of incident discovery closure data depicted on a daily basis iaar Inama pen x Proja I Hamia peter Urai ELLK E as ihack to Project Home Last G0 Days of Data Daly Lasi 12 Months of Data Veekly Incident Discovery Rate Report Daces Closed ma J 1 z AAAA D Pre OG GOST HP POO DE POGO 0G G ph Ase i a es TD te amaa Copynght C 2006 Infecira Conporation SpuraTest vii inflectra In this version of the report the y axis represents the number of incidents either created or closed in a 24 hour period and the x axis represents a specific day in the time span Each data point can be viewed by positionin
19. ate new users in the system Ability to modify existing users in the system f Project Home Test Cases Th Copy hhe Requested Requested Requested Requested Requested Requested Requested Welcome Fred Bloggs My Profile Log Qut Lbr information System Refresh Y Clear Filters Joe P Smith Joe P Smith Joe P Smih Joe P Smith Joe P Smith Joe P Smith Joe F Smith 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 Role Manager 3 Delete gt indent p Outdeni Copyright C 2006 2007 Inflectra Comoration Spiralest v1 0 2 inflectraZ To filter the list by importance status test coverage or author name you simply choose an item from the appropriate drop down list and for the other fields you enter a free text phrase then click lt Filter gt to apply the different filters Note that the name field is searched using a LIKE comparison so that searching for database would include any item with the word database in the name The other freetext fields need to be exact matches e g dates requirement numbers In the screen shot above we are filtering on Status Requested 4 1 9 Copying and Moving To copy or move a requirement or set of requirements simply select the check boxes of the requirements you want to copy or move and then click either lt Copy gt or lt Move gt as appropriate Upon clicking the button the rows you selected will be marked in bold with a
20. can used to manage key project artifacts during the software development lifecycle Although the primary purpose of the incident tracker is to manage the defects raised during the execution of test cases in the test management module it is also a powerful risk issue bug tracking system in its own right When coupled with the project dashboard see section 3 4 it is a powerful tool for representing all the key risks and issues associated with a project in a single graphical format Unlike a standalone bug issue tracking tool however you can trace the incidents defects back to the test case and the underlying requirement that generated them giving the project manager unprecedented power in analyzing the in process quality of a system during its lifecycle This power is clearly illustrated in the Requirement Incident Count pane in the Project Home dashboard see section 3 4 4 6 1 Incident List When you click on the Incidents tab on the global navigation bar you will initially be taken to the incidents list screen illustrated below Welcome Fred Bloggs My Profile Log Out Libre information System Project Horne i Tes Cases spiraTest Library Information System gt Incidents dh New Incident Delete T Gear Fites Gh Refresh eT D 55 A 60 A 6 ri S i 55 Fi 56 Risk Risk Risk Change Request Change Request Change Request Change Request Change Request Change Request Change Request O
21. cases can be mapped against requirements for test coverage or have lists of associated test steps 5 1 1 New Test Clicking on the lt New Test gt button inserts a test case above the currently selected test case i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a new test case below an existing test case you need to select the test folder below it If you insert a new test case without first selected an existing item from the list the new test case will simply be inserted at the end of the list Once the new test case has been inserted the item is switched to Edit mode so that you can rename the default name and choose an owner and or author Note that all new test cases are initially set with an execution status of Not Run 5 1 2 New Folder Clicking on the lt New Folder gt button inserts a test folder above the currently selected test folder i e the one whose check box has been selected at the same level in the hierarchy The new folder is automatically populated with a single default test case If you want to insert a new test folder below an existing test folder you need to select the test folder below it If you insert a new test folder without first selected an existing item from the list the new test folder will simply be inserted at the end of the list of test folders but before any of the test cases Note that in a test folder all of the child test fo
22. e or more requirements that the test is effectively validating providing the test coverage for the requirement During the execution of the test case each failure can be optionally used to record a new incident which can then be managed in the incident tracking module see below This provides complete traceability from a recorded incident to the underlying requirement that was not satisfied 2 3 Incident Tracking SpiraTest provides the ability to create edit assign track manage and close incidents that are raised during the testing of the software system under development These incidents can be categorized into bugs enhancements issues training items limitations change requests and risks and each type has its own specific workflow and business rules Typically each incident is raised initially as a New item of type Incident Following the review by the project manager and customer they are changed to one of the other specific types given a priority critical high medium or low and status changed to Open Once it is assigned to a developer for fixing it is changed to status Assigned The developer now works to correct the incident after which time its status changes to Fixed or Not Reproducible depending on the actions taken or not taken Finally the project manager and customer verify that it has indeed been fixed and the status is changed to Closed SpiraTest provides robust
23. e 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 3 2 2 My Tests This section lists all the test cases you have been made owner of across all the different projects you are a member of This typically means that the project manager has assigned you to be responsible for executing the assigned test scripts To aid in this process the script name is displayed along with its last execution status failed passed or not run and date of last execution This enables you to see how recently the tests have been run and whether they need to be re run If you click on the test name hyperlink you will be taken to the details page for this test case see section 5 2 and the project that the test case belongs to will be made your current project If you click on the Execute link listed in parenthesis it will actually launch the test case in the test case execution module see section 5 3 so that you can easily retest failed cases 3 2 3 My Open Incidents This section lists all the incidents you have been made owner of across all the different projects you are a member of This typically means that the project manager has assigned you to be responsible for resolving the incident In the case of a bug this can mean actu
24. eate your account In addition the system will prevent you logging on to the system with the same username at the same time on multiple computers This is to avoid the system getting confused by a user trying to make contradictory actions at the same time If for any reason you do try and log in to the system when you already have an active session in progress you will see the following screen Welcome to ee spiraTest gt You can either Log Out and try a differant user name or Sign Of The Other ations to force the other Version v1 0 eet locations to log out Copynght C 2006 Inflectra Corporation inflectra You have two choices you can either click the Log Out link and try logging in as a different user or if you want to log off any other active sessions e g you closed the browser and the session is still listed as active simply click the Sign Off The Other Locations link and you will be logged in to the application Since SpiraTest is licensed to organizations for a specific number of concurrent users unless they have purchased an unlimited Enterprise license only a fixed number of users may be active at the same time So for example if an organization has a five 5 concurrent user license and a sixth user tries to log in they will be presented with the following screen Welcome to spiraTest _ Return to Login page Version v1 0 Copyright C 2006 Inflectra
25. ecution status for this step in this particular test run Where the test step was listed as a Failure you will have an additional hyperlink View Incidents displayed This allows you to view any incidents that are associated with this particular test step failure S a Wal Fred Blagga bi Bighi Lea O spiraTest et n oat Carmi Libary Iniormaion Sysiom osi Canses los Run Dotsiis 4 Back to Test Run List Test Case Abiity to create new book Test Run E DHI Execution Date 1Dec 209 000007 User logs Use taken l man manu Bip Doit Usor clicks link to create book Use taken to fred screen in are e lihen chika Meni A yarad Shakespeare incidomis List for Stop 00007 Test Run Stop E 204003 Cannot add a naw book io the system at Haja pajam Liaj Copyeght C 2006 infectra Comporation SpiraTesi vi inflectra Clicking on the link will change the background color of the test case to gray and display a list of all the associated test steps in a grid below the test step list Each of the incidents listed will reflect the most up to date information regarding that incident including its type status priority name assigned owner detection date and who first detected it Clicking on the incident number hyperlink will take you to the details page for that incident which is described in section 6 2 6 Incident Tracking This section outlines how the incident defect tracking features of SpiraTest
26. efresh amp Functional Tests Test Case Ability to create new book T Ability to create new book View Test Steps View Test Runs View Coverage 7 shies tn sol sesira becs Sample Data Status T Ability Ability pate new auth T Ability to edi eoosting aulhor T abilit uen a ad oe O eee book eer laken to katsena in wizard n Passed Oo 0003 User enters books name and author then clicks N User taken to next screen in wizard Macbeth William Shake cae User chooses book s genre and sub genre from li User sees screen displaying all entered i Play Tragedy O 000005 User clicks submit bution Conhirmaton screen is displayed Eas Passed Hew Mew Mew Mew Copyright 0 2006 2007 Inflactra Corporation SpiaTest vi 0 2 This page is made up of two areas the left pane is the navigation window and the right pane contains the test case detailed information itself The navigation pane consists of a link that will take you back to the test case list as well as a list of the peer test case to the one selected This latter list is useful as a navigation shortcut you can quickly view the detailed information of all the peer test cases by clicking on the navigation links without having to first return to the test cases list page The main right pane can be switched between three different
27. ely related to the screen you happened to be on when you clicked the Help link 3 3 3 Choose Project Choosing a project from the list of your assigned projects in the drop down menu allows you to quickly and easily jump between projects regardless of the page you happen to be on When you choose a project you will be taken to the home page for that project which is described in section 3 4 below 3 4 Project Home When you click on either the Project Home tab or the name of the project in the My Page project list you will be taken to the homepage of the specific project in question Welcome Fred Bloggs My Profile Log Out Project Home Requirements Test Cases Incidents spiraTest Library Information System gt Project Home Role Manager Sample application that allows users to manage books authors and lending records for a typecal Description Priority Date Opened branch library Cannot install system on Windows ME 4 Dec 2003 rage System Administrator Administrator n Ability to be accessed by Mozilla Ag 11 Dec 2003 ai a Management of children s loans 1 Dec 2003 Reports Incident Decor bata System may require process changes 1 Dec 2003 Status 1 Critical 2 High 3 Medium 4 Description Priori Date Opened ae 2 2 Sampla Risk 1 1 Critical 10 Dec 2003 Planned 3 Sample Risk 2 2 High 10 Dec 2003 in Progess Sample Risk 3 4 Low 10 Dec 2003 Completed Status 1 Critical 2 Hig 3 Medium 4
28. eports for the project Currently the only report available is the Incident Discovery Rate report that is described in section 6 3 3 4 2 Requirements Summary This section consists of a Summary table that displays the aggregate count of requirements in the system broken down by importance on the x axis and status on the y axis This allow the project manager to determine how many critical vs low priority enhancements are waiting to be implemented vs actually being implemented In addition it makes a distinction between those requirements simply requested and those actually planned for implementation so the project manager can see what the backlog is between the customer s demands and the plan in place Clicking on the View Details link at the top of the table simply brings up the project requirements list see section 4 1 3 4 3 Requirements Coverage This section consists of a bar graph that displays the aggregated count of requirements test coverage for the project The Passed Failed and Not Run bars indicate the total count of requirements that have tests covering them allocated across the execution status of the covering tests For example if a requirement is covered by four tests two that have passed one that has failed and one that has not yet been run the counts would be passed 0 5 failed 0 25 and not run 0 25 These fractional quantities are then summed across all the requirements to give the execution statu
29. equirements scope matrix for a project and how you can map any existing test cases to the requirements Typically when starting a project developing the requirements list is the first activity after the Administrator has set up the project in the system 4 1 Requirements List When you click on the Requirements tab on the global navigation bar you will initially be taken to the requirements list screen illustrated below Welcome Fred Bloggs My Profile Log Out Role Manager C E Functional System Requirements E Online Library Management System Book Management Ability to add new books to the system y to edit existing books in the system ity te delete cisim books in the system Ability to completely erase all books stored in th Edition Management Author Management Subject Management E Administration Functions In Progress In Progress Completed Completed Completed Completed Completed Completed Completed Completed In Progress In Progress Planned Requested Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith 1 Dec 2003 1Dec 2003 71 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2004 11 Dec 2003 41 Dec 2003 41 Dec 2003 41 Dec 2003 000004 000005 oooo06 HooooT HOO00G E j tiys 000010 0000 000
30. er Name P _ H spiralest a Login Remember Me Version v1 0 1 Copyright C 2006 2007 Inflectra Corporation Forgot your password j ii unt inflectra Don t have an account You need to enter your given user name and password into the system in the appropriate boxes then click the lt Log In gt button to gain access to the application Normally you only remain logged in to the application whilst in active use and you will be asked to log in again after either closing the browser or 20 minutes of inactivity To prevent this and stay logged in to SpiraTest regardless of browser window closing or inactivity select the Remember Me check box before clicking the lt Log In gt button Note that this setting is specific to each individual computer you are logging in from and that it will be reset when you explicitly log out with the log out link described in more detail in section 3 3 If for any reason you are unable to login with the provided username password combination and error message will be displayed If you cannot remember the correct log in information click on the Forgot user name password link and your password will be emailed to the email address currently on file If you don t have an SpiraTest account setup clicking on the Don t have an account link will take you to a form that you need to fill in which will be forwarded to the system administrator who will actually cr
31. es a spiraTest wo SpiraTest User Manual Version 1 0 2 Inflectra Corporation inflectra Contents 1 Introduction 2 Functionality Overview 2 1 Requirements Management 2 2 Test Management 2 3 Incident Tracking 2 4 Projects and Users 2 5 Artifact Relationships 2 6 Application Site Map User Project Management 3 1 Login Screen 3 2 My Page 3 3 Global Navigation 3 4 Project Home 3 5 My Profile Requirements Management 4 1 Requirements List 4 2 Requirement Details Test Case Management 5 1 Test Case List 5 2 Test Case Details 5 3 Execute Test Case s 5 4 Test Run Details Incident Tracking 6 1 Incident List 6 2 Incident Details 6 3 Incident Discovery Report Aa WO W N N N N oOo N OQ A 12 12 15 16 16 19 22 24 26 26 28 29 1 Introduction SpiraTest provides an integrated holistic Quality Assurance QA management solution that manages requirements tests and incidents in one environment with complete traceability from inception to completion Quality Assurance is a key component of the Software Development Life Cycle SDLC which needs to be integrated into the planning and management of a program or project from its inception Too often though QA is implemented as Quality Control whereby testing that the required functionality works as expected is performed at the end when it is most costly to make corrections and changes To ma
32. from excel Library Information System Enhancement 3 Medium 25 Nov 2003 auawa tall Test System Limitation Library Information System Limitation 3 Medium 4 Dec 2003 Ahliy r j O k I i 5 i f i i existing bon re aa paa a Sample Risk 3 Library Information System Risk 4 Low 10 Dec 2003 Copyright C 2006 2007 Inflactra Corporation SpiraTest v1 0 1 j n flectraZ Note that once you have successfully logged in and chosen a project SpiraTest remembers this selection and on subsequent log ins will automatically select that project and highlight it for you in the My Projects list see 3 2 1 below Your homepage contains all the information relevant to you consolidated onto a single page for you to take immediate action The page typically consists of the following elements 3 2 1 My Projects This section lists all the projects you have been given access to together with the name description web site and date of creation To view the description of the project simply position the mouse pointer over the link and a tooltip window will popup containing the description When you initially view the page all of the projects will be shown as links in normal type with a white background When you click on a project to view you will be taken to that project s home page and that project will be set as the current project That project will now appear in your home page in bold type with a yellow background see abov
33. g the mouse pointer over the point and a tooltip will pop up listing the actual data value Similarly by clicking on the date range radio button you can display the past 12 months of incident discovery data organized on a weekly basis Welnore Fred Giggs biy Profle Loo Gad My Page pm gt Propo Henne gt Inmehdant Checoviwy Male Last 60 Days of Data Day Last 12 Months of Data Weekly Incident Discovery Rate Report Oacneed Closed Copyaght C 2006 infactra Cemperation SpuraTes wt inflectra 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 Clicking the Back to Project Home hyperlink will take you back to the Project Home dashboard Legal Notices This publication is provided as is without warranty of any kind either express or implied including but not limited to the implied warranties of merchantability fitness for a particular purpose or non infringement This publication could include technical inaccuracies or typographical errors Changes are periodically added to the information contained herein these changes will be incorporated in new editions of the publication Inflectra Corporation may make improveme
34. he requirements to the end of the list you just click the link without selecting a destination To abort the copy or move all you need to do is click the Cancel link and the operation will be aborted Note that copied requirements will also include the test coverage information from the originals 4 2 Requirement Details When you click on a requirement item in the requirements list described in section 4 1 you are taken to the requirement details page illustrated below Vileicome Pred Bloggs fy Profile Lia Gut Requirement Ability io associate books wath different subjects Book Management The fost covmage box micales the beat cases that mo cureiiy mapped ageming ihe requimmen Adi Ability 16 add new books jo the salam To add test cases to tis requiramant choose from the ist below and check You can use the Remmi and Rema All butbons bo memo tosis that no longer cover the requrement Absbty io ad mshng books in iha sy lityi i waji ku m Available Tet Cases fubility te atecciate looks with differen i Ability io saporas books with diaran jibilty fo craio nee book ADs fo edt orein book Absity jo gapo Ability to edt wasting author Baliy 4 letehe orate A Abiity fo massy book bo dienst i Aulhor mackerel Person lope eck and needs io re Adding new book awd mahar lo liran Deuble chcking on a ciwed lesl cade will lake you io lhe beH Cone deall Copynght C 2006 infectra Cop
35. hen you click on the Test Cases tab on the global navigation bar you will initially be taken to the test case list screen illustrated below Welcome Fred Bloggs My Profile Log Qut Libry information System lest Cases spiraTest Library Information System gt Test Cases mp New Test ca New Folder 3 Delete gt Execute Copy CyMove TestName Owner OOOO Pod h Refresh T Clear Filters 56 Functional Tests Ability to create new book T ability to edi existing book T Ability to create mew author T Ability to edit existing author T Ability to reassign book to different author E Regression Tests amp Scenario Tests B Exception Scenario Tests T Person loses book and needs to raport loss cp Newest cpNewFoker 3 Delete gt Execute Copyright C 2006 2007 Inflectra Corporation SpiraTest v1 0 2 Fred Bloggs Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Joe P Smith Joe P Smith Joe P Smith sous Execution Date 1 Dec 2003 21 Mar 2007 1 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dec 2003 11 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 1 Dec 2003 1 Dec 2003 14 Dec 2003 1 Dee 2003 1 Dec 2003 1 Dec 2003 11 Dec 2003 11 Dec 2003 1 Dec 2003 1 Dec 2003 1 Dee 2003 Oooo Edie OOOOOS e ono0o4 000005 E 000006 e eam D00007 Edit oomo fe
36. isplays a breakdown of the top five issues logged against the project in order of decreasing priority Note that items not given a priority are listed at the top since critical issues could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the issue item hyperlink will take you to the incident details page for the issue in question see section 6 2 3 4 6 Top Open Risks This section displays a breakdown of the top five risks logged against the project in order of decreasing priority Note that items not given a priority are listed at the top since critical risks could be lurking in that list and the project manager will want to immediately review these to assign priorities Clicking on the risk item hyperlink will take you to the incident details page for the risk in question see section 6 2 3 4 7 Incident Summary This section consists of a Summary table that displays the aggregate count of incidents in the system broken down by importance on the x axis and status on the y axis This allow the project manager to determine how many critical vs low priority incidents are waiting to be addressed and how many new items need to be categorized and assigned Clicking on the View Details link at the top of the table simply brings up the incident list see section 6 1 By default this summary table displays the total count of all incidents regardless of type
37. ity ranked from Critical to Low and its completion status from Requested to Completed as well as a graphical indicator that represents its coverage status For those requirements that have no test cases covering them i e validating that the requirement works as expected the indicator consists of a yellow solid bar bearing the legend Not Covered For those requirements that have at least one test case mapped against them they will display block graph that illustrates the last execution status of each of the mapped test cases Thus if the requirement is covered by two test cases one of which passed and one of which wasn t run the graph will have three green bars 50 passed and three gray bars 50 not run Note The number of bars has no relation to the number of tests To determine the exact requirements coverage information position the mouse pointer over the bar chart and the number of covering tests along with the pass fail not run breakdown will be displayed as a tooltip 4 1 1 Insert Clicking on the lt Insert gt button inserts a requirement above the currently selected requirement i e the one whose check box has been selected at the same level in the hierarchy If you want to insert a requirement below a summary item you 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
38. ld is searched using a LIKE comparison so that searching for database would include any item with the word database in the name The other freetext fields need to be exact matches e g dates test case numbers In the screen shot above we are filtering on Execution Status Not Run 5 1 7 Copying and Moving To copy or move a test case or test folder simply select the check boxes of the test cases folders you want to copy or move and then click either lt Copy gt or lt Move gt as appropriate Upon clicking the button the rows you selected will be marked in bold with a light yellow background and the screen will prompt you to choose the destination for the copy move Welcome Fred Bloggs My Profile Log Out Project Home Requirements Test Cases Incidents spiraTest Library Information System gt Test Cases Owner Execution Date Oo O bae EE Functional Tests Fred Bloggs 1 Dec 2003 Fred Bloggs 1 Dec 2003 gooi T Ability to create new book Fred Bloggs 1 Dec 200F Fred Bloggs 1 Dee 2003 poogt T Ability to edit existing book Fred Bloggs 1 Dee 2003 Fred Bloggs 1 Dee 2003 T Ability to create new author Joe P Smith 1 Dec 2003 Fred Bloggs 41 Dec 2003 T Ability to edit existing author Joe P Smith 1 Dec 2003 Fred Bloggs 1 Dec 2003 T Ability to reassign book to different author Passed Joe P Smith 1 Dec 2003 Fred Bloggs 1 Dec 2003 DOOD ica m Regression Tests 41 Dec 2003 Joe P Smith 1 Dec 2003 ottir SIS Scenario Tests
39. lders are always displayed before any of the actual test cases Once the new test folder has been inserted the item is switched to Edit mode so that you can rename the default name and choose an owner and or author 5 1 3 Delete Clicking on the lt Delete gt button deletes all the test cases and or test folders whose check boxes have been selected If any of the items are test folders then all the children are all deleted whether test cases or folders This behavior is similar to that in Microsoft Windows Explorer Note that you cannot delete all the test cases in a test folder at least one test case needs to be left in the folder the system will warn you if you try to do this 5 1 3 Execute Clicking on the lt Execute gt button executes all the test cases selected together with all the test cases contained with any selected test folders The test execution functionality of SpiraTest is explained in more detail in section 5 3 5 1 4 Refresh Clicking on the lt Refresh gt button simply reloads the test case list This is useful as other people may be modifying the list of test cases at the same time as you or executing specific test cases and after stepping away from the computer for a short time you should click this button to make sure you are viewing the most current test case list for the project 5 1 5 Edit Each test case folder in the list has an lt Edit gt button display in its right most column When yo
40. nage QA across a project from day one it is imperative that the original requirements are documented together with the use cases that validate the desired functionality These use cases then form the basis of the test scripts that can be executed to validate that the functionality has been correctly built and that the requirements have been satisfied During the execution of these test scripts failures may occur which are recorded as incidents either to be fixed or documented depending on the severity Typically these activities require people to use at least three different types of software gt Requirements Management gt Test Script Management gt Defect Issue Bug Tracking However this stove piped approach has many limitations and drawbacks most importantly the fact that there is no traceability between the different artifacts How can the project manager know that all the requirements have been tested Conversely how can the developer know which test script was responsible for a recorded bug needed to accurately reproduce the issue This user manual outlines the features and functionality available in SpiraTest and demonstrates how to use the application for managing the QA processes on a typical project 2 Functionality Overview This section outlines the functionality provided by SpiraTest in the areas of requirements management test management incident tracking and project user management
41. nt details page To change fields not displayed in the incident list you will however need to click on the incident name to view the Incident Details page see section 6 2 6 2 Incident Details When you click on an incident item in the incident list or click the lt New Incident gt button as described in section 6 1 you are taken to the incident details page illustrated below ea m Cannot edd a new book fo the system Bug X Shue Aguapnad w Tau Run Step DOOD Prenty i Critical tlaed On mia Description Ween I click on tha Button HEL i Sat a PEBGEFLEt St of Fess Repolulion eee eee Copy gt 2006 bieda Comporsbon SpeaTeat v1 9 a Fa sidik sn iii j inflectra This page is made up of two areas the top navigation bar with the gray background that allows you move between incidents and the main pane yellow background that contains the details of the incident in question The navigation bar allows you to move within the list of incidents that were displayed in the incident list page without having to go back to that page So if the incident list page contained a list of all bugs sorted by priority the buttons on this navigation would allow you to cycle between the different bugs in order of priority If you want to view incidents that are outside this filtered list or want to change the way they are sorted you need to click the Back to Incident List hyperlink and change the filter sort
42. nts and or changes in the product s and or program s and or service s described in this publication at any time SpiraTest and Inflectra are trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Explorer and Microsoft Project are registered trademarks of Microsoft Corporation All other trademarks and product names are property of their respective holders Please send comments and questions to Technical Publications Inflectra Corporation 10301 Julep Avenue Silver Spring MD 20902 U S A support inflectra com
43. ny of the tabs will simply take you back to My Page so that you can select a project 3 3 1 Log Out Clicking on the Log Out link will immediately log you out of your current session and return you to the login page illustrated in section 3 1 If you had set the Remember Me option during your previous login that setting will be reset so if you want to avoid having to keep logging in you ll need to re check that box during your next log in 3 3 2 Help Clicking on this link on any page will bring up the online version of this manual shown below HR Spiralest Online Help Microsoft Internet Explorer Spiralest Help Center Table of Contents 1 Introduction 2 Functionality Overview 2 1 Requirements Management 2 2 Tes Management 2 3 Incktent Tracking 2 4 Projets and Users 2 5 Artifact Relationships 2 6 Applicaton Sie Map User Project Management 3 1 Login Screen 3 2 hy Page 3 3 Global Navigation 3 4 Projeti Hoe 3 5 My Profie 4 Requirements Management 4 1 Requirements List 4 2 Requirement Betas 4 Test Case Management 6 1 Tesi Case List 5 2 Tesi Case Deisis 6 3 Execute Tesi Case s 5 4 Tesi Run Details 6 Incident Tracking 6 1 hieni List 6 2 incidenti Details 6 3 nedeni Discovery Report SpiraTest User Manual 1 Introduction Quality Assurance QA is a key component of the Software Development Life Cycle SDLC which needs to be integrated into the management of the
44. on the incident list page You can either enter a specific incident number in the text box and click the lt Find gt button or simply click one of the four movement buttons move first move previous Move next and move last to cycle to a different incident in the list 6 2 1 Editing an Existing Incident If you are editing an existing incident the following fields will be editable for you to change gt Name Status New Open Assigned Fixed Closed Duplicate Cannot Reproduce gt Incident Type Bugs Enhancements Issues Training Items Limitations Change Requests and Risks Detected By User Assigned Owner Priority Critical High Medium Low Closed Date Description VV VV VV y Resolution Note that the mandatory fields are listed in bold type with asterisks Once you ve made the changes to the appropriate incident fields you can either click lt Update gt to commit the changes or lt Cancel gt to discard the changes and return back to the incident list 6 2 2 Inserting a New Incident If you are inserting a new incident only the following fields will be editable for you to fill in gt Name Detected By User gt Priority Critical High Medium Low gt Closed Date gt Description gt Resolution The reason for the limited number of editable fields is that all incidents are created as type Incident and status New so that they have to be formally reviewed assigned a type priority owner
45. pen Open Assigned Duplicate Closed Closed Open Assigned Assigned Open Sample Risk 2 Sample Risk 3 Test Change Request Test Change Request Test Change Request Tesi Change Ragquest Teal Change Request Test Change Request Test Change Request Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Joe F Smith 10 Dec 2003 10 Dec 2003 10 Dec 2003 Dec 27003 amp Dec 2003 B Dec 2003 7 Dee 2003 T Dec 2003 T Dec 2003 6Dec 2003 a Fred Bloggs Fred Bloggs Joe P Smith Fred Bloggs Fred Bloggs Joe P Smith Joe P Smith Fred Bloggs Fred Bloggs Copyright C 2006 2007 Inflectra Conporation SpiraTest v1 0 1 inflectraZ The incident list screen displays all the incidents entered for the current project in a filterable sortable grid The grid displays the incident number together with the incident type bug issue risk etc status new open etc priority name assigned owner detection date and original detector In addition you can view a more detailed description of the incident along with a resolution if any by positioning the mouse pointer over the incident name hyperlink and waiting for the popup tooltip to appear If you click on the incident name hyperlink you will be taken to the incident details page described in section 6 2 Clicking on any of the pagination links at the bottom of the page will advance you to the next ten incidents in the list according to the applied filter and sor
46. program or project from its inception Too often though QA is implemented as quality control whereby testing that the required functionality works as expected is performed at the end when it is most costly to make corrections and changes To manage QA across a project from day one it is imperative that the original requirements are documented together with the use cases that validate the desired functionality These use cases then form the basis for the test scripts that can be executed to validate that the functionality has been corectly built and that the requirements have been satisfied Dunng the execution of these test scnpts failures may occur which are recorded as incidents to either be fixed or documented depending on the seventy Typically these actmities require people to use at least three different types of software Requirements Management Test Script Management Defect Issue Bug Tracking However this stove piped approach has many limitations and drawbacks most importantly that fact that there is no traceability between the different artifacts How can the project manager know that all the PAR PAPAA R A haia haan taska OO ae el Baiv eana tha eee baari udat kask eee iraa Clicking on any of the links in the left hand table of contents will automatically scroll the reading pane on the right to the appropriate section in the help manual By default the reading pane will open to the help item that is most clos
47. raTest T My Profile Pigase mara the mefonmabon bested below and mako any charspes f necessary Once you have finished click Update to confom them First Name Fied Middle Initial Last Hame Bloggs User Hane hedhlepps C Change Password Copyright C 2006 inflectra Corporation SpraTest 1 0 inf lectra You can change your user information including your first name last name middle initial and user name The system will check to make sure that the user name is not already in use and warn you if this is the case Clicking the lt Update gt button will commit the changes whereas clicking lt Cancel gt returns you back to either Project Home or My Page depending on whether you have a project currently selected or not 3 5 1 Change Password In addition to being able to update your user information you can optionally change your password at the same time If you check the Change Password box when the lt Update gt button is clicked the system will expect you to have entered your old password and two instances of your new proposed password If the old password matches the one stored in the system and the two entries of the new password match then the system will update your password otherwise you will simply get a warning message indicating what needs to be corrected 4 Requirements Management This section outlines how the requirements management features of SpiraTest can used to develop a r
48. s breakdown of the covered requirements In addition to the three statuses for the covered requirements the fourth Not Covered bar depicts the total number of requirements that have no tests covering them putting the three other bars into perspective Typically a project is in good health if the Not Covered bar is zero and the count of Passed requirements is greater than Failed or Not Run The greatest risk lies with the Not Covered and Not Run status codes since the severity quantity of any bugs lurking within is not yet known If you position the mouse pointer over any of the four bars the color of the bar changes slightly and the underlying raw data is displayed as a tooltip together with the percentage equivalent Clicking on the View Details link at the top of the table simply brings up the project requirements list see section 4 1 3 4 4 Requirement Incident Count This section displays a count of the total number of incidents and the number of open incidents mapped against requirements in the system displayed in an indented list This section is useful for determining the parts of the application that have the most instability as you can look at the requirements that have yielded the greatest number of incidents Clicking on any of the requirements hyperlinks will take you to the detail page for the requirement in question see section 4 2 3 4 5 Top Open Issues This section d
49. s other people may be modifying the list of requirements at the same time as you and after stepping away from the computer for a short time you should click this button to make sure you are viewing the most current requirements list for the project 4 1 6 Edit Each requirement in the list has an lt Edit gt button display in its right most column When you click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information 4 1 7 Show Level Choosing an indent level from the Show Level drop down box allows you to quickly and easily view the entire requirements list at a specific indent level For example you may want to see all requirements drilled down to the third level of detail To do this you would simply choose Level 3 from the list and the requirements will be expanded accordingly 4 1 8 Filtering You can easily filter the list of requirements as illustrated in the screen shot below spiraTest Library Information System gt Requirements 3 Delete indent da utdeni Ability to link authors to them contact informati Administration Functions B Data Import Functionality Ability te impot from legacy system x Ability to cre
50. sorting and filtering of all the incidents in the system as well as the ability to view the incidents associated with particular test cases and test runs enabling drill down from the requirements coverage display right through to the open incidents that are affecting the requirement in question 2 4 Projects and Users SpiraTest supports the management of an unlimited number of users and projects which can be administered through the same web interface as the rest of the application All artifacts requirements tests and incidents are associated with a particular project and each user of the system can be given a specific role for the particular project So a power user of one software project may be merely an observer of another That way a central set of users can be managed across the enterprise whilst devolving project level administration to the manager of the project In addition to these administration functions each user profile and project has its own personalized dashboard view of all the pertinent and relevant information This feature reduces the information overload associated with managing such a rich source of project information and allows a single user or project snapshot to be viewable at all times for rapid decision making 2 5 Artifact Relationships The sections above have outlined the different features and functions available in the system and have described the various artifacts managed in the system e g
51. st steps and reorders the test step position numbers to close any gaps in numbering 5 2 4 Move Up Clicking on the lt Move Up gt button simply reorders the test step list so that the currently selected test step is one position higher up the list Note Attempting to move a test step above the top of the list will give a warning message 5 2 5 Move Down Clicking on the lt Move Down gt button simply reorders the test step list so that the currently selected test step is one position lower down the list Note Attempting to move a test step below the bottom of the list of existing test steps will give a warning message 5 2 6 Refresh Clicking on the lt Refresh gt button simply reloads the list of test steps This is useful if other people are making changes to the test list and you want to make sure that you have the most current version 5 2 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 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 l
52. t Cancel gt and your changes will be discarded 5 2 9 View Test Runs This view displays the name of the test case together with a list of the previous execution runs that the test case has been put through Each test run is listed together with the date of execution the name of the test case the name of the tester the overall execution status for the test case in that run and a link to the actual test run details See section 5 4 Welcome Fred legge fy Profile Log Out My Page f Project Heme J Requeemets Tost Cama Library lnleamacion Syatam gt Tea Cate gt Ton Laie Donal m Tost Lis hme iSO ep Moret enn gt Functional Tesa Test Cage Ability to create new book ae ergata tw enak O View Test Steps C View Test Runs C Wiw Coverage spiraTest Ability to omma new book Abikty to create new book Gopynighi iC 2005 infect Corporation Speatest v1 0 inflectra 5 2 9 View Coverage This view displays the name of the test case together with the requirements coverage information for the test case in question Veloce Fred Glaggs fly Pupils Lag Gul My Page Liars information Sysinen est Lass gt oe Cosap endl x 1 eB E Functional Tesia Test Cage Abt to creaie new book Se g r spiraTest n TAi t cais maw book D View Test Steps C View Test Runs View Coverage The requirements coverage box meficaies the requirements that are cucrently mapped against the test come To mid requrements bo this
53. t Finish gt button will be displayed instead In addition to logging the failure you can optionally choose to have the failure result in a new incident be automatically created This is achieved by selecting the Log an Incident for this step checkbox and entering a name for the new incident The other information needed for the new incident is automatically populated from the test step details The newly created incident will also be linked to the test step allowing traceability from within the incidents module The functionality for managing incidents is described in more detail in section 6 Note that the entire test run is not actually saved until the lt Finish gt button is clicked so you can use the move forward backward buttons to revisit previous test cases and or test steps and make changes before saving the test run As a consequence however you should make sure you complete the test run or at least the test cases you have time for and save it before leaving the computer for a period of time this will ensure work is not lost due to the timeout of your session 5 4 Test Run Details As described in section 5 2 8 when you view the details of a test case one of the views possible is to list all the test runs for that test case Welcome Fred Bloggs My Profile Log Qut My Fage Preyect Home Flequirementa Test Canes Bedana Library halonmmasion Sysam gt Tast Cagea gt Tasi Cans Dacia TP e Ep Deitel li 6 Mee Orem
54. t order 6 1 1 Sorting and Filtering You can easily filter and sort the list of incidents as illustrated in the screen shot below Welcome Feed Biegga biy Profile Log Oui 0 O C i o7 nooo ES Wa al yala cay ae ot Cannot add a nena book ip ita mam bamali pi ia ada bax i pee Fred Dipgge Joo P Smith dpe P Smith dot P Smith oui Fred Blogga Fred Blagas 2 Noe2ng there 2000 Dior 200 toe 2000 12000 Nea 15Na doez tihi 3 E chatiy The homepage hanga white Fred Bloges lacing oOo 0 The book sling Spier diego fHow std z0 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 to apply the different filters Note that the name field is searched using a LIKE comparison so that searching for database would include any item with the word database in the name The other freetext fields need to be exact matches e g dates incident numbers To change the column that is sorted or to change the direction of the current sort simply click on the up down arrow icon in the appropriate column The currently sorted column is indicated by the larger white arrow with the back border In the screen shot above we are filtering on type bug and sorting by decreasing priority 6 1 2 New Incident Clicking on the
55. tent case choose fom the kat below and chek Add You can uae the Remove and Remco AN buttons fo rompa requeements thal are na longer cowmred by the best Cape Available Requirements Ea eet S ena Svelem AARAA Abddty bo add mew booka bo the gyre Ability bo echt existing bos i Abiity bo delete tosing book aa Abily to associaio books wil Ahy bo acciaie books mel Abity bo abhi books wel Pe a Lh a aaae al pam Abiy t crnate ere adic Dewble chc king nn a covered tegema yall lake you lo ihe reguemern dyek The main right pane consists of two lists of requirements the one on the left being the hierarchical list of the requirements belonging to the project the summary items are denoted by their gray color The right box contains the list of requirements mapped to this test case Double clicking on items in this box will jump you to the requirements details screen for this requirement see section 4 2 To change the coverage for this test case you use the buttons Add Remove Remove All positioned between the two list boxes The lt Add gt button will move the selected requirements from the list of available on the left to the list of mapped on the right Similarly the lt Remove gt and lt Remove All gt buttons will remove either the selected or all the requirements from the right list box and add them back to the left list box Note that none of the changes are committed until you click the
56. the new requirement will simply be inserted at the end of the list Once the new requirement has been inserted the item is switched to Edit mode so that you can rename the default name and choose a priority status and or author 4 1 2 Delete Clicking on the lt Delete gt button deletes all the requirements whose check boxes have been selected If any of the items are summary items then if the item is expanded and the children are visible the children are simply made children of the item above it in the list however if the item is not expanded and the children are hidden then the children are all deleted This behavior is similar to that found in project planning tools like Microsoft Project In addition if all the children are deleted from a summary item it changes back into a detail item 4 1 3 Indent Clicking on the lt Indent gt button indents all the requirements whose check boxes have been selected If any of the items are made children of a requirement that had no previous children it will be changed from a detail item into a summary item 4 1 4 Outdent Clicking on the lt Outdent gt button de indents all the requirements whose check boxes have been selected If any of the items were the only children of a summary requirement item then that item will be 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 a
57. the right Similarly the lt Remove gt and lt Remove All gt buttons will remove either the selected or all the test cases from the right list box and add them back to the left list box Note that none of the changes are committed until you click the lt Update gt button at the bottom right of the screen If you want to discard the changes you have made simply click either the lt Cancel gt button or the Back to Requirements List link and you will be returned to the Requirements List page 5 Test Case Management This section outlines how the use case test case management features of SpiraTest can used to develop the business use cases for the system which specify how the different pieces of functionality are expected to work in practice In addition these use test cases form the basis of the business specification of the system when associated with the underlying requirements matrix Typically when starting a new project gt The requirements matrix is entered first Then the list of use cases is developed to outline the key scenarios that need to supported to implement the requirement Then the use cases are fleshed out into full test cases by adding the detailed test steps with the expected result and suggested sample data However when migrating existing projects into SpiraTest you may need to migrate the test case list first and then add the supporting requirements matrix afterwards 5 1 Test Case List W
58. u click this button you change the item from View mode to Edit mode The various columns are made editable and lt Update gt lt Cancel gt buttons are displayed in the last column When you have made your updates you can either click lt Update gt to commit the changes or lt Cancel gt to revert back to the original information 5 1 6 Filtering You can easily filter the list of test cases as illustrated in the screen shot below Welcome Fred Bloggs My Profile Log Out lest Lases spiraTest a Library information System gt Test Cases Role Manager cp NewTest chNewFolder Delte gt Execute hee hhe Refresh YT Gea Fitters TestName States Owner Eemi Date Author Creation Date Test O A Scenario Tests Hot Run Joe P Smith Joe P Smith 1 Dec 2003 Oooo BE Exception Scenario Tests Hot Run Joe P Smith Joe P Smith 1 Dec 2003 000011 T Person loses book and needs to report loss Mot Run Joe P Smith 11 Dec 2003 nooo T Adding new book and author to library Mot Run Joe F Smith 11 Dec 2003 000013 Edit cb Hew Test es New Folder t Delete gt Execute Copyright C 2006 2007 Inflectra Corporation SpiraTest v1 0 2 in flectra To filter the list by execution status owner name or author name you simply choose an item from the appropriate drop down list and for the other fields you enter a free text phrase then click lt Filter gt to apply the different filters Note that the name fie
59. views by clicking the appropriate radio button Initially the pane will be in View Test Steps mode but it can be switched to View Test Runs and View Coverage modes if so desired Each of the views is described separately below 5 2 1 View Test Steps This view displays the name of the test case together with all the defined test steps that a tester would need to perform to verify that the functionality works as expected The list of test steps displays the position number the description the expected result some suggested sample data and the most recent execution status of the individual test step 5 2 2 Insert Step Clicking on the lt Insert Step gt button inserts a new test step before the currently selected by means of the check box test step Clicking the lt Insert Step gt button without selecting a test step will insert a new step at the end of the list All test steps are displayed in Edit mode so the description expected result and sample data fields are editable allowing you to enter the appropriate data see section 5 2 7 In addition to the existing test steps the system always displays five blank test steps so that it is easy and quick to enter large numbers of test steps Upon entering up to five test steps and clicking the lt Update gt button five new blank rows will be added at the bottom of the list 5 2 3 Delete Clicking on the lt Delete gt button deletes the currently selected te

Download Pdf Manuals

Related Search

Related Contents

EMR - Codumé  TAD8811 - SV-NETサーボシステム - tamagawa seiki co.,ltd.  bon de commande  Guida dell`utente della fotocamera Avanzata  Toshiba Tecra M10-0L5    

Copyright © All rights reserved. Failed to retrieve file