---
title: "Tests reports"
slug: "what-are-the-available-tests-reports"
updated: 2024-08-01T21:42:21Z
published: 2024-08-01T21:42:21Z
---

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

# Tests reports

Under the **Reports tab** for a **Project**, there are three available Tests reports

- Test Plan
- Steps Execution
- Planned vs. Actual
- Compliance Monitor (e-Signature)
- Test Coverage
- Testing Progress Forecast Report
- Tests and Steps trend by status
- Coverage by Users![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1722548512815.png)

**Note**

- **Planned vs. Actual,****Testing Progress Forecast Tests,****Steps Trend by Status**reports are **UTC**Timezone.

---

## **Test Plan**

Presents the Tests in your project according to module and priority, with the ability to filter the report according to your needs.

---

## **Steps Execution**

Compare the number of **planned**steps / Planned Runs to the number of **passed**steps / Planned Runs. You can view the report by the number of steps, or by the sum of effort in hours. You can click on any number in the report to view the steps list. The steps list allows you to **review**, **edit**, and **export**test steps.

**Note**

- The report does not consider steps in the **Not Applicable**status
- The due date filter relies on the step due date when it exists. Otherwise, the filter will rely on the test due date.

---

## **Planned vs. Actual** [](/v1/docs/how-to-read-the-planned-vs-actual-report)

[How to read the Planned vs. Actual report?](/v1/docs/how-to-read-the-planned-vs-actual-report)

---

## **Test Coverage**

The Test Coverage report provides a view of **all the analyzed objects**. The objects are grouped according to the SAP module and are divided into two lists, covered and not covered.

**Note** For an**Impact Analysis** project, the report will display **impacted objects only.**

Objects covered are associated with at least one test, whereas those not covered do not have any associated testing assets in the system. Unit Tests, Progression Tests, and **Functional Tests** are included in the Test Coverage report.

**How does Panaya calculate the Test Coverage?**  
Test activities are reflected in the Test Coverage report when one or more of these conditions apply:

- For [**Tests**](/v1/docs/what-are-the-differences-between-a-test-and-a-quick-test) -  
The Test**Step** includes a valid **Transaction/Fiori App**in the **Transaction field**.  
These Test activities and steps can be created manually or imported in one of the Test import methods.  
A valid transaction appears with an Information icon.

- For **Unit Tests**- Panaya automatically populates the Transaction field.

 Note****Transactions not appearing in the Transaction field, recorded using the Panaya Testing Tool, will be included in the Test Coverage report once converted to Quick Tests.  

- For **[Quick Tests](/v1/docs/what-are-the-differences-between-a-test-and-a-quick-test)**-  
If the Quick Test includes a **script** with transaction names, Panaya will consider these objects (transactions) covered.  
The script can be recorded or converted from the evidence of a previous test run.  
For **[imported](/v1/docs/how-to-import-test-assets-into-panaya) Quick Tests**imported [**from your documents**](/v1/docs/how-to-import-tests-from-files), Panaya will read the transaction names from within your files. All valid transactions will be reflected in the report.

Note

- Infotype objects are not included in the Test Coverage report.
- Coverage is calculated for Entry level objects only (i.e., Transactions)

---

  

## **Coverage by Users**

[](/v1/docs/how-to-read-the-coverage-by-users-report)

[How to read the Coverage by Users report?](/v1/docs/how-to-read-the-coverage-by-users-report) ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638972186532.png)

## Related

- [Planned vs. Actual Report](/how-to-read-the-planned-vs-actual-report.md)
- [Project Execution Plan](/project-execution-plan.md)
