---
title: "Test"
slug: "clovastudio-routertest"
updated: 2026-09-17T09:33:47Z
published: 2026-09-17T09:33:47Z
canonical: "guide.ncloud-docs.com/clovastudio-routertest"
stale: true
---

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

# Test

Available in Classic and VPC

You can test routers and decide which version to apply to your service.

## Test screen

The router test screen is laid out as follows: ![clovastudio-router_test_ko.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clovastudio-router_test_en(2).png?sv=2026-02-06&spr=https&st=2026-11-01T19%3A26%3A45Z&se=2026-11-01T20%3A26%3A45Z&sr=c&sp=r&sig=6aYtMCqwU1U8nrQ%2BskLquXQr%2BLvB1L7QE%2Bs5Gv79aXI%3D)

| Area | Description |
| --- | --- |
| ① Test area | Area for configuring and running test versions and queries. - **Version**: select the version to use for testing. - **Request test**: input what you want to test. - **[Add previous turn]** button: button to add a field where the user can enter their previous request. Only one addition is allowed at most. - **[Initialize]** button: initialize the test request and results. - **[Run]** button: executes the test. |
| ② Test result area | Area for checking test results. - **[Copy]** button: button to copy test results. |

## Run test

To run a test, follow these steps:

1. From the NAVER Cloud Platform console, click **Menu** > **All Services** > **AI Services** > **CLOVA Studio** in order.
2. From the **my product** menu, click the **[Go to CLOVA Studio]** button.
3. Click the **Router** menu in CLOVA Studio.
4. Click Router.
5. Click the **[Test]** tab.
6. Select the version to test.
7. Enter a test request.
8. Click the **[Run]** button.
9. Check the test results.

## Check test results

The following describes each field that makes up the test results:

| Item | Description |
| --- | --- |
| domain | result | Domain identification results. Empty string if no matching domain exists |
| called | Whether to perform domain identification |
| blockedContent | result | Content filter identification results. Empty list if no matching filter exists |
| called | Whether to perform content filter identification |
| safety | result | Safety filter identification results. Empty list if no matching filter exists |
| called | Whether to perform safety filter identification |

              Note

              

- If the request matches a specific domain as a result of domain identification, the filters (content filters and safety filters) set for that domain are executed. If no matching domain is found, no filters are executed.
- If the test results are inaccurate, you can improve accuracy by modifying the domain name, domain description, content filter name, and content filter description.
- Some improper or unusual inputs may cause the model not being able to recognize the intention or deciding that the classification is not proper, and it may return the domain with an empty value. If necessary, you can supplement the classification results by including explicit criteria in the domain description.