> For the complete documentation index, see [llms.txt](https://docs.simplifyqa.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplifyqa.ai/introduction-to-parameters/understanding-runtime-parameters.md). # Understanding Runtime Parameters Runtime Parameters are dynamic inputs that can be passed to test cases during execution. These parameters provide flexibility, allowing you to reuse test cases with varying values and conditions, without having to modify the test steps or scripts. They are essential for automating tests in different environments, with different data, and in various scenarios. ### What are Runtime Parameters? Runtime Parameters are variables that you can set and use within your test cases during execution. They help in customising test runs based on specific inputs that are defined at runtime, rather than hardcoding values into the test scripts. ### Key Features of Runtime Parameters * Dynamic Inputs: They can be provided at runtime and vary between executions. * Test Reusability: Test cases can be reused with different sets of data. * Environment Flexibility: You can run tests in different environments (e.g., UAT, Production) by passing different parameter values. * Seamless Integration: Allows integration with data-driven testing approaches by dynamically feeding data into tests. * Scalability: Easily scale your tests by running them with different parameter values without changing the core test logic. ### Creating Runtime Parameters in SimplifyQA To use runtime parameters effectively, follow these steps: #### 1. Create a Runtime Parameter * Navigate to Test Management > Parameters. * Click on '+ Parameter', then enter a name and select a parameter type as 'Runtime'. * If you want the parameter keys to be unique, enable the "Make Unique" field and click 'Save'.

2. **Understanding the 'Make Unique' Field** When creating a runtime parameter, selecting 'Make Unique' will open a dropdown with the following options: This option is used to make the runtime parameter keys unique by appending below options:


OPTION	DESCRIPTION	EXAMPLE OUTPUT
_TestcaseID	Appends the Test Case ID to the key.	testUser_12345
_UserID	Appends the User ID to the key.	testUser_56789
_UserID_TestcaseID	Combines User ID and Test Case ID.	testUser_56789_12345
_TestcaseID_UserID	Combines Test Case ID and User ID.	testUser_12345_56789

**Use case:** If multiple test cases run in parallel, enabling this feature ensures that each parameter remains unique, preventing duplicate runtime values. 3. **Using Runtime Parameters in a Test Case (For example)** * Navigate to a Test Case: Go to Test Management > Test Cases and open a test case. * For Example: Use 'Get Text and Store' action which fetches the text from UI and stores to runtime parameter. * Add a step to your test case where you need to capture a value dynamically. * Select the action: "Get Text and Store". * Provide a Runtime Parameter Name (e.g., CapturedOrderID). * Use the Stored Parameter in another Step: * In a subsequent step, reference the runtime parameter as “CapturedOrderID” * Example Use Case – Capturing Order ID Dynamically


STEP	ACTION	INPUT	OUTPUT
1	Navigate to Order Page	URL	-
2	Get Order ID from UI	XPath: //span[@id='orderID']	Store in ${CapturedOrderID}
3	Type Text or Validate Text	Input: ${CapturedOrderID}	-

This ensures that every order ID is dynamically captured and reused throughout the test. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.simplifyqa.ai/introduction-to-parameters/understanding-runtime-parameters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.