1 / 26

Visual Intercept Incident Tracking System

SQA Incidents Tracking System using Visual Intercept. Track bugs, feature requests, V&V test requests, and more. Installation and setup instructions included.

victorclarke
Download Presentation

Visual Intercept Incident Tracking System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Systems SQAIncident Tracking Systemby William Gunkel, Manager Test System SQA

  2. SQA Incident Tracking System Overview Test Systems has retired the old bug tracking system ‘Track Record” We now use Win95/98 NT based incident tracking system ‘Visual Intercept’ It’s not just tracking bugs anymore We track: Bugs, feature requests, V&V Test requests, Document / design change requests, AND any other issues that require an electronic paper trail

  3. SQA Incident Tracking System Installation Folder Software server: Swgroup: Which should be mapped as your ‘I’ drive

  4. SQA Incident Tracking System Installation • If you do not already have Visual Intercept installed • As shown on the previous slide go to the ‘VI’ folder and run the ‘Setup.exe’ program to install Visual Intercept client on your PC • VI is on the ‘Software’ server, under the swgroup folder • The swgroup folder on the Software server should be mapped as your ‘I’ drive

  5. SQA Incident Tracking System Installation options Use the NetSetup defined configuration

  6. SQA Incident Tracking System Installation options Note the required path to the database

  7. SQA Incident Tracking System Installation options Continue, we do not use the ‘primary’ directory

  8. SQA Incident Tracking System Installation options Must use the existing database

  9. SQA Incident Tracking System Installation options Must use the existing datasource

  10. SQA Incident Tracking System Log on screen Enter your network login name Password is your login name

  11. SQA Incident Tracking System Setup Options: Integration

  12. SQA Incident Tracking System Setup Options: Integration • From the Tools menu • Select Options • Set path for Documents to: • I:\PROGRAMS\Visual Intercept Enterprise\docs • Set path for temp folder to: • I:\PROGRAMS\Visual Intercept Enterprise\temp • Set path for reports to: • I:\PROGRAMS\Visual Intercept Enterprise\Reports

  13. SQA Incident Tracking System Setup Options: Integration • Set the Visual Source Safe Path to: • \\SOFTWARE\SWGROUP\Vss\srcsaf • User ID: Your VSS login name • Password: Your VSS password

  14. SQA Incident Tracking System Setup Options: Mail

  15. SQA Incident Tracking System Setup Options: Mail • VI has built in Email notification system. • Receive Email notice when your ‘incident changes status • Set User ID: • Same as your network login ID • Password same as your network password • Set template path to: • I:\PROGRAMS\Visual Intercept Enterprise\ismail.tpl

  16. SQA Incident Tracking System Setup Options: Notification Set the Notification option to ‘OnChange’, any changes to your incident will generate an Email to you

  17. SQA Incident Tracking System Setup Options: Notification • Set Directory to: • I:\PROGRAMS\Visual Intercept Enterprise\Rules

  18. SQA Incident Tracking System Setup Options: Queries All queries with check marks in the box will be listed in the IDE queries pull down box

  19. SQA Incident Tracking System Setup Options: Queries • Set Directory to: • I:\PROGRAMS\Visual Intercept Enterprise\Queries

  20. SQA Incident Tracking System Tool Bar Click here to enter a new incident Click here to fetch all incidents in the database Click here to select a pre-defined query Click here to run the query

  21. SQA Incident Tracking System Project Browser Window Previously reported incidents You may use the project browser window to pick the project for which you wish to record an incident The incident should be reported to the project with the narrowest possible focus. In the case of ‘Fonix III’ for a source code issue with the GUI you would use ‘Fonix III\GUI\Source’ sub-project. If the issue was say a feature request for the GUI you would apply incident at the ‘Fonix III\GUI’ sub-project level

  22. SQA Incident Tracking System Project Browser Window: Versions Double clicking any of the project folders will display the ‘Project’ dialog which list the version for that project. If the current version is not listed, add it by pressing the ‘New’ button. Or if a version number does not apply to this project use/add ‘None’ Please contact SQA if you can not find the Project for which you wish to report an incident

  23. SQA Incident Tracking System Project Browser Window: Tool Bar Select your project then press the new incident button on the tool bar, OR just press the new incident button and select the project from the incident dialog

  24. SQA Incident Tracking System Incident Form: Part 1 All Incidents must have a ‘Subject’, keep it simple but as descriptive as possible Track number is not a required field & may be used to tie to some other tracking system (EAR etc.)

  25. SQA Incident Tracking System Incident Form: Part 2 Be sure and make the correct project and version selection The fields shown in the circle are for the ‘Requester’ and should be set as required Please make careful selection of the category, as this is a key field for searching and tracking incidents The description of the problem should ALWAYS be as complete as possible. Include build number and date of test software if applicable. Also include ‘test environment’information (location, gear used etc.)

  26. SQA Incident Tracking System My Incident Query You may check all your incidents by running the ‘My Incidents’ query as shown

More Related