Run smoke testing in the development environment to verify a node before deploying it to production. Smoke testing checks three things:
Whether scheduling parameters are correctly substituted.
Whether upstream and downstream dependencies are wired correctly.
Whether the node produces the expected output.
In a standard workspace, smoke testing runs in an isolated development environment. Even when a node writes data, your production data is not affected.
Prerequisites
Before you begin, make sure you have:
A node under development in Data Development
Workspace administrator access (required only to enable Force smoke testing)
Enable Force smoke testing
Workspace administrators can turn on Force smoke testing to require every node to pass smoke testing before it can be deployed to production.
Force smoke testing is not available for workspaces in basic mode.
In the left navigation pane of Data Development, click the
icon to open the Settings page.Choose Security Settings and Others > Smoke Testing, then turn on Force smoke testing for the workspace.
Run smoke testing
There are four ways to trigger smoke testing. Choose based on your current workflow stage:
| When to use | How to trigger |
|---|---|
| During commit — test and commit in one step | Click the  icon in the toolbar on the node editing page, then select Yes for Smoke Testing. |
| After commit — run a standalone test from the editor | Click the  icon in the toolbar on the node editing page. |
| After commit — trigger from the publishing queue | On the Task Publishing page, click Smoke Testing for the target node. |
| After commit — trigger from Operation Center | In the upper-left corner of Operation Center, switch to the development environment. In the left navigation pane, click Auto Triggered Task O&M > Auto Triggered Task, right-click the target node, and click Test in the dialog box that appears. |
Configure smoke testing parameters
After opening the smoke testing dialog, select a data timestamp to use as the business time for the test run.
If you select today's or yesterday's date as the business time, the smoke testing task does not run immediately — it waits until the node's scheduled time. For example, if the current time is 12:00 on June 2, 2024, the node is scheduled to run at 15:00, and you select June 1, 2024 as the business time, the task runs at 15:00 on June 2, 2024, not immediately.
View smoke testing records
There are several ways to open smoke testing records:
In the toolbar on the node editing page in Data Development, click the
icon to open the View Smoke Testing Records page.After clicking the smoke testing icon and configuring parameters, the records dialog opens automatically.
If the entry point is not visible in the left navigation pane, add the module on the Settings page. For details, see Change the layout: Customize the displayed modules.
On the Smoke Testing Records page, each record shows Test Time, Version, Tester, and Data Timestamp.
Click Initiated in DataStudio to filter for records triggered from DataStudio. Records from the development environment of Operation Center are not included in this view.
To inspect a specific run, click View Log to see the full execution log. To stop a run that is still in progress, click Stop next to a record with a Status of Running.