What is the difference between a Unit and a Scenario?

In PerfecTwin, testing is ultimately performed by running a Scenario, but understanding how Units and Scenarios relate to each other is important when designing efficient and reusable test structures.

⚙️ How it works

A Unit is the basic building block of automation, while a Scenario is the complete test flow that connects multiple Units together.

• A Unit typically represents a single logical task, often one SAP T-Code.

• A Scenario is created by linking multiple Units to form an end-to-end business process.

For example, similar to an SD Order-to-Cash flow, a Scenario can be designed to execute:

VA01 → VL01N → VL02N → VLPOD → VF01

Each of these steps can be built as individual Units and then connected in sequence inside a Scenario.

🧩Unit

• Units are not tied to a specific Scenario.

• A single Unit can be reused across multiple Scenarios.

• If a Unit is updated, the changes are automatically reflected in every Scenario that includes it.

• As a best practice, it is recommended to create one Unit per T-Code, although a Unit can contain multiple T-Codes if needed.

🎞️Scenario

Scenarios allow you to design more advanced testing logic by combining Units, such as:

• Passing data between Units

• Conditional branching based on specific criteria

• Looping and repeated execution

When a Scenario is executed, the system records the full execution history and test results, making it suitable for formal testing and analysis.