.png?alt=media)
Assertion section in request editor
Assertion section in request editor
\\
* Example 2:\
Given `param1` was set with an xml as below, any partial subset in xml-contains validation value with same structure will result pass in assertion:\
.png?alt=media)\
\
\- Using star notation to accept any value for `latitude` and `country` fields.\
\
Note, the "\*" notation works only on simple values (strings/numerics/booleans)
You may embed parameters in any assertion expression. These parameters will be evaluated right before the assertion is executed.
See **an example of the assertion** that validates the generated ID is in [the format of UUID](https://docs.loadmill.com/api-testing/test-suite-editor/functions#__is_uuid-target) below:
{% hint style="info" %}
:man\_mage: When creating tests via our [Chrome recorder extension](https://docs.loadmill.com/working-with-the-recorder), Loadmill will create **two automatic assertion types** for you:
1. Default assertions - for any extraction we find in the recorded test, we add a default assertion to it (example: "id" exists).
2. Specific assertions - for any parameter with given user key (for example, "success") we extract it and assign to it an assertion (example: "success" equals "true").
Optional automatic JSON Schema assertion: you can enable [this assertion](https://docs.loadmill.com/working-with-the-recorder/recorder-settings#strict-response-validation) within Settings - Recordings.
{% endhint %}
## Suggestions
In many cases Loadmill users use the same or similar extractions and assertions. We've implemented the Suggestions feature that allows team admins to configure a repository of [extractions](https://docs.loadmill.com/api-testing/test-suite-editor/set-parameters-extractions) and assertions within **Settings - Suggestions**.
Then, each user can add the assertions from the repository by clicking on **+ SUGGESTIONS**.
By default, there are a few common extraction and assertion examples in the repository. Team admins can also navigate to the Suggestions Settings directly from within the suggestion dialog window.
## Caveats
Keep in mind that all parameter values are **textual**, i.e. a parameter has **no type** such as `Number` or `Array` that we know from common programming languages.
This is important in order to avoid confusion when using parameter extractors such as **JSONPath**. For example, consider the following scenario:
1. Extract the value for `books` via the JSONPath query `student.books` on
```javascript
{
"student": {
"books": []
}
}
```
2. Assert `books` is **Not Empty**.
You may expect this assertion to fail but, in fact, it will succeed. This is because the parameter `books` is evaluated to `[]` and therefore is considered as a non-empty string. One possible way to correct this is to use a **RegExp** assertion on the `books` parameter instead: `\[[^\s]+\]`.