> For the complete documentation index, see [llms.txt](https://docs.qyrus.com/api-testing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qyrus.com/api-testing/api-process-testing/api-process-advanced-features.md).

# Advanced Features

### Report Actions

![image](/files/ukC0R6B7CgKEoRYbchVe)

After executing a test and viewing the report, you'll find several actions that you can perform to manage and interact with the test results.

#### Username

The "Username" section displays the name of the user who initiated the test execution.

#### Send Email

The "Send Email" action allows you to share the test report with relevant stakeholders via email.

#### Download Report

The "Download Report" option enables you to download the test report as a file. This is useful for offline review, archiving, or sharing the report outside of the testing platform.

#### Retry Test

If the test execution encountered issues or failures, the "Retry Test" button lets you initiate the same test run again. This can be helpful for retesting to verify fixes or rule out intermittent issues.

#### Delete Report

The "Delete Report" action allows you to permanently remove the test report.

#### Create Ticket

The "Create Ticket" action enables you to create a support or bug ticket directly from the test report.

![gif](/files/HpR7vHHtkVvCLNLjodht)

### Parameterized Case

#### Parameterized API Testing and Execution

![image](/files/c3PIToqf16enev0iiB8a)

In this guide, you'll learn how to perform parameterized API testing using external Excel and JSON files. You'll also understand how to configure test script connections, add connection configurations, and execute the scripts.

step-1 : Prepare an Excel or JSON or XML file with a list of input details to be parameterized and saved.

Step-2 : Implement the API request to save connections using the data from the file.

Step-3 : Execute the script and ensure the connections are saved as expected.

#### Parameterized Functional Reports

![image](/files/TAkMyNEl5B6ZUDfz0fkS)

For parameterized reports we will have individual reports for each case in Functional.

![gif](/files/MJcjQMYv8UZsl8vFwhNy)

#### Parameterized Performance Reports

![image](/files/xvordn9ds3BSqo6NlKeX)

For parameterized reports we will have individual reports for each case in Performance.

![gif](/files/FBbdpe6T4vFCLGSFtcPL)

## Path Extraction

### JSON Path Extraction

1. **Input JSON Data:**

* Users access the application and are presented with a text area or input field where they can paste or enter JSON data.

2. **Click "Extract" Button:**

* Users click the "Extract" button to initiate the extraction process.

3. **JSON Path Extraction:**

* The application processes the entered JSON data using the provided JSON Path expression.
* The extracted data based on the JSON Path expression is displayed as the response.

### Xpath Path Extraction

1. **Enter XPath Expression:**

* Users also have the option to enter an XPath expression in another input field if they want to extract data from XML.

2. **Click "Extract" Button:**

* Users click the "Extract" button to initiate the extraction process.

3. **XPath Extraction:**

* The application processes the entered XML data using the provided XML Path expression.
* The extracted data based on the XML Path expression is displayed as the response.


---

# 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 current page URL with the `ask` query parameter:

```
GET https://docs.qyrus.com/api-testing/api-process-testing/api-process-advanced-features.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.