# Parameterization

Parameterization is a powerful feature in Qyrus that allows users to pass data to their scripts using external data tables. This flexibility enables dynamic testing scenarios and data-driven testing, enhancing the versatility of your automated tests. it also allows user to [**skip particular step**](#how-to-skip-test-cases) by passing "\~" symbol in data table.

## How to Use Parameterization

To leverage parameterization, you can either create a data table using our **TDM** (Test Data Management) service or utilize the existing Parameterization feature. Here's how to use it:

## Prerequisites

Before you get started, ensure you have:

* Previously created a **Project**
* Previously created a **Module**
* Previously created a **Script**

**Note:** This feature is also available within Test Lab and Sprints.

1. Navigate to your previously created **Test Script** or create a new one by following the [Step creation](/desktop-testing/getting-started/build/step-creation.md) documentation.
2. After creating your steps, click on the "Parameterize" button to enable parameterization for the desired step.

![Parameterization Step 1](/files/unHxhkoMUHMullURwfzb)

3. Provide the name of the **Data Column** and save the script.

![Parameterization Step 2](/files/O7lbhyPnGFquKKoTxma5)

4. Click "Create Table" under parameterization to define your data table structure.

   ![Parameterization Step 3](/files/QVSYkL4fXlAdE8Jc97QV)
5. Populate the data table with the required information.

   * `Test_Case`: This field is mandatory and represents the name of the test case execution associated with the corresponding data. The number of rows in the "Test\_Case" column determines how many times the test script will be executed, with each execution using different data from the corresponding row. For example, if there are two rows for 'Test\_Case' as shown in the image below, the test script will be executed twice. In the first execution, the "Name" step's data value will be "Hritik," and in the second execution, it will be "Hritik Shinde."

   ![Parameterization Step 4](/files/YPB6GZWlr9IN6F7cQ14W)
6. Overview

   ![Parameterization Overview](/files/yOWOPlSjwLDv0OYFrjHn)

**Note:** Users can also use an environment created in the project setup to save parameterized tables.

7. Once the data is saved successfully, you can execute the test. Ensure you select the appropriate environment in which the data table is stored.

   ![Execute Parameterized Step](/files/YKrnVgLOMFnQFCYrojk4)
8. The test script will be executed for the specified test cases defined in the data table.

   ![Parameterization Result](/files/HrpejcQe3JRjqTlFf5Gt)

## How to skip test cases ?

* To skip test case you have to mark data column value with Tilde "\~" symbol

  ![Parameterization Skip Step](/files/UG4QwuQXQ16iSlR9PovJ)
* This will skip the particular step while execution and no operation will be perform for the test case marked as "\~"

  ![Parameterization Result Skip Test Case](/files/fNZqYDbouKZfgnOUE0iD)
* To Skip entire test case in parametrization mark test case with Tilde "\~" symbol

  ![Parameterization Result Skip Test Cases](/files/CLGaJkPtDNfO8umPUFyO)

  ![Parameterization Result Skip Test Case](/files/LqiQuKTQUoAvkHyngWEd)

## Login to sap parameterize

* In login to SAP, users need to input essential column information, including client, password, SAP system name, and username.

  ![Parameterization Login To Sap Parameterized Step](/files/bgGQklVK45YzZteSMa3B)

  ![Parameterization Login To Sap Parameterized file](/files/nwjbsQcrz7ISQE9Tr6Kx)
* To Skip a test case in login to sap in parameterize file use "\~" symbol in system name

  ![Parameterization Login To Sap Parameterized file Skip Test](/files/Wjh1IItFTJnxyMToAYFx)

  ![Parameterization Login To Sap Results](/files/ujrx36PzT36Ro4HAZmDt)

By following these steps, you can harness the power of parameterization to enhance your testing capabilities in Qyrus.


---

# 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.qyrus.com/desktop-testing/getting-started/build/parameterization.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.