---
title: "Run Tests - Lasernet FO Connector Test and Performance Suite Guide"
slug: "run-tests"
description: "Tests can be executed manually, in the background (as a batch job), or using test automation (RSAT). Read for more information."
updated: 2026-03-03T14:47:52Z
published: 2026-03-03T14:47:52Z
canonical: "kb.lasernetgroup.com/run-tests"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Tests

Tests can be executed manually, in the background (as a batch job), or using test automation (RSAT). Refer to the [Integration with RSAT](/v1/docs/integration-with-rsat) section of this guide for more information on test automation.

A test can be executed manually or in the background using a batch job by navigating to:

- **Lasernet** > **Test and performance suite** > **Test** > **Test checkpoints**, select a Test checkpoint, and then click **Run test**.
- **Lasernet** > **Test and performance suite** > **Test** > **Test flows**, select a Test flow, and then click **Run test**.
- **Lasernet** > **Test and performance suite** > **Test** > **Run test**

A Test checkpoint or a Test flow can be run from this dialog.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (34)(5).png)

The **Checkpoints** section displays more detailed information about the selected Checkpoint. Multiple Checkpoints maybe listed here if a Test flow is selected.

- Set the **Open review form** toggle to **Yes** to open the **Test results** form after the test is run, so test results can be reviewed.
- The **Run in the background** section can be used to create a batch job for background processing.
  - Set the **Batch processing** toggle to **No** to run a manual test.
  - Set the **Batch processing** toggle to **Yes** to run a background test. This batch job uses standard Dynamics functionality.

When a test is run, a comparison is made between the elements and structure in the Test checkpoint XML file and the Test result XML file. The Test checkpoint PDF file and the Test result PDF file are also compared if **Compare PDF** is set to **Yes** on the Test checkpoint. The test result is then saved so that it can be viewed later.