> For the complete documentation index, see [llms.txt](https://docs.sprintsq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprintsq.com/test/test-data.md).

# Test Data

Test data in SprintsQ is essential for reusing data across multiple tests, ensuring efficiency and consistency. When you edit test data, the changes automatically propagate to all associated test cases.

**Types of Test Data in SprintsQ:**

* **Text:** This type can hold any text-based information such as page URLs, element names, test credentials, and more.
* **State:** A 'state' captures all relevant data like cookies and local storage from a webpage. To record a state, you must replicate the same navigation steps as when creating a test case. For instance, modern web applications typically store user information in cookies and local storage, enabling automatic login without re-entering credentials. Utilizing 'state' test data can bypass repetitive login steps across test cases.

**Creating Test Data:**

1. Select the 'Test Data' option from the left panel.
2. Click on the '+Test Data' button to start the process.

*Notes:*

* Users must possess the appropriate permissions with 'test data creation' rights to create test data.
* The values within a 'state' type are not visible to the users for security and privacy reasons.

By using test data effectively, you can streamline your testing process and avoid unnecessary repetition in your test cases.


---

# 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.sprintsq.com/test/test-data.md?ask=<question>&goal=<endgoal>
```

`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.