/
Test User and Test Data Requirements

Test User and Test Data Requirements

Table of Contents

What is a test user?

A test user is an account that can log into the school's authentication system, and (if applicable) the SIS and LMS systems.

For example, Westeros university uses ADFS for authentication and has Banner as their SIS system and Canvas as their LMS system. Ready Education will need a test student account that can log-in using ADFS and access banner and canvas for courses information.

Why do we need a test user?

We need a test user for end-to-end testing in the mobile app. The test user is used by engineers and QA to test authentication, SIS and LMS integrations in a controlled environment prior to rolling out Production integrations to your campus.

Without a test user, our ability to test your campus app is limited. In particular, we:

  • cannot verify your school’s authentication

  • cannot verify your SIS and LMS integrations such as Courses, Bursar, Financial Aid, Holds, and Enrollment

  • cannot demo your app's integrations to you and share your progress

With a test user, we're able to do the first round testing of your campus app during activation and to debug issues that arise from support after launch. With a test user:

  • Our team of quality assurance testers verifies your integrated app.

  • Our developers have access and visibility to troubleshoot issues and edge cases during activation and post-launch

  • Your customer success agent and activation team gives demos of your app during activation

What makes a good test user?

The test data required depends on the level of your schools integration. Click on the below integration to learn about the necessary test data.

  • Authentication

  • Courses

  • Financial Aid

  • Bursar

  • Holds

  • Enrollment

Courses Test Data

For testing courses integrations, we need our test user account to be enrolled into at least one course that has entries in the SIS and LMS system. For eg. if we are integrating with your Banner (SIS) and Canvas (LMS) systems, we would need our test student account to have the following data set for us to test integrations end-to-end:

Requirements:

  1. Test User passes authentication with the required attributes (sis_id and lms_id if applicable)

  2. Test user is registered in a current semester course. This is a two-part requirement:

    • Register the test user in courses in your SIS (e.g. Banner)

    • Register the test user in the same SIS (e.g. Banner) courses in your LMS (e.g. Canvas).

    Note: The test data for courses need to overlap both your SIS and LMS system in order for the mappings to connect the integrations

  3. Add SIS test data to the test user:

    • Course Schedule (date, time, location, etc)

    • Grades e.g. final or midterm grades

  4. Add LMS test data to the test user account:

    • Assignments

    • Annoucements

    • Discussions e.g. posted discussions, and ability to reply to discussions

    • Assignment Grades e.g. quiz grade, or essay grade

Financial Integrations Test Data

  • Holds

    At least one hold of each type: administrative and financial . The Holds data resides in your SIS system. 

  • Financial Aid

    At least one award in each of these status: Offered, Accepted and Declined. Data across multiple terms is recommended. The Financial Aid data resides in your SIS system. 

    Types of data to consider:

    • Grants and Scholarships

    • Loans (subsidized, unsubsidized, PLUS loans)

    • Work Study

  • Bursar

    At least one charge and payment. Data across multiple terms/academic years is recommended for better testing. The Bursar (Account Balance) data resides in your SIS system. 

Do we need test data in production environment?

We typically start our integrations in the test/staging environment and need test user and data in the test/staging SIS and LMS systems.

Having a test user in production helps us verify integration across production SIS and LMS systems before going live on your production campus app. Keeping an active production test user and data also helps us quickly debug integrations when students report an issue.

How long do you need the test user and test data?

We recommend keeping the test user and test data active during the activation phase. Post activation, we recommend maintaining the test user with data for debugging and demo purposes.