Managing Test Data Queues in Orchestrator

Overview

Manage test data queues and queue items in Orchestrator. Newly created test data queues are empty but you can upload queue items based on your defined JSON schema, either directly in Orchestrator, or through Studio.

JSON Schema Definition

To create a test data queue, you need to define a JSON schema that formats the data properly. This will support uploading items to your test data queue, where the columns are the first level properties of the JSON content, as defined by your schema.

The following JSON schema example contains a root schema.

{
    "$schema": "http://json-schema.org/draft-07/schema",
    "$id": "http://example.com/example.json",
    "type": "object",
    "title": "The root schema",
    "description": "The root schema comprises the entire JSON document.",
    "default": {},
    "examples": [
        {
            "id": 1,
            "first_name": "John",
            "last_name": "doe",
            "email": "john.doe@aol.com",
            "gender": "male",
            "ip_address": "148.38.201.83",
            "skills": "UHV"
        }
    ],
    "required": [
        "id",
        "first_name",
        "last_name",
        "email",
        "gender",
        "ip_address",
        "skills"
    ],
    "properties": {
        "id": {
            "$id": "#/properties/id",
            "type": "integer",
            "title": "The id schema",
            "description": "An explanation about the purpose of this instance.",
            "default": 0,
            "examples": [
                1
            ]
        },
        "first_name": {
            "$id": "#/properties/first_name",
            "type": "string",
            "title": "The first_name schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "John"
            ]
        },
        "last_name": {
            "$id": "#/properties/last_name",
            "type": "string",
            "title": "The last_name schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "doe"
            ]
        },
        "email": {
            "$id": "#/properties/email",
            "type": "string",
            "title": "The email schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "john.doe@aol.com"
            ]
        },
        "gender": {
            "$id": "#/properties/gender",
            "type": "string",
            "title": "The gender schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "male"
            ]
        },
        "ip_address": {
            "$id": "#/properties/ip_address",
            "type": "string",
            "title": "The ip_address schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "148.38.201.83"
            ]
        },
        "skills": {
            "$id": "#/properties/skills",
            "type": "string",
            "title": "The skills schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "UHV"
            ]
        }
    },
    "additionalProperties": true
}{
    "$schema": "http://json-schema.org/draft-07/schema",
    "$id": "http://example.com/example.json",
    "type": "object",
    "title": "The root schema",
    "description": "The root schema comprises the entire JSON document.",
    "default": {},
    "examples": [
        {
            "id": 1,
            "first_name": "John",
            "last_name": "doe",
            "email": "john.doe@aol.com",
            "gender": "male",
            "ip_address": "148.38.201.83",
            "skills": "UHV"
        }
    ],
    "required": [
        "id",
        "first_name",
        "last_name",
        "email",
        "gender",
        "ip_address",
        "skills"
    ],
    "properties": {
        "id": {
            "$id": "#/properties/id",
            "type": "integer",
            "title": "The id schema",
            "description": "An explanation about the purpose of this instance.",
            "default": 0,
            "examples": [
                1
            ]
        },
        "first_name": {
            "$id": "#/properties/first_name",
            "type": "string",
            "title": "The first_name schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "John"
            ]
        },
        "last_name": {
            "$id": "#/properties/last_name",
            "type": "string",
            "title": "The last_name schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "doe"
            ]
        },
        "email": {
            "$id": "#/properties/email",
            "type": "string",
            "title": "The email schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "john.doe@aol.com"
            ]
        },
        "gender": {
            "$id": "#/properties/gender",
            "type": "string",
            "title": "The gender schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "male"
            ]
        },
        "ip_address": {
            "$id": "#/properties/ip_address",
            "type": "string",
            "title": "The ip_address schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "148.38.201.83"
            ]
        },
        "skills": {
            "$id": "#/properties/skills",
            "type": "string",
            "title": "The skills schema",
            "description": "An explanation about the purpose of this instance.",
            "default": "",
            "examples": [
                "UHV"
            ]
        }
    },
    "additionalProperties": true
}

Manage Test Data Queues

Create Test Data Queues

Log in to Orchestrator.
Open your folder.
Navigate to Testing>Test Data Queues.
Click Add test data queue.
Enter a Name for your test data queue.
Add an optional Description to help you easily identify the use of each test data queue.
Click Browse to find and upload your JSON schema.

Important: To create a JSON schema, click How do I create a JSON schema?, and see JSON Schema Definition.
Click Add to save changes.
Your test data queue is added to the list. You can start uploading items to your queue through:
- Orchestrator
- Studio

Edit Test Data Queues

Log in to Orchestrator.
Open your folder.
Navigate to Testing>Test Data Queues.
Select a test data queue and click the vertical ellipsis to open the dropdown menu.
Click Edit.
Configure your test data queue settings.
Click Update to confirm changes.

Delete Test Data Queues

Log in to Orchestrator.
Open your folder.
Navigate to Testing>Test Data Queues.
Select a test data queue and click the vertical ellipsis to open the dropdown menu.
Click Delete.
Click Ok to confirm changes.

Manage Test Data Queue Items

Manage queue items in Orchestrator to prepare your test queues for consumption.

To manage test data queue items, navigate to Testing>Test Data Queues, click the vertical ellipsis on a queue, and then click View Items.

The following table lists the actions that you can take to manage your test data queue items

Action	Description	Procedure
Upload items	Upload items to your test data queue.	In the Test Data Queues page, select a queue and click the vertical ellipsis to open the dropdown menu. Click Upload Items.
IsConsumed	The item was used in a test data queue. Items flagged as Consumed will be excluded from future test data queue runs.	In the Test Data Queues page, select a queue and click the vertical ellipsis to open the dropdown menu. Click View Items. Click the Is-Consumed box on individual items.
Set all items in the queue as consumed	Flag all items as Consumed to be excluded from future test data queue runs.	In the Test Data Queues page, select a queue and click the vertical ellipsis to open the dropdown menu. Click View Items. Click Set all items in the queue as consumed.
Set all items in the queue as un-consumed	Flag all items as Un-consumed to be included in future test data queue runs.	In the Test Data Queues page, select a queue and click the vertical ellipsis to open the dropdown menu. Click View Items. Click Set all items in the queue as consumed.
Remove	Remove an item from the test data queue.	In the Test Data Queues page, select a queue and click the vertical ellipsis to open the dropdown menu. Click View Items. Click Set all items in the queue as consumed.

On this page

Overview
JSON Schema Definition
Manage Test Data Queues
Create Test Data Queues
Edit Test Data Queues
Delete Test Data Queues
Manage Test Data Queue Items

Was this page helpful?

PREVIOUSTest Data Queues

NEXTManaging Test Data Queues in Studio

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy