Creating a good test user is the single most important thing you can do to help the campus app succeed -- don’t delay!
What is a test user?
A test user stands in for your students during creation of the campus app. It is a fictitious student, not associated with any real person. A test user has fictitious courses, grades, and assignments.
A test user has a username and password. Anyone who knows the username and password of the test user can log in to the app as if they were that student. They can also go to My Profile, view the test data and interact with it.
In technical terms, a test user is a series of entries in your school’s authentication database, associated with entries in the Student Information System (SIS) and Learning Management Systems (LMS).
What is a test user for?
A test user lets Ready Education build a custom adaptor to connect your school’s databases to the campus app. It lets us verify that the adaptor works, and do acceptance testing.
Without a test user, our ability to test your campus app is limited. Without a test user:
- We cannot verify your school’s custom app integrations.
- We cannot see your app in action and develop support materials accordingly.
- We cannot demo your app to you and share your progress.
By contrast, 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.
- Your customer success agent gives early demos of your app.
- Our training specialist develops materials tailored to your school.
Making a good test user is the single most impactful thing you can do to ensure your campus app is a success. Here’s how:
- Create an entry in your school’s authentication database
Create associated entries in the SIS and LMS systems
Ensure the test user has a valid time frame
Check your work
- Submit your test user to Ready Education
1. Create an entry in your school’s authentication database
DONE BY: Campus IT
Your school maintains a database of student usernames. If you have an entry in that database, and know the password, you can log in to all school systems. This is sometimes called a “Single Sign On” (SSO). Other kinds of authentication are LDAP, SAML or Google Authentication.
We require an entry in your school’s authentication database. Ask campus IT to create a username and password. Then communicate the username and password by submitting a request at Ready Education Help Center
2. Create student data in the SIS and LMS systems
DONE BY: Campus IT
In addition to the authentication database, your school maintains smaller databases such as the Student Information Systems (SIS) and Learning Management Systems (LMS). Some examples of SIS are Banner, Jenzabar, and Peoplesoft. Some examples of LMS are Blackboard and Moodle.
The campus app integrates with these systems to provide information like courses, grades, and assignments.
- An entry in the SIS database
- An entry in the LMS database
The entry in the SIS database should be a typical user, with all the information that would be associated with a real student.
The entry in the LMS database must be associated with one course, one grade and one assignment.
These users must be associated with the test user in the authentication database.
3. Ensure the test user has a valid time frame
DONE BY: Campus IT
Ready Education works year round to provide a high standard of quality of your app. Having continued, uninterrupted access to the test user is important to resolving issues quickly and efficiently for you.
Ready Education must be able to log in with the test user, and access SIS/LMS data, for a minimum of six months. If you can provide indefinite access, we highly recommend it. An expired test user can add hours or days to the resolution time of critical bugs.
4. Check your work
Before submitting the test user to Ready Education, check your work. Problems with a test user can easily snowball and can put your app launch at risk.
- Log into to the authentication system using the test user’s username and password. Ensure the test user can log in.
- Log in to the individual LMS and SIS systems. Ensure the test user can log in to each individual system, and test data is present in each.
5. Submit your test user information
For More Information
If you have any questions about test users, please visit Ready Education Help Center
BEST PRACTICE: Give ownership of the test user to campus IT. Have them document the various entries in the authentication, SIS and LMS databases. It will be an invaluable resource if you ever need to troubleshoot your own campus app integrations.
If you have comments or feedback about this "how-to" document, please leave them in the comments below. Thanks for reading!