--- title: "Test ticket ballots and prize draws with many test accounts · Proxy Mail QA" description: "Check entry rules, priority for members, the draw, payment windows and the emails winners and non-winners get, with a batch of test entrants on your own ballot or draw." url: https://proxymail.qa/use-cases/ballots-and-prize-draws --- 1. [Home](https://proxymail.qa/) 2. [Use cases](https://proxymail.qa/use-cases) # Testing ticket ballots and prize draws A ballot is only tested when it has enough entrants for some to win and some to lose. Create a batch of test entrants, give some of them priority, run the draw on staging, and check every entrant hears the right news. Updated October 13, 2026 ## The entrants you need | Entrant | Set up as | What it checks | | ---------------------- | --------------------------------------------- | -------------------------------------------------------- | | Priority member | Top tier, or the most loyalty points | Priority entry or better odds, as your rules say | | Member | A member with no priority | The normal path | | Non-member | Registered, no membership | Let in, or kept out of a members-only ballot | | Duplicate | The same person entering twice | The second entry is refused or merged | | Late | Enters after the ballot closes | Refused, with a clear message | | Group | Enters with friends, if your ballot allows it | The group wins or loses together | | Winner who doesn’t pay | Wins, then ignores the payment link | The window closes and the tickets go to the next in line | Add enough plain members to make the draw real: with more entrants than prizes, some must lose. ## Set them up 1. **Create the entrants at once.** Choose **Add account**, set **How many** (up to 50), label the batch with the ballot’s name and tick **Generate persona**. 2. **Sign up as each** and give it its membership or points in your staging admin. 3. **Tag each by type**, such as `priority`, `member` or `non-member`, and note anything else, such as “Group with k3f9 and x7aa”. 4. **Enter the ballot as each one**, then run the draw on staging. ## What to check - **Entry rules:** one entry per person, the closing time, and who’s eligible. - **The draw:** priority and weighting work as described, and groups stay together. - **Payment windows:** a winner’s payment link works once and only within its window; when it closes, the next entrant is offered the tickets. - **Results:** every entrant hears, nobody hears twice, and nobody is told both that they won and that they didn’t. ## The emails to check Entry confirmation, results for winners and non-winners, payment reminders, “your window closes soon” and waiting-list offers. Open an entrant’s inbox to read their result and find the payment link. We never open links, so a single-use payment link still works when you click it. ## Automate it For bigger draws, script the entrants with the [REST API](https://proxymail.qa/docs/api): create each with `POST /v1/addresses`, sign them up and enter them with Playwright or Cypress, and tag them with `PATCH /v1/addresses/{address}`. Keys allow 60 requests a minute on the Free plan. Use test entrants only on a ballot or draw you run or are allowed to test, in development, staging or QA. ## 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 account](https://app.proxymail.qa/?mode=signup) ## Questions ### How many entrants can I create? Up to 50 at once in the app, and 50 new addresses a day on the Free plan. If your app treats plus-addresses as different people, name+1@mailclub.dev, name+2@mailclub.dev and so on are separate entrants whose mail all arrives in one inbox, with the tag shown on each email. ### Can I enter real ballots with these accounts? No. Entering a real ballot or prize draw many times breaks its rules, and ours. Use test entrants on a staging copy of your own ballot. ### How do I check every entrant got their result? After the draw, filter the Accounts page by the batch's tag: an entrant whose row still shows the entry confirmation hasn't had a result. The project's QA report lists every email each entrant received, with times, as a CSV. ## Related guides - [Test age gates and age-restricted contentOne account per age band, from under 13 to turning 18 tomorrow, with parental consent emails and each date of birth noted.](https://proxymail.qa/use-cases/age-restricted-content) - [Test content that depends on locationAn account per country for geo-blocked content, regional prices, tax and consent, and a traveller who crosses a border.](https://proxymail.qa/use-cases/location-based-content) - [Test predictor game scoringA player for every scoring rule, with picks and expected points in the notes, so the leaderboard proves the rules work.](https://proxymail.qa/use-cases/predictor-games) - [Test membership tiers and paywallsFree, trial, paid, top-tier and lapsed accounts, and every subscription email from welcome to payment failed.](https://proxymail.qa/use-cases/membership-tiers) - [Test roles and permissionsOwner, admin, editor, viewer, removed user and another customer’s admin, each invited by email and signed in for real.](https://proxymail.qa/use-cases/roles-and-permissions) - [Test referral rewards and welcome offersReferrer, friends and first-time customers, plus the self-referral and repeat claims your rules should refuse.](https://proxymail.qa/use-cases/referrals-and-welcome-offers) - [Test both sides of a marketplaceBuyer, seller, a second buyer and a moderator, so every order, message, refund and review email is checked from both ends.](https://proxymail.qa/use-cases/marketplaces) - [Test email changes, lockouts and account deletionAn old and a new address for change of email, plus accounts to lock out, reset, protect with codes and delete.](https://proxymail.qa/use-cases/account-changes) - [Test email preferences and unsubscribeAn account per preference setting, to prove opted-out users get nothing and unsubscribe works in one click.](https://proxymail.qa/use-cases/email-preferences) [See every email testing problem we solve →](https://proxymail.qa/solve)