Proxy Mail QA

Testing predictor game scoring with many players

A scoring rule is only tested when someone earns exactly the points it's meant to give. Give each test player a different set of predictions, work out their points before the results come in, and the leaderboard tells you whether the rules work.

Updated

Why one player can’t test a game

A single test player only ever earns one score. To check that an exact score gets 3 points and a right result gets 1, that a missed deadline gets nothing, and that ties are broken the way the rules say, you need players who each take a different path through the rules, in the same round.

Plan the players before kick-off

Here’s a set for a game that gives 3 points for an exact score and 1 for the right result, with ties broken by the number of exact scores. The match finishes 2–1 to the home side.

Player Prediction Expected What it proves
A 2–1 3 points Exact score
B 1–0 1 point Right result, wrong score
C 0–2 0 Wrong result
D 1–1 0 A draw that didn’t happen
E No prediction 0 Missing entries don’t break the table
F 2–1, after the deadline 0, entry refused The deadline is enforced
G and H Level on points after a few rounds Same points The tie-break orders them as the rules say

Add a player for each extra rule your game has: double-points jokers, bonus questions such as first scorer, streaks, and private mini-leagues.

Set them up

  1. Create the players in one go. Choose Add account, set How many, label the batch with the round (“Round 7 scoring”) and tick Generate persona, so each player has a name and a username for the sign-up form and the leaderboard.
  2. Sign up and join the game as each player. Save each password on its address so you can sign back in later in the season.
  3. Enter each player’s predictions and write them in the address’s notes with the points you expect, for example “2–1 · expect 3”.
  4. Tag players by what they prove, such as exact, late or tie, so you can filter to them quickly.

What to check when the results are in

The emails to check

Deadline reminders (only for players who haven’t predicted yet), the round’s results, weekly round-ups, and winner and prize emails. Each one lands on its player’s row: open the inbox to check the scores in the email match the leaderboard, and that only the winner was told they won.

Automate it

For a game with many rounds, script the players with the REST API: create each one with POST /v1/addresses and {"label": "Round 7", "password": true}, sign them up with Playwright or Cypress, and record their picks with PATCH /v1/addresses/{address} and a notes value. Free accounts can create 50 new addresses a day.

Run these players on a staging copy of your game, never in a live competition.

Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

Create a free accountOpen the app

Questions

How many players do I need?

One per scoring rule you want to prove, plus two for a tie. Six to ten covers most predictor games: an exact score, a right result, a wrong result, no prediction, a late entry and a pair who finish level. Create them all at once, up to 50.

Can I use these accounts in a live competition?

No. Use them on a staging or test copy of your own game. Entering a live competition more than once usually breaks its rules, and using Proxy Mail QA to do it breaks ours.

How do I keep track of each player's predictions?

Write them in the address's notes with the points you expect. When the results are in, compare the leaderboard with your notes, then download the project's QA report to share what you found.

See every email testing problem we solve →