Coherent Web TestTrack Pro 2012 User’s Guide (Web Client)

1. Coherent Web TestTrack Pro 2012 User’s Guide(Web Client)

2. Content • TestTrack Pro Overview • TestTrack Pro Workflow States • TestTrack Pro Workflow • System Requirements • Getting Started with TestTrack Pro • Using TestTrack Pro Web Client • Questions

3. Overview • The TestTrack Pro (TTPro) COTS product is a consolidated, centralized non-conformance reporting system used to track projects’ defects. • Users and Administrators can collectively store separate projects’ data in a single system. Each project is distinct, can be configured separately, and has its own administrators. • In TTPro, non-conformance reports (NCRs) move through a lifecycle of states (workflow milestones/events). A defect lifecycle starts with its submission and generally ends with its resolution. TTPro uses this lifecycle concept and manages bugs using a state transition tracking mechanism. • Defects in TTProare identified as NCRs. NCRs are organized by project and are sequentially numbered using unique 2-3 digit project prefixes: 18xxxxxx – 18999999 • There are five key data elements that drive the flow of Coherent Web defect tracking: • Defect Number:Every problem entered into the TTPro System contains an unique identifier. This numeric identifier is generated by the system for all projects. • Severity:Used to capture the impact (scaled 1 – 5) on operations. • Project:Categorizes defects according to affected subsystem or other classification. • Summary:A concise statement of the problem. • State:The state is a workflow milestone achieved in the lifecycle of the reported defect. States has associated events that perform a specified action within the state called, events. States change when triggered by specific events.

4. Workflow States • NCRs are transferred (workflow of events) from the “Open” state to the “Closed” state. • State – the initial decision point in the workflow of a defect., i.e., open, closed, fixed. • Event – specifies what action is to be performed at (or added to) each state. Events can be performed by the system. • NCRs can be assigned in any state, without changing state. • NCRs can be closed by the CW Team from any state.

5. NCR Workflows Content Update (Nominal) NEW CLOSED (Close) Content Approved & Modified (Acknowledge) Earthdata TeamAcknowledged FIXED OPEN In-Progress (Fix) Content Updated (Begin Work) NCR Assigned & Work Starts

6. NCR Workflows (con’t.) CMS Update (Nominal Requiring UAT Testing) NEW (Review) All development and testingactivities are complete- Approved - (Acknowledge) Earthdata TeamAcknowledged (Begin Work) NCR Assigned & Work Starts OPEN In-Progress FIXED (Fix) CMS Updated (Deploy to UAT) Pre-Approval for installationinto UAT Earthdata environment Ready for UAT Deployment Ready for UAT Testing (Verify in UAT) Awaiting Verification CLOSED (Verify in OPS) Awaiting Verification Ready for OPS Testing (Deploy to OPS) Pre-Approval for installationinto OPS Earthdata environment Ready for OPS Deployment

7. NCR Workflows (con’t.) CMS Update (Nominal NOT Requiring UAT Testing) NEW (Review) Pre-Approval for installationinto Earthdata environment (Acknowledge) Earthdata TeamAcknowledged (Begin Work) NCR Assigned & Work Starts OPEN In-Progress FIXED (Fix) CMS Updated CLOSED (Verify in OPS) All development and testingactivities are complete- Approved - (Deploy to OPS) Awaiting Verification Ready for OPS Testing Ready for OPS Deployment

8. NCR Workflows (con’t.) CMS Update (Verification Failed) NEW (Review) All development and testingactivities are complete - Approved - (Acknowledge) Earthdata TeamAcknowledged (Begin Work) NCR Assigned & Work Starts OPEN In-Progress FIXED (Fix) CMS Updated (Begin Work) NCR Reassigned & Work Starts (Open) Verification Failed- REJECTED- RE-OPENED Ready for UAT Testing Ready for UAT Deployment (Deploy to UAT) Pre-Approval for installationinto UAT Earthdata environment (Review) All development and testingactivities are complete - Approved - In-Progress FIXED (Deploy to UAT) Pre-Approval for installationinto UAT Earthdata environment Ready for UAT Deployment (Fix) CMS Updated (Verify in UAT) Awaiting Verification Ready for UAT Testing Ready for OPS Deployment (Deploy to OPS) Pre-Approval for installationinto OPS Earthdata environment CLOSED (Verify in OPS ) Awaiting Verification Ready for OPS Testing

9. TestTrack Pro Web Client • What’s Required: System Elements: • Internet Explorer 8.0+ or Firefox 3.6+ standard software to access web interface • Username and Password (NAMS) (see Administrator) • Read/Write permission to database(see Administrator) • TTPro Server and Web Server up and running

10. Getting Started • Logging In: Users are NOT allowedmultiple logons, due to the limited number of available licenses. Automatic system idle timeout (20 minutes). • Launch recommended Internet Browser and Enable Pop-ups • Enter URL: https://links.gsfc.nasa.gov:20072The SeapineTestTrack Pro “Welcome…” screen appears… • Enter Username and Password (NAMS), thenclick Login • the Login dialog box appears • Select Project from list box • Select Start at from list box • Select Login – The selected Project’s window displays the list of its defects. The project’s defect list window appears….

11. TestTrack Pro (Web Client) List Window • The defect list window provides access to the TestTrack Pro project’s defect records. • Users have the capability of controlling what defects are displayed by using the Filter command. LogoutandUser Menu Active Userinformation Number Records Indicator Next/Previous Page Project Indicator TTPro Menu & Tabs Filter list (run button) Setup Columns User Defined column headers to sort on, insert or delete (list view) up to 9 columns Events Defect Search Defect # Locator List of defects within specified Project Import /Export options Email options Defect Indicators

12. * Required entry( ) TestTrack Pro (Web Client) Defect Screen • Upper Tab Area – Generally defines all related parts of the Defect. • Lower Tab Area – display tabs that support NCR series of events or lifecycle flow • Field names in bold text are“required” entry, although all related fields should be input. • Defect numbers are assigned after data entry of problem is committed.To commit entry, depress the Save button in upper and/or lower panel of window. • Use “Logout” when exiting Web Client. Using the “Exit Windows” options will only close the windowand not releasing a User license until post-idle time-out of system. Logout TTPro Work Activity Tabs “abc” – Textbox with Spell Checking Commit Entry& Close View Status Upper (Work Activity) Tab Input Area Calendar Defect Details Tabs Lower (Defect Details) Tab Input Area *input fields not shown

13. Entering New NCR - Main Update NCR • Ensure all bold-titled fields are completed. These are mandatory fields. • Tab (or click in) through to input fields. • Use defect tabs to move through sections of the defect (NCR). • To save updates, select “Apply” but to commit and exit, select “Save”. Commit NCR State of NCR Enter a concise statement of problem NCR’s activity tabs *activity tabs’ input fields (screens) not shown

14. Entering New NCR – Detail • DetailTab • Reported n time(s): The submitter’s name and date. • Found by (Submitter): System-generated, but changeablename of the person who found the problem. • Date Found: Date the problem was detected. • Description: Detailed, but concise description of the problem • sufficient for an Engineer to analyze. Should include: • when the problem occurred • what server was affected • what logs are available • what processes or servers were running • associated hardware problems observed • how often the problem occurs • what steps were taken to alleviate the problem and their results (if any) • current state of the system • operational system impact. • Save the NCR entry and commit the record, assign a defectnumber, and active the project window. The defect summary line will appear in the project window. Add Additional Defect Occurrences Calendar Add detailed description of Defect Occurrences Spell Check Save/Update Defect Add related attachments supporting the defect’s fix

15. Entering New NCR – Workflow WorkflowTab Track the Lifecycle of Events of the Defect: This features displays a listing of every event or state change for the defect. It provides information on: Event, Date of update, Who made the change, and Other Information related to the defect that the system captures/tracks. To view the details of an event, click on the item’s link listed in the Workflow window. Save the changes to Workflow entry fields. Workflow links to edit or view details Save/Update Defect Previous/Next Defect

16. Viewing New NCR – Workaround WorkaroundTab Workaround: Provide location to record complete details how to work around the bug or recommended detail to fix or implement the defect. Add complete detail of a workaround the bug or fix Save/Update Defect Previous/Next Defect

17. Entering New NCR – Folders FoldersTab Folders: Provide an organized location to group defects with other related defects (providing links to multiple NCRs). TTPro allow User to define 5 folders as Public (accessible to other users) or Private (restricted to folder’s owner). NOTE: Folders can only be created in the TestTrack Pro Client. Click option to Add, Move, or Remove NCRs to/from Folder Public or Private defect folders Paths or location is listed. Click the path to access folder with related defect(s). Save/Update Defect

18. Viewing NCR – History HistoryTab History: Tracks system-generated history of changes made to the NCR. Data in this view is unchangeable. Created data Modified data Sort-on column headers Tracked Changes Save/UpdateDefect

19. Editing NCRs Events To Edit the information in a NCR Event, workflow events must be modified. The events are located as active links in the Workflow tab: Select the NCR checkbox, from the Defects List Window Select the Edit option Select the Workflow tab, to display any active links of events Select the Event Link to edit (i.e., Acknowledge, Assign, Fix). Additional options will prompt to all the event to be modified. Modify fields as necessary. Select Edit details, to update/modify event Click OK, to update/commit change(s). NOTE: The event date can not be changed. A system-generated automatic email notice is sent to Assignees notifying change made to defect Update Event Workflow links to edit or view details Previous/Next Defect

20. Setting User Options • User Optionslets you specify your password and personal preferences. • Password options allow user to reset pre-defined password. For security purposes, the system automatically prompts user to reset password every 90 days. • Notification options allow you to specify circumstances under which TTPro is to send you email (e.g., whenever an NCR changes). These messages supplement a project’s system notification. • Display Options: • Set number records per page. • Client window layout. • Defect’s status and assignment field.

21. Setting User Options (con’t.) • Adding multiple NCRs: Choose to Close the Add NCR before creating or editing defects to preclude inadvertently create multiple defect reports when creating a new NCR (defect). Your Administrator can not perform this function. • Dictionary option all user to use system generated dictionary and add user inputs. • Spell Check Options assists with spell correcting functions throughout defect editing. • Save must be clicked to capture all option changes.

22. Help! links.hitc.com:20072 Use TestTrack Pro Logout TTPro Login Q&A