Test configurations

Test configurations capture the environments and platforms your tests are executed against — the operating systems, browsers, hardware, or other variants where behavior might differ. They let a single test case be run and recorded across the conditions that matter for your product.

Configurations and groups

You define individual configurations and organize them into configuration groups, so the variants relevant to a product are managed together rather than as a loose list. A group might gather the supported operating systems, or the device variants a medical product ships on — whatever set of conditions your verification has to cover.

Why configurations matter

For regulated verification, “the test passed” is incomplete without “on what.” A defect might appear on one platform and not another, and your evidence has to show the test was exercised across the conditions you claim support for. Test configurations make that explicit: a run can be tied to the configuration it was performed on, so coverage is understood per environment, not just in aggregate.

How they’re used

Configurations defined here are selected when planning and executing test runs in the Tests section, so the verification record reflects not just whether something was tested, but where.