> 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.md). # Introduction to Parameters Parameters in SimplifyQA enable dynamic test execution by allowing testers to pass variable values into test cases instead of using hardcoded data. This feature enhances test reusability, flexibility, and efficiency, making it easier to run the same test across multiple data sets, environments, or conditions. ### Key Benefits of Using Parameters in SimplifyQA * **Data-Driven Testing:** Execute test cases with multiple inputs without modifying the script. * **Improved Reusability:** Use the same test case across different scenarios by passing dynamic values. * **Environment-Specific Testing:** Define parameters for URLs, credentials, or configurations to test across various environments. * **Easier Maintenance:** Update test data in one place without modifying individual test cases. * **Enhanced Test Coverage:** Increase test variations by using parameterised values instead of static data. By leveraging parameters in SimplifyQA, teams can create scalable, flexible, and efficient test automation workflows, ensuring comprehensive test execution with minimal effort. --- # 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.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.