Skip to main content
A simulation in test mode is played by a small group of testers before trainees see it. Their runs, thumbs and survey answers collect into numbered rounds. This page covers the people and the rounds: who tests, how much, by when, and what you can do to a round. What happens with their feedback is in Reviewing and Approving Changes.

​
The tester course

Every mini module gets a tester course when its build finishes. It is named after the simulation with - testing on the end and lives under Courses like any other course. Testers are whoever is assigned that course.
The tester course under Courses, with a Test Mode section and the simulation as its one lesson
The course’s Test Mode section is what puts it in the testing loop. Reddy turns it on when the module is built and off when the module graduates. You can use the same switch on a course you made yourself to put any simulation, including a Reddy-built one, into a testing round.

​
Assigning testers

1

Open the tester's profile

Go to Employees and click the person’s name. Their side panel opens.
2

Add the tester course

Under Courses, pick the simulation’s tester course. The assignment saves straight away and the tester is notified.
Employee side panel for Pam Beesly with the tester course listed under Courses
A tester needs the simulation’s product on their profile as well as the course. Product access is set in the same panel under Products. See Assigning Products and Managers.
Testers added after a round has started join the current round. Removing the course from someone takes them out of future rounds; what they already said stays in Results.

​
What testers see

The tester course appears on the tester’s dashboard marked Test mode, with the acceptance rule for the round: play at least the minimum number of times, up to the maximum.
A tester's dashboard showing the testing course in test mode with the rule Test at least 1 time, up to 2
Start opens the simulation exactly as a trainee would see it. Testers leave a thumbs up or down on the customer’s lines during the call and fill in the survey afterwards.
The retention simulation as a tester sees it before starting the call
Once a tester has reached the maximum runs for the round, the lesson locks for them until the round moves on. That keeps everyone testing the same version.

​
Runs, deadlines and reminders

These live on the Settings tab of the Simulations area. Runs per tester and approvers are per simulation; deadlines and reminders apply to every tester.
Simulation settings: a program card with name, cadence, minimum new feedback, runs per tester and approvers, then deadlines and reminders

​
Following a round

Open the simulation and click Testing. The round card shows where the round is, runs collected, testers done, the next deadline and the last update that shipped.
Testing tab during round 1: one of two runs collected, one tester done, the other in progress with a due date
The Testers table shows each person’s status in this round and their record across rounds: Click a tester to read their feedback. Previous rounds keeps every earlier round with its window, testers, runs, thumbs down and what shipped from it.
Round 2 open with testers in progress and round 1 listed under Previous rounds

​
Managing a round

Each one asks you to confirm first.
Kill round 3? confirmation dialog

​
FAQ

There is no minimum. A round closes when every assigned tester has met the minimum runs, so a round with one tester closes after one run. Two or three testers give Reddy more to read.
No. Deactivated users drop out of the round. If a tester is still active but never plays, kill the round or remove the course from their profile.
Yes. Make a course with the simulation as a lesson, tick Enable test mode on the course, and assign testers. It gets a Testing tab and rounds like a mini module.
Either they have reached the maximum runs for this round, or an update is shipping. The lesson unlocks when the next round opens.