> For the complete documentation index, see [llms.txt](https://www.neptune.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.neptune.tech/application-testing/overview.md).

# Overview

Author, run, and track automated end-to-end acceptance and regression tests for Dynamics 365 Finance & Operations — entirely from within D365, executed in the cloud.

**Application testing** is the acceptance and regression testing module of **Advanced Suite**, our Dynamics 365 Finance & Operations ISV solution. It lets you build and run automated end-to-end (E2E) regression tests — without leaving D365 and without installing or maintaining any local test runner.

You design test cases inside D365, press run, and each test executes against your environment in the cloud, exactly as a real user would: opening forms, filling fields, clicking buttons, and verifying the result. Results, screenshots, and a live video of every run are kept in D365.

## Why Application testing

* **Native to D365.** Test cases, suites, parameters, and results live in D365 — same security, same data, same place your consultants already work.
* **No local infrastructure.** No RSAT install, no Visual Studio, no machine to keep online. Each run is provisioned in the cloud on demand and torn down afterwards.
* **Isolated and repeatable.** Every run gets its own fresh browser session against your environment — no shared state between runs.
* **Watch it happen.** Follow any run live and review the recorded video afterwards.

## How it compares to RSAT

Application testing covers the same job as Microsoft's Regression Suite Automation Tool (RSAT) — replaying recorded business processes — but removes the local moving parts. There is no RSAT desktop app, no certificate juggling, and no per-tester machine setup. Test cases can even be imported from existing Task Recorder recordings.

{% hint style="info" %}
New to the terminology? Start with [How it works](/application-testing/how-it-works.md), then [Getting started](/application-testing/getting-started.md) to activate your first environment.
{% endhint %}

## In this section

* [How it works](/application-testing/how-it-works.md) — the idea in one page
* [Getting started](/application-testing/getting-started.md) — install, activate, connect an environment
* [Authoring](/application-testing/authoring.md) — build, parameterize, and organize tests
* [Execution](/application-testing/running-and-monitoring.md) — run, watch live, review history
* [Tutorials](/application-testing/tutorials.md) — worked examples, end to end
* [Price and licensing](/application-testing/price-and-licensing.md)
* [FAQ](/application-testing/faq.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://www.neptune.tech/application-testing/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.