Skip to content

Testing a Game

Luke Aeschleman edited this page Oct 5, 2017 · 3 revisions

Games automatically open and close based on their start and end time. Though this can be changed in the admin interface, many other site variables are based on these times. For example, when registration is open it displays the start time, which is based on the entry in the database.

Testing Local and Dev environments

Since these environments are not meant for public consumption, you can simply change the start and end times of the game you want to test. Or you can follow the process below replacing the clue.unc.edu subdomain with the dev or local domain.

Testing Production Game

We don't want to adjust the start and end times of an upcoming/production game. So there is a workaround that allows admins to temporarily activate the game interface on a single device.

  1. Create a test team. This team can be on the waitlist
  2. Add the person who will be testing the game to the team. This is the "game-tester"
  3. On the device you want to use to test the game, go to https://clue.unc.edu/test-game
    • Note: This url will only work if there is an active game.
  4. You will be prompted to enter your administrative username and password.
    • Essentially, you are "approving" the test-game on this device
  5. Then you will be prompted for the game-tester's username and password.
    • The game-tester is logging in as normal

Once the logins are complete, the game-tester can use the interface normally.

Clone this wiki locally