All Products
Search

This Product

    DataWorks:Run tests and view test instances

    Document Center

    DataWorks:Run tests and view test instances

    Last Updated:Apr 23, 2026

    A test instance is generated when you run a test on a scheduled task. On the test instance page, you can view the instance details in a list or a DAG.

    Introduction

    You can run a test on a scheduled task to verify that its scheduling and execution meet expectations in the production environment. This generates a test instance, letting you monitor its run status on the test instance page.

    Note

    Running a test instance executes the actual code logic. Proceed with caution.

    Limitations

    • Feature limitations:

      • DataWorks Professional Edition and higher provide the following advanced features to improve your development and O&M efficiency. For more information, see Editions and billing.

        • Run Diagnostics: Helps you quickly locate task run issues. This feature is available for a free trial. For more information, see intelligent diagnosis.

        • Advanced DAG analysis: Includes node aggregation, upstream analysis, and downstream analysis to help you gain insights into complex task lineage.

        • Export Query Results: Allows you to use data for external reports or further analysis.

      • Only users with O&M permissions can use some features. If a feature is grayed out or unavailable, go to the Management Center overview page. In the navigation pane on the left, click Workspace Members and Roles, and on the Workspace Members tab, verify that the target user has O&M permissions. For more information, see Manage permissions for workspace-level modules.

    • Log and instance limitations:

      • You cannot manually delete test instances. Instances are automatically deleted by the platform after they expire (approximately 30 days). If a task no longer needs to run, you can freeze the instance.

      • For shared resource groups for scheduling, instances are retained for one month (30 days) and logs are retained for one week (7 days).

      • For exclusive resource groups for scheduling, task instances and logs are retained for one month (30 days).

      • Logs of completed instances that exceed 3 MB are cleaned up on a daily basis.

    • After you configure the maximum number of concurrent instances for a task, test instances are also subject to this limit and share the concurrency quota with scheduled instances and backfill instances. When multiple types of instances are queued simultaneously, only backfill instances that are not for the current day have their priority downgraded (from 8 to 3).

    Run a test and generate a test instance

    1. Go to Operation Center.

      Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Development and O&M > Operation Center. On the page that appears, select the desired workspace from the drop-down list and click Go to Operation Center.

    2. Run a test on a scheduled task.

      On the Operation Center page, in the left-side navigation pane, click Auto Triggered Task O&M > Auto Triggered Node. On the Auto Triggered Node page, you can run a test on a scheduled task by using one of the following methods.

      • Method 1: In the list view of scheduled tasks, click Test in the Actions column of the target task. If the current page is not in list view, click the Arrow icon icon in the middle of the page to return to list view.

      • Method 2: In the DAG view, right-click the DAG of the target instance and click Test from the context menu. If the current page is not in DAG view, click DAG in the Actions column of the target instance to open the DAG of the task.

    3. Configure the parameters in the Test dialog. image

      Parameter

      Description

      Test Name

      You can enter a name for the smoke testing.

      Data Timestamp

      Select the business date for the test.

      Note

      • If you select a business date earlier than yesterday, the task runs immediately.

      • If you select yesterday as the business date, the task runs at the scheduled time.

      Advanced configuration

      After you enable advanced settings, you can assign values to scheduling parameters. The assigned values take effect only for the current test.

    View the list of test instances

    The test instance list displays test instances generated after you run tests on scheduled tasks. You can view the execution status of test instances and perform related operations on them.

    List icon

    Operation

    Description

    Filter

    In area 1 of the preceding figure, you can use filter conditions to filter out the instances you want to query.

    You can filter instances by Node Name, Node ID, Task type, Run At, Data Timestamp, Scheduling Resource Group, My Node, The node I tested today, and Pause (freeze) a node.

    Note

    The default business date for filtering is the day before the current date.

    Tasks

    In area 2 of the preceding figure, test instances that meet the filter conditions are displayed in a list.

    Actions

    In area 3 of the preceding figure, you can perform the following operations on test instances:

    • DAG: The DAG displays the upstream and downstream dependencies of a test instance. You can perform related operations in the DAG. For more information, see Manage DAGs.

    • Diagnostics (Run Diagnostics): Used to perform end-to-end analysis on a task. When a task does not run as expected, you can use this feature to locate the issue. For more information, see Intelligent diagnosis.

    • Rerun: Used to rerun a task that has succeeded or failed. After the task runs successfully, it can trigger the scheduling of downstream tasks that are in the not-run state. This is commonly used to handle failed or missed nodes.

      Note

      You can rerun only tasks in the Successful or Failed state.

    • More:

      • Rerun Descendent Nodes: Used to rerun downstream nodes of a task that has succeeded or failed. You can select the downstream tasks to rerun. After the task runs successfully, it can trigger the scheduling of downstream tasks that are in the not-run state. This is commonly used for data repair.

        Note

        You can rerun only tasks in the Successful or Failed state. If you select tasks in other states, the page displays a message indicating The Selected Nodes Include Nodes That Do Not Meet the Run Conditions, and the run submission is blocked.

      • Set to Successful: Used to set a failed task to the successful state. When a task fails but you do not want it to block downstream tasks, you can use this feature. This is commonly used to handle failed nodes.

      • Terminate: Used to terminate a task that no longer needs to run. After the task is terminated, it exits with a failure status.

        Note

        You can terminate only instances in the Waiting time, Waiting for resources, or Running state.

      • Freeze: When a task and its downstream tasks do not need to run for a period of time, you can use this feature. For more information, see Freeze and unfreeze instances.

        Note

        Do not perform operations on the projectname_root node. This node is the root node of the workspace. All scheduled task instances depend on this node. If you freeze this node, scheduled task instances cannot run.

      • Unfreeze: Used to unfreeze an instance that is in the frozen state.

        • If the instance has not run yet, it runs automatically after its upstream tasks finish running.

        • If all upstream tasks have finished running, the instance is directly set to the failed state. You need to manually rerun it for the instance to run normally.

        Note

        The unfreeze operation applies only to the specific instance. If the scheduled task is still in the frozen state, the instances generated the next day will still be in the frozen state.

      • View Lineage: View the lineage information of the current instance.

      • View cycle task details: View the basic information of the current instance.

      • View Runtime Log: After a task starts running, you can view its detailed execution process in the runtime log. For descriptions of key parameters in the logs, see Runtime log parameters.

    Batch operations

    In area 4 of the preceding figure, you can select multiple tasks in batches and perform operations such as Terminate, Rerun, Set to Successful, Change Resource Group, Freeze, Unfreeze, and Export Query Results.

    Items per page

    In area 5 of the preceding figure, you can change the number of items displayed per page. A maximum of 200 items can be displayed per page.

    Test instance DAG

    In the list view, click the Test Instance name or click DAG in the Actions column to open the DAG of the instance. You can right-click an instance in the DAG to perform related operations. DAG diagram

    Feature

    Description

    DAG panel features

    Click DAG next to a task to open its DAG. You can perform the following operations in the DAG:

    • Search: In area 1 of the preceding figure, you can filter instances by Node Name, Node ID, Instance ID, Instance Name, and more.

    • Select DAG Display Style: In area 2 of the preceding figure, you can click the feature icons in the upper-right corner of the DAG view to adjust the display style as needed. From left to right: Open Map/Close Map, Show Alert Status/Hide Alert Status, Update Node Status, Zoom In DAG canvas, Zoom Out DAG canvas, 1:1 layout ratio between nodes and canvas, Auto Fit Screen based on the current window size, and Toggle Full Screen View toggle.

    Single instance operations

    Right-click the target node to perform related operations.

    • View Code: Used to verify the code of the current node in the production environment. If the code does not meet expectations, check whether the latest version of the node has been deployed successfully.

    • Edit Node: Click to go to the Data Studio page and open the current node.

    Note

    For other operations, see View the list of test instances.

    Single instance details

    In area 4 of the preceding figure, you can perform the following operations:

    • View Log Data: After a task starts running, you can view its detailed execution process in the runtime log. For descriptions of key parameters in the logs, see Runtime log parameters.

    • Show Details: Used to view information about the current task, including properties, context, runtime log, operation log, and code. For more information, see View instance details.

    View instance details

    In the DAG view, click the target instance. In the window that appears in the lower-right corner, click Show Details. The instance details page appears, where you can view detailed information about the current instance, including properties, context, runtime log, operation log, and code.

    View instance details

    Feature

    Description

    General

    On this tab, you can view the scheduling properties of the task in the production environment. For descriptions of the parameters on the page, see Configure schedule settings.

    • Task status interpretation: The task status is related to the task run. If a task is in the not-run, waiting time, waiting for resources, or frozen state, see Troubleshoot task status issues for troubleshooting.

    • Time spent waiting for resources: If a task has been waiting for resources for a long time, you can use the intelligent diagnosis feature to identify which tasks are occupying resources when the current task runs, and quickly locate abnormal tasks for troubleshooting.

    • Excessive duration: If the task duration is significantly longer compared to historical runs, refer to the following scenarios for troubleshooting.

      • Non-synchronization tasks: Contact the person responsible for the corresponding compute engine.

      • Batch synchronization tasks: A specific phase of the task may be running slowly or the task may be stuck in a prolonged waiting-for-resources state. For more information, see Troubleshoot batch synchronization tasks.

    • Monitoring rules: You can view the monitoring rules associated with the current instance. Click Create on the right side to quickly create a monitoring rule for task run status. For more information, see Create a monitoring rule.

      Note

      Only monitoring rules for task run status can be viewed here. Data Quality monitoring rules are not supported.

    • Baseline monitoring: You can view the baselines associated with the current instance. Click Create on the right side to quickly create a baseline. For more information, see Manage baselines.

    • Maximum number of concurrent instances: Displays the maximum number of concurrent instances configured for the task. The value is Unlimited or a specific number (1 to 10000). This setting limits the maximum number of instances of the same task that can run simultaneously. The limit applies to scheduled instances, backfill instances, and test instances.

    Runtime Log

    After a task starts running, you can view its detailed execution process in the runtime log. For descriptions of key parameters in the logs, see Runtime log parameters.

    Operation Log

    Used to view the operation records of a task or instance, including the time, operator, and specific operation.

    Code

    Used to view the latest code of the current task in the production environment. If the code does not meet expectations, check whether the latest version of the task has been deployed successfully. For more information, see Deploy nodes.

    Troubleshoot task run issues

    If a task does not run as expected, you can use the intelligent diagnosis feature to diagnose the reasons why the task did not run or identify issues.