# Synchronizing Scenario Outlines

Scenario Outlines can be used to specify business rules that can be represented with a table of input-output pairs. The following example shows a scenario outline for specifying the addition function of a calculator.

```
Scenario Outline: Add two numbers
    Given I have entered <a> into the calculator
    And I have entered <b> into the calculator
    When I press add
    Then the result should be <result> on the screen

Examples: 
    | description   | a  | b  | result |
    | classic       | 50 | 70 | 120    |
    | commutativity | 70 | 50 | 120    |
    | zero          | 0  | 42 | 42     |
```

This scenario outline represents three executable tests, one for each row of the `Examples` table.

The kind of test cases that are created in Jira for scenario outlines depends on the Test Case Management solution used.

| TCM solution           | Scenario Outline representation                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Jira TCM Customization | A Test Case issue is created with the scenario outline examples included as a table to the scenario description. |
| Zephyr Scale           | A Test Case is created with the scenario outline examples included to the *BDD Script* field as Gherkin.         |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.specsolutions.eu/specsync/jira/features/push-features/synchronizing-scenario-outlines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
