​
Overview

The End Condition step marks the end of a conditional block that was started with a Start Condition step. This step is automatically added when you create a Start Condition, but can also be added manually if needed to properly close conditional blocks.

​
Form Fields

This step has no configurable fields - it simply serves as a closing marker for conditional logic.

​
Automatic Behavior

  • Auto-Generated: Automatically added when you create a Start Condition step
  • Block Closure: Defines where the conditional execution scope ends
  • No Configuration: Requires no setup or configuration

​
Manual Usage

You can manually add an End Condition step in cases where:
  • Missing End Condition: A conditional block was left open and needs to be closed
  • Complex Nesting: You need to explicitly manage the scope of nested conditions
  • Block Restructuring: You’re reorganizing test steps and need to redefine conditional boundaries

​
Examples

​
Automatic Pairing

When you add a Start Condition: 
1. Fill username field
2. Start Condition: If error message is visible
3. End Condition (automatically added)
4. Click submit button

​
Manual Addition

When you need to close an orphaned conditional block: 
1. Start Condition: If user is admin
2. Click admin panel
3. Verify admin features
4. End Condition (manually added)
5. Continue with regular flow

​
Best Practices

​
Balanced Blocks

  • Always Paired: Ensure every Start Condition has a corresponding End Condition
  • Proper Nesting: When nesting conditions, ensure proper opening and closing order
  • Clear Scope: Keep conditional blocks focused and well-defined

​
Manual Management

  • Check for Orphans: Look for Start Conditions without matching End Conditions
  • Logical Grouping: Place End Conditions at logical breakpoints in your test flow
  • Avoid Overlapping: Don’t create overlapping or improperly nested conditional blocks

​
Common Issues

​
Missing End Condition

  • Problem: Conditional block extends beyond intended scope
  • Solution: Add an End Condition step at the appropriate location
  • Prevention: The system automatically adds End Conditions, but verify they’re correctly positioned

​
Mismatched Conditions

  • Problem: End Conditions don’t properly match with Start Conditions
  • Solution: Review conditional block structure and ensure proper pairing
  • Debugging: Use test case outline view to visualize conditional block structure

​
Incorrect Scope

  • Problem: End Condition is placed too early or too late in the test flow
  • Solution: Move the End Condition to the correct position to define proper scope
  • Best Practice: Plan conditional block boundaries before implementation