Smoke testing verifies that a scheduling node's parameter replacement logic and runtime behavior are correct before the node reaches the production environment. Run a smoke test during deployment to catch basic configuration errors early — before they affect live data.
Supported node types
Smoke testing is available for the following node types:
| Category | Node types |
|---|---|
| Data Integration | Batch synchronization |
| MaxCompute | MaxCompute SQL, MaxCompute Script, PyODPS 2, PyODPS 3, MaxCompute MR, SQL script template |
| Hologres | Hologres SQL |
| EMR | EMR Hive, EMR Impala, EMR MR, EMR Presto, EMR Shell, EMR Spark, EMR Trino, EMR Kyuubi |
| CDH | CDH Hive, CDH Spark, CDH Spark SQL, CDH MR, CDH Presto, CDH Impala |
| Lindorm | Lindorm Spark, Lindrom Spark SQL |
| ClickHouse | ClickHouse SQL |
| ADB | ADB Spark, ADB Spark SQL |
| Data Quality | Data quality monitoring |
| General-purpose | Shell node, Function Compute, SSH |
| Algorithm | PAI DLC, PAI Designer |
Enable forcible smoke testing
A workspace administrator can require all nodes to pass smoke testing before deployment. When enabled, no node in the workspace can be deployed to the production environment without passing a smoke test first.
Go to the Workspaces page in the DataWorks console. In the top navigation bar, select the target region. Find the workspace and choose Shortcuts > Data Studio in the Actions column.
In the left-side navigation pane of the Data Studio page, click the
icon and select Data Studio Settings.On the Settings page, click the Security Settings and Others tab. In the Smoke Testing section, turn on the Force smoking test switch.
Run smoke testing
After completing code development for a node, click Deploy in the top toolbar of the node configuration tab.
Initiate smoke testing based on your workspace mode:
Basic mode: The node runs on a single computing resource. Click Deploy to deploy the node, then initiate smoke testing.
Standard mode: The development environment and production environment are isolated. Click Initiate Smoke Testing before deploying to production. The test runs in the development environment.
In the Smoke Testing panel, select a data timestamp for the test.
Selecting today's or yesterday's date as the data timestamp delays execution — the test instance won't run until the node's scheduled time arrives. For example, if the current time is 12:00 on June 2, 2024, the node's scheduling time is 15:00, and you select June 1, 2024 as the data timestamp, the test won't run until 15:00.
View smoke testing records
Go to the SMOKE TESTING RECORDS pane using either method:
Method 1: In the left-side navigation pane of the Data Studio page, click the
icon (Smoke Testing Records icon).Method 2: On the DEPLOY tab, click Initiate Smoke Testing, then click the
icon (Smoke Testing Records icon).
The SMOKE TESTING RECORDS pane shows the testing time, testing status, tester, and data timestamp for each run.
To view detailed execution logs for a record, click View Log. If the Test Status is Running, click Stop to cancel the test.