Overview and Best Practices for Testing

To learn the basics, watch these short videos, including an interactive practice testing session:



Continue with...

...Testing Demonstration:

...Proctor Practice


Best Practices for Testing Sessions

  • Ensure the lab is ready at least a day ahead

    Use the Lab Readiness Checklist (1 page).

  • Assign the test for each student

    Test assignment is a step you take during setup, and it relieves students from having to choose the test themselves. See also: Test Descriptions—Summary.

  • Limit the number of students in a session

    The testing session is the software feature that controls who can test—and how many. Adding too many students in the testing session (100+) becomes hard to manage. Try limiting to the students you have in the lab on a given day.

  • Naming testing sessions:

    • Keep it short and easy for students to type
      • Avoid spaces, special characters, and ambiguous letters like "l"
    • Make sure the names are unique by using a convention:
      • Example policy for naming testing sessions:

        <instructor initials><subject><grade><period>
      • Example name based on this format:

        <     J.B.          >< math  ><  7  ><  2   >

  • In large groups, do not start everyone at once

    If too many students join simultaneously, network performance could degrade. Have students sign in a few at a time.

  • Give early learners a break mid-way

    After about 25 minutes, interrupt testing to give students a rest (see Suspend Tests ).

back to top >>