When to use COMMON and CASE ​

Recommendation on how to split setup and the checked scenario in ComplexQA: kind COMMON and kind CASE.

Why ​

The same sign-in or section entry repeats across many scenarios. Copying those steps into every CASE costs more than extracting them into a COMMON predecessor. Only a CASE with status READY enters the autotest run queue.

How to work ​

1. Model repeated setup (sign-in, open a section, base data) as an autotest of kind COMMON.
2. Set the COMMON status to READY when the setup is stable.
3. Model the checked scenario as a CASE: unique steps after setup.
4. On the CASE card, open Pre autotest cases and list COMMON predecessors in order.
5. Bind a test account to the CASE when you need login / password. Kind COMMON has no account; TEST_ACCOUNT steps inside COMMON read that CASE account.
6. For an autotest run, select only the needed READY + CASE items.

The hint under the block title states: those COMMON autotests run first in the same browser session, in that order; nested predecessors are not expanded; COMMON itself does not enter the run queue.

Creation: Autotest creation. Field model: Autotest.

What to avoid ​

JSON import does not set kind COMMON or predecessors: change the kind after import yourself. Breakdown: How to author autotest steps without false failures.

Kinds named SHARED, SETUP, or SCENARIO do not exist in the product.