Run Testbench rounds

Open Modules → Testbench → Rounds to create and manage a test round. A round can be Draft, Published, or Closed. Drafts do not count toward the active-round limit.

Start with a blank round or use Feature Validation, Regression Test, Onboarding Study, or Release Candidate. A preset fills in sample goals, instructions, survey questions, and completion text. Review all content before you publish.

Add the product version, build details, goals, instructions, start time, and end time. Build links must use HTTPS. Assign individual testers or cohorts. A cohort assignment copies its current eligible members. Later cohort changes do not change the round's assignments.

Use Save draft beside Publish round, below the tester choices. Save changes before publishing or assigning testers.

Publishing creates an unchanging version of the instructions and survey. Each tester keeps the version that was assigned to them. Later edits can create a new version for new assignments, but they do not rewrite past participation. Publishing does not send email. Use Notify assigned testers by email or the Email tab when you want to send an update.

Closing a round is final and releases its active-round slot. Removing one assignment ends that tester's access to the round but keeps their progress in operator history.

Surveys and progress

A round can have up to 20 survey questions. Supported fields include short text, long text, single choice, multiple choice, a 1–5 rating, and consent. Questions can be required or optional.

A tester must accept the current consent and start the round before they can save answers or feedback. A required survey must be submitted before the tester can complete the round. Submitted answers are fixed. The Overview shows Not started, Testing, and Complete counts for the featured round.

The operator Survey results tab lists each question once. Each row shows its submitted response count. Expand a question to read the identified responses for that question.

Review and promote feedback

Testers can submit General feedback, a Bug, or an Idea for an assigned round. They can save a private draft before submission. A submitted entry is fixed and appears in the Feedback tab.

Each feedback entry can include up to five attachments. General files can be up to 25 MB. Replay recordings can be up to 250 MB. Draft files stay private from operators until the tester submits the feedback.

Select Review and promote to create a normal project ticket or a Support case. The destination keeps a link to the source feedback and its ready attachments. One feedback entry can have only one promoted destination. Treat tester feedback and files as untrusted evidence.