> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-failed-assertions-error.md).

# Troubleshoot Failed Assertions Error

{% hint style="danger" %}
**At a Glance**: ❌ This error in Pynt occurs when your API tests do not meet the expected conditions or outcomes, leading to failed assertions. This guide helps resolve failed assertions, improving the accuracy and reliability of your security scans.
{% endhint %}

***

## Error: The functional tests had assertions that failed, which affected the security tests.

### What Happened?

Pynt has encountered assertions while running the provided functional tests, which might effect the coverage of the security tests.

### How to Resolve?

1. **Run Functional Tests**: Run your functional tests through Postman.
2.  **Fix Assertion Errors**: Identify and fix all assertion errors in your tests before running Pynt’s security scans.

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# 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.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-failed-assertions-error.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.