> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/test-your-integration/test-your-integration/upgrade-test-orders.md).

# Upgrade test orders

## Overview

You can use these instructions to upgrade test orders.

***

## Requirements

1. Configure at least 2 products for your account.
2. Set up one of the products as the upgrade of another.
3. Enable the test order system.
4. Place a test order with the upgradeable product.

***

## Workflow

1. Navigate to [Subscription management](https://secure.2checkout.com/cpanel/licenses_management.php) or to [Order search](https://secure.2checkout.com/cpanel/reports.php) and search either for a test subscription belonging to or a test order involving the upgradable product.
2. Click on **View** subscription to access the details page of the item you wish to trigger the auto-renewal process for.
3. Click on or copy & paste the **Upgrade test link** into your browser's address bar.
4. You will land in the shopping cart where you can place an upgrade test order. The system adds the DOTEST=1 URL parameter to the Buy Link.
5. The system updates the **Subscription history** area with the details on the upgrade test order.

***

## Possible test order status transitions

<div data-with-frame="true"><img src="https://content.gitbook.com/content/wpvpXXy7uMuuOvyKFMt1/blobs/FVaRHwQQDO7EzL0Xq8rI/testorder12.png" alt=""></div>

| Order status in search export                  | Order status in Control Panel | Approve status   | Notes                                  |
| ---------------------------------------------- | ----------------------------- | ---------------- | -------------------------------------- |
| COMPLETE                                       | Finished                      | Finished         | The order was fulfilled.               |
| AUTHRECEIVED                                   | Pending approval              | Pending approval | 2Checkout is yet to approve the order. |
| AUTHRECEIVED                                   | In progress / Processing      | In progress      | The order was approved.                |
| PENDING (for automatic authorization failures) | Unfinished                    | Unfinished       | 2Checkout is yet to approve the order. |
| TOTAL REFUND                                   | Refunded                      | Refunded         | Full refund.                           |
| PARTIAL REFUND                                 | Refunded                      | Refunded         | Partial refund.                        |

#### <i class="fa-books">:books:</i> Related documentation

* [Subscription Billing](https://verifone.cloud/docs/2checkout/Documentation/Subscription-Billing)
* [Place test orders from the Merchant Control Panel](/test-your-integration/test-your-integration/place-test-orders-from-the-merchant-control-panel.md)
* [Test payment methods](/test-your-integration/test-your-integration/test-payment-methods.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://docs.2checkout.com/test-your-integration/test-your-integration/upgrade-test-orders.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.