# Values (Value Store)

The Value Store in DoesQA allows you to save and access different types of values for various purposes during test execution. Values can be set and updated at different stages of the test, making it flexible and convenient for managing dynamic data.

### Value Types

The Value Store supports the following data types:

* **Strings**: Text values, such as "Hello, World!"
* **Objects**: JSON-like structures containing key-value pairs
* **Booleans**: True or false values
* **Numbers**: Integer or floating-point numeric values

### Creating Values

{% content-ref url="/pages/VXY9ifHrYArzHKaBYajy" %}
[Creating Values](/values/creating-values.md)
{% endcontent-ref %}

### Accessing Values

Values stored in the Value Store can be accessed and used in specific nodes. This allows for dynamic manipulation and utilization of data during test execution. For instance, you can use stored values to:

* Reuse values in form inputs, validations
* Pass dynamic data between steps
* Compare stored values to text on the page for validation purposes
* Use stored values in API calls or webhooks
* Make your tests more flexible, reusable, and maintainable

Remember to utilise the appropriate syntax for accessing values in the nodes where they are supported.&#x20;

You can access values by using the `$` syntax when filling in a field.&#x20;


---

# 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.does.qa/values/values-value-store.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.
