# Various Types of Parameters

In SimplifyQA, parameters play a crucial role in making test cases dynamic and reusable. These parameters allow users to pass values into test cases without hardcoding them, ensuring flexibility and efficiency in test execution. 

There are three main types of parameters available in SimplifyQA:

1. **Local Parameters**

Local parameters are specific to a single test case and can only be accessed within that test case. They are useful when you need to pass values that are relevant only to the current test execution and do not need to be shared across other test cases.

2. **Global Parameters**

Global parameters are defined at the project level and can be accessed across multiple test cases within the same project. These parameters are useful when you need to maintain consistent values, such as configuration settings, credentials, or common test data, across different test cases.

3. **Runtime Parameters**

Runtime parameters are generated dynamically during test execution. These parameters store values that may change based on execution conditions, such as responses from APIs, dynamically created test data, or system-generated values. They are particularly useful for scenarios where the output of one step needs to be used as an input in subsequent steps.

By leveraging these parameter types, users can create flexible, scalable, and efficient test automation workflows in SimplifyQA.


---

# 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.simplifyqa.ai/introduction-to-parameters/various-types-of-parameters.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.