# Testing Methodology at Portainer

### Release Testing

Before a release is initiated, the entire Portainer team dedicate time to complete comprehensive testing of the `portainerci/portainer:develop` & `portainerci/agent:develop` images.

Due to the complexity of the codebases, merged pull requests have the potential to interact with each other and cause bugs. If a bug is found, it is fixed, pushed and re-tested to ensure that the release is bug free. To get an idea of the testing that we do for a release, see the attached file below.

{% file src="<https://1754797668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L_5Fi8quGjgcLSMuygk%2F-LqoeIv_ncLq246IcVGB%2F-LqrVeng2HDaZT1n-7Xr%2FTesting%20Plan.xlsx?alt=media&token=a6cc6da0-031b-442f-8a9a-72581c07ff73>" %}
Release Testing Plan
{% endfile %}


---

# 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://portainer.gitbook.io/portainer/other-information/testing-methodology-at-portainer.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.