CHRS Knowledge Base

Using Service Now in CHRS Testing

Updated on

Overview

This job aid shows CHRS testers how to use ServiceNow to complete tests and record the results.

  • Before you start
  • Add Dashboards to Favorites
  • Find your assigned test scripts
  • Find your job aids
  • Execute a test script
  • Access the test environment
  • Record your results
  • Return to the dashboard
  • Check back

Testing flow - The flowchart shows the CHRS testing process.

flow chart of testing process

Before you start

  • Have DUO installed on your cell phone.
  • Have your cell phone nearby.
  • Install Cisco AnyConnect on your workstation.
    • Cisco AnyConnect is a virtual private network that you must authenticate with to access CHRS test systems.

Install Cisco AnyConnect - Initiate ServiceNow Ticket

Cisco AnyConnect is a virtual private network that you must authenticate with to access CHRS test systems. Follow the steps below to create a ServiceNow ticket to install Cisco Anyconnect.

  • Select your campus, then click Login.
campus login drop down menu
  • Click Send Me a Push.
duo push notification
  • Approve the DUO push on your cell phone.
    • After clicking on approve, ServiceNow will open
approve or deny icon
  • Click All > Create New
screenshot of servicenow menu "all" drop down menu
  • Complete the fields:
    • Severity: Individual
    • Urgency: Low
    • Type: Request
    • Category: CO Security
    • Subcategory: Multifactor Authentication
example of servicenow fields
  • Complete these fields:
    • Short description
    • Description
screenshot of description fields

Create Favorite Dashboard

  1. Click All.
  2. Click the star icon next to Dashboards.
favorite dashboard menu

Find your assigned test scripts

Your assigned test scripts are all on your dashboard. You should see your dashboard when you log in.  

  • Go to All > Dashboards.
dashboard menu
  • Click the Tester Dashboard tile.
    • The Tester Dashboard opens, showing your assigned tests.
screenshot of tester dashboard

Review your assigned tests

  • Columns:
    • Number: This is the test instance number. The test instance is an individual test that is assigned to you. Test numbers start with TMTI.
    • Test: Description of the test instance.
    • Due Date: The date that the test completion is due.
    • Assigned to: Your name displays here.
    • Status: The current status of the test instance. When you complete tests, you will update the status.
    • Order: The order in which the test should be executed.
    • Test Case Number: A set of related test intances make up a single end-to-end process to be tested, called a Test Case. Test Cases are maintained by project managers. You might have several test instances that belong to the same test case. Test case instances start with TMTT.  
example of tests assigned to tester
  • Open a test instance, click the test instance number.
    • The test instance opens.
example of test instance number

Find your job aids

Most test scripts are accompanied by a job aid, which provides step-by-step instructions for completing specific tasks. To successfully execute your tests, you should refer to both the test script instructions and the corresponding job aid. Additionally, some job aids include video tutorials for further guidance.

  • While viewing your test instance, copy the Job Aid URL which navigates to CHRS Knowledge Base
example of URL for end user to copy
  • Open a second browser instance to have the job aid on a separate monitor if you have one.
    • Enter the URL into a second Browser tab.
  • Optional: Click the Print button to print the job aid.
    • You can print the job aid if you have only one monitor.
example of two open browsers
printer icon

Execute a test script

To execute a test script, you need to manage multiple sources of information:

  • Follow instructions provided in the test.
  • Use any property values provided in the test.
  • Use the job aid to help with the procedure.
  • Find the Test field and Detailed Description fields.
  • Test field is the goal.
  • Detailed description can contain values or additional information.
example of test fields descriptions
  • Read the Expected result section.
example of expected results field

Access the test environment to begin testing

Start Cisco AnyConnect

Start Cisco AnyConnect Cisco AnyConnect is a virtual private network that must be running for you to access the testing environments.

  • From Windows system tray, click the Cisco AnyConnect icon to start Cisco AnyConnect.
    • If the globe icon is not visible, you might need to click the up-arrow to expand your system tray.
screenshot of glob icon
  • Click Connect.  
    • Connect to the server awsvpn.cmsdc.calstate.edu
    • After the first time, you should not need to re-enter the server information.
screenshot of Cisco connect page
  • Log in to CSU.
    • Select your campus.
    • Click Login.
screenshot of CSU login page
  • Sign in with DUO
screenshot of Duo login
  • Approve the DUO push on your cell phone or other device.
screenshot of approve DUO
  • Click Accept.
screenshot of Cisco Accept page

Log in to the test environment

Be sure you know who you are logging in as. In most cases, campus testers log in as themselves, but on some occasions, you might need to log in as another user. Check the test script for any login requirements.

  • Open the CHRS Development Environments launch page.
  • Enter HACHRSIT into the Quick Launch field at top of page, then click Go.
  • Optional Navigation: CMS CHRS > Tools 8.60 (or current version) . Project Environment > HACHRSIT (or current environment, check with PM)
screenshot of quick launch field
  • Log in:
    1. Enter your user name.
    2. Enter your password.
    3. Click Sign In.
CHRS login page
  • Navigate to your homepage
    • When you sign in, you see your default homepage.
    • This example shows the Manager Self Service homepage.
    • If you have access to other homepages, you can select them from the homepage menu at the top of the page.
    • For more information about navigating the CHRS fluid interface, view the CHRS Navigation video tutorial.
example of home page with tiles
  • Complete your test.
    • Follow the instructions in your test script.
    • Use the job aids for further guidance.
    • Note your results.

Record your results

  • Record your results on the ServiceNow Test Instance page:
    • Enter Actual Results.
    • Update the test status.
  • On the test instance page, enter your Actual Result.
  • Always enter the actual result of your test, even if the test was successful.
  • Provide detailed information especially if test failed.
actual result fields to type in results
  • Update the Status.
    • Unexecuted: The original state of the test. •
    • In Progress: You are still working on the test.
    • Passed: Finished. The actual results match the expected results.
    • Failed: Test failed because the system is not working. A ServiceNow ticket opens automatically.
    • Blocked: Test cannot be completed at this time. Work with your campus and the testing team to resolve the issue so you can continue testing.  
    • Retest: The test failed previously. The issue was fixed. The status is set to retest so you can re-attempt the test.
    • Campus Review: Use this status if your campus requires a review before determining the test results.
screenshot of status menu drop down options
  • If you select Failed, enter The Reason for Failure.
  • IMPORTANT: Include steps to reproduce the error, error messages, screenshots, or any other information that might help the CMS team identify the issue. Provide as many details as possible.
example of reason for failure text box
  • If you select Blocked, enter the Blocked Reason.
    • Provide details
screenshot of blocked reason text field
  • Optional: Click Attachments to add screenshots.
screenshot of attachment icon
  • Click Update.
    • After you click update you will return to Tester Dashboard
update icon button

Return to the dashboard

When you are on your dashboard, monitor the dashboard tiles for updates.

  • On the Dashboard, review these tiles for updates on Retests, Failed tests, Blocked tests, and Campus Review.
    • Click the number on the tile to open the list of test cases in that category. The page opens on a new browser tab.
example of tester dashboard
  • Review the Test Defects table.
    • When a test case fails, it creates an incident ticket in ServiceNow. You can see the ticket number, category, priority, and incident state from the the Test Defects area.  
    • Click the Incident Number to open the ServiceNow ticket.
    • IMPORTANT: Review the incident activities before you retest the test script.

Monitor

If any of your tests are marked blocked, failed, or campus review, you are not done yet. You need to check back to see if these issues are updated so that you can test or retest them.

If your test status is…  Do this: 
Blocked Wait for the issue to be resolved and for the test to be reset to Unexecuted.
Failed Wait for the issue to be resolved and for the test to be reset to Retest.
If your test status is…  Do this: 
Campus Review Wait for your campus to review the test as a group to provide you with additional context or instructions.

End of Article

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Previous Article (job aid) PM Role in Testing
Next Article (job aid) Requesting CHRS environment to connect to CS environment