ctcLink Reference CenterResourcesReports/Queries SIT and UAT TestingOracle Test Manager Tester Guide - SIT Phase

Oracle Test Manager Tester Guide - SIT Phase

1. Misc. Information

All users identified for SIT  UAT testing will be assigned the Tester role with the exception of the test facilitators who will have Full Access roles.

Accounts for each tester are already created. Username and password will be provided prior to testing.

2. Oracle Test Manager Login

  1. Testers will log into Oracle Test Manager at https://oats.ctclink.sbctc.edu:8089/otm/ (Tester accounts are already created prior to the test phase and usernames and passwords will be provided to each tester).
  2. Enter your Username and Password then click Login.

 

Oracle Log In page

3. Test Tabs

When testers log into Oracle Test Manager, they will have full read/write/execute access to the Tests, Test Executions, and Issues tabs.

The Test tab will contain all test scripts in the left side tree view. Tests scripts may be assigned to a specific user.

Tests tab

4. Searching for Test Scripts

Use the Filter feature to query all test scripts assigned to a specific tester or for all test scripts identified for a particular test scenario.

  1. Click on the Filter button.
Tests tab

A Filter Tests box is displayed. 

  1. Select the Field drop down menu and select the Tester option.
  2. Keep the default Operator value and select your user name from the Value list.
Filter Tests

To search for all test scripts assigned to a specific pillar:

  1. Select Linked Test Scenario # option in the Field drop down menu.
  2. Enter CS, FIN, HCM, CEMLI in the Value field to return all test scripts for that pillar. Individual or group test scripts can be filtered by knowing the unique system generated test case id for the test script you looking for.
  3. Click on Apply and the test cases for the selected user are now available in the left tree view.
Filter Tests
  1. Once you have used filtering and would like return to your normal view, click on the Filter dropdown list to the right of the Filter button.
Tests tab
  1. Click on None and the filter is removed and the normal view with all test scripts is returned.

5. Tests Tab

Select a test script to run from the left tree view.  It will now be highlighted and the information for it displayed to the right of the tree view.

  1. Click on the attached file link listed under Attachments.
Tests tab
  1. Follow any prompts to download and open the test script file.
  2. Click on Run Test.
Tests tab
  1. A Test Run Info dialogue prompt is returned. Fill in the information as described below.
  • Run Name: Leave the default value
  • Version: If not present, select SIT from menu options.
  • College: Select the appropriate college from the list.
  1. Click on Run
Test Run Info
  1. A Run Manual Test window is returned. At this point, go to the test script file opened at the beginning of this section and execute all the steps.

 See section 6.2  6.3 for processing passed and failed test scripts.

6. Test Execution Tab

  1. Select a pillar from the left tree view.  It will now be highlighted and the information for it displayed to the right of the tree view. Test scripts for each pillar are already present and displayed in the Test List area.
Test Execution tab

6.1.Test Execution – Running Test Scripts

  1. Click on the test script hyperlink name to begin testing it.
  2. Click on the attached file link listed under Attachments. Follow any prompts to download and open the test script file.
  3. Click on Run Test.
Tests tab
  1. A Test Run Info dialogue prompt is returned. Fill in the information as described below:
  • Run Name: Leave the default value.
  • Version: If not present, select SIT from menu options
  • College: Select the appropriate college from the list.
  1. Click Run.
Tests Run Info
  1. A Run Manual Test window is returned. At this point, go to the test script file opened at the beginning of this section and execute all the steps.
  2. Click on Run Test.

6.2.Passed Test Script Process

When the test script is completed and has passed expected results, follow the directions entered in step 1 of each test script.

Appendix B:  System Generated Unique ID #

Action Expected Results Comment
Execute all test steps within the attached test file script. PASS:  If all the test steps meet their expected results the test script passes.

FAIL:  If one or more steps fail their expected results the test script fails.
PASSED TEST SCRIPT: Select Pass in the Result list, go to the bottom of the screen and click on Complete Test Run.

FAILED TEST SCRIPT:  Select Failed in the Result list then click on the Add icon under Add Issue. 

6.3 Failed Test Script Process

Defects discovered during the formal test execution process will be entered using this process.  If the test script failed, the tester is instructed to click on the Add icon under the Add Issue column header.

Run Manual Test
  • This will open a new Add Issue window where users will enter required information for defects found while executing test scripts.
  • All fields with an asterisk in the label name are required fields.
  • (See Appendix A, B, and C for data element values and format).
Add Issue
  • Defects entered as part of the test process will have some information in their Summary and Detailed Description fields already.
  • Summary field:  Leave the default value and add the Test Script ID to the beginning.  After adding the Test Script ID it will look very similar to: 3857 Test CS-FA:  Waivers_Test Script (Step #1) Failed.
  • Detailed Description field:  Click within this field and use the key command of Ctrl+A to select all.
  • Click on the Delete button.
  • Enter the step number that failed and provide any additional steps or information that will help others to reproduce the same failed result.
  • Once all fields are entered and the failed test script file is attached, click Save.

7. Add New Issue Process

Defects discovered outside of the formal test execution process will be added as new issues in OTM.

  1. Add a new defect, not associated to a test script/scenario by clicking on the Issues tab.
  2. Click on the Add button.
  • A new Add Issue window is returned.
  • All fields with an asterisk in the label name are required fields.  
  • Enter all required information and test steps in the Detailed Description field to allow others to reproduce the failed results.
  • See Appendix A, B, and C for required values and format for each data element.
  • Once all fields are entered and the failed test script file is attached, click Save.
Add Issue

Appendix A: Issue Data Element Table

Label Values Value Format
Summary (defect found during SIT test script execution). Populated value will be similar to:  Test CS-FA:  Waivers_Test Script (Step #1) Failed.  Test script ID needs to be added before "Test".  3857 Test CS-FA: Waivers_Test Script (Step #1) Failed
Summary (defect found during SIT test script execution) User input required. Enter brief description of issue.  High level description of issue. 
Component CS
HCM
FIN
OAA
OSECE
Mobile
N/A
Version Other
SIT
N/A
Status 1- New
2- Assigned
3- In Progress
4- Duplicate
5- Ready to Retest
6- Closed
7- Deferred
N/A
Severity 1- Critical
2- High
3- Medium
4- Low
N/A
AssignedTo auto populate with logged user name N/A
Priority - Low
- Medium
- High
N/A
Detailed Description User input Brief description of issue and steps to reproduce it.
Resolution User input Description of what was done to correct issue and steps to reproduce if different from Detailed Descriptions.
College - Columbia Basin
- Clark
- Green River
- Lower Columbia
- Peninsula
- Pierce
- SBCTC
N/A
Browser - Chrome
- Firefox
- Internet Explorer
- Safari
- Other Unsupported Browsers
N/A
Test Script ID System generated ID Each scenario and test script is assigned a system generated number which precedes the scenario/script name. The number is currently only four (4) digits long.  See Appendix B for reference. 
Oracle SR # Comes from Oracle Support when issue entered with Oracle.  N/A
Tests tab

 
 

 

 

Appendix C:  Pillar and Associated Module Acronyms

CS made up of the following modules:
· CS Fundamentals (CSF)
· Academic Advisement (AA)
· Academic Structure (AS)
· Campus Community (CC)
· Faculty Workload (FW)
· Financial Aid (FA)
· Instructional Assistants (IA)
· Managing Continuing Education (MCE)
· Recruiting and Admissions (RA)
· Self Service (SS)
· Student Financials (SF)
· Student Records (SR)
· Student Services Center (SSC)
HCM made up of the following modules:
· HCM Fundamentals (HCMF)
· Absence Management (AM)
· Benefits (BEN)
· Budgeting Compensation (BC)
· Core HR (CHR)
· Faculty Workload (FW)
· Payroll (PAY)
· Talent Acquisition Management (TAM)
· Time and Labor (TL)
FIN is made up of the following modules:
· Accounts Payable (AP)
· Accounts Receivable (AR)
· Asset Management (AM)
· Billing (BI)
· Budgeting (BU
· Cash Management / Treasury (CMT)
· Commitment Control (CC)
· Contracts (C)
· eProcurement (EP)
· Expenses (EX)
· Fundamentals (FUN)
· General Ledger (GL)
· Grants (GRT)
· Project Costing (PC)
· Purchasing (PUR)
· Strategic Sourcing (SS)
· Supplier Contract Management (SCM)

0 Comments

Add your comment

E-Mail me when someone replies to this comment