1 / 8

Agenda

Agenda. Introductions General Guidelines Getting Started How to Test Demo Logging Results Questions. General Guidelines. R eview the Quick Reference Guide Print your scripts before you come Follow the script schedule in sequence Note predecessors and dependencies

jela
Download Presentation

Agenda

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. Agenda • Introductions • General Guidelines • Getting Started • How to Test Demo • Logging Results • Questions

  2. General Guidelines • Review the Quick Reference Guide • Print your scripts before you come • Follow the script schedule in sequence • Note predecessors and dependencies • For any FAILS, be available to retest • If you’re done early, ask for more • Be Flexible in schedule adjustments • It won’t be perfect…

  3. Getting Started • Lotus Notes • CourtNet (GEARS) • Testing Schedule • PeopleSoft • UPK

  4. PeopleSoft/UPK How to Test Demo

  5. Logging Results • Open a new email message in Lotus Notes • For each script, record the result in the email message Include: • Script Number • Result • Notes/Screen Prints/Navigation (if needed) • Email your results to GEARSTESTTEAM@mdcourts.gov • Send it as you complete each scenario (grouping of scripts) • Send the remainder no later than 4:30 pm

  6. Logging Results • Result can be: • PASS • Pass with SCRIPT ISSUE • FAIL • RETEST PASS • Script Issue vs. Process Fail • Fails should be logged for process fails, NOTscript issues • Before logging a FAIL • Take a screen print of the issue • Notify the Test Room Manager to verify the result

  7. Questions?

More Related