Skip to main content
A suite is a collection of test configurations that run together as a batch. Instead of starting runs one at a time, you define which scenarios to run on which builds and devices, then execute them all at once. Think of a suite as a test matrix: scenarios on one axis, device and build combinations on the other. One execution creates a run for every combination.

​
What’s in a Suite

A suite is a saved list of items, where each item specifies:
  • Scenario — Which test plan to run
  • Build — Which version of your game
  • Device — Which device to run on
You can mix and match — run the same scenario across multiple devices, or run different scenarios on the same device. Each item becomes one run when the suite is executed.

​
Creating a Suite

  1. Give the suite a name (e.g., “Nightly Regression”, “Smoke Tests - Android”)
  2. Add items by selecting scenario + build + device combinations
  3. Save the suite for repeated use
Suites are project-scoped and reusable. Once created, you can execute the same suite whenever you need to — after a new build, before a release, or on a schedule.

​
Executing a Suite

When you execute a suite, Duzz creates one run for every item in the suite. All runs start in parallel. Each execution is tracked separately, so you can compare results across executions — for example, how this week’s nightly regression compares to last week’s.

​
Trigger Types

Suites can be triggered in different ways:
TriggerHow it works
ManualYou click “Execute” in the UI
Build uploadAutomatically runs when a new build is uploaded to the project
ScheduleRuns on a recurring schedule

​
Reviewing Results

After a suite execution completes, you get an overview of all runs:
  • Which runs passed and which failed
  • Checkpoint progress for each run
  • Links to individual run results for deeper investigation
This makes it easy to spot regressions quickly — if the same scenario passes on one device but fails on another, or passes on the old build but fails on the new one.

​
When to Use Suites

  • Regression testing — Run your full test suite against every new build
  • Cross-device testing — Verify the same scenarios work across different devices and platforms
  • Release gates — Run a defined set of tests before every release
  • Nightly runs — Schedule automated test runs overnight

​
Quick Reference

ConceptWhat it is
SuiteA saved collection of scenario + build + device combinations
ItemOne entry in the suite (one scenario, one build, one device)
ExecutionOne batch run of the entire suite — creates a run per item
TriggerHow the execution starts (manual, build upload, or schedule)