# QA testing tips and tools

## App Releases

* [Desktop App Releases](https://github.com/mattermost/desktop/releases)
* [Mobile App Releases](https://github.com/mattermost/mattermost-mobile/releases)

## E2E Tests

* [E2E Test Reference](https://developers.mattermost.com/contribute/webapp/end-to-end-tests/)

## Release Management

* [Release Management Docs](https://docs.mattermost.com/process/feature-release.html)

## Telemetry Testing

**Review the** [**Mattermost Telemetry Handbook**](https://docs.google.com/document/d/1CJeMFxnwUq8njKd3S3zxnfqrwUz8zNDsTmUAYqgy_uo/edit?usp=sharing) **for bug fixes relating to server, web-app, mobile, and/or plugin telemetry.**

The handbook contains step-by-step instructions for adding and/or updating telemetry, as well as QA-ing test data. Resources contained in the handbook include: telemetry scoping requirements for PM/Dev/QA, standardized Rudderstack development implementation processes, and dashboards to monitor test data.

## Test Servers

* [Test Server Configs and Credentials (internal resource)](https://wiki-internal.mattermost.cloud/en/quality/test-servers.md)

## Email Aliases

If you need an additional email address for testing purposes, GMail supports email aliases in the format `email+alias@domain.com`, such as `john.smith+testing@mattermost.com`. The characters following the `+` in the email address make that email unique while still ensuring that you receive that email in your inbox.


---

# 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://handbook.mattermost.com/operations/research-and-development/quality/testing-tips-and-tools.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.