After you develop code, you must debug it. This topic describes how to perform smoke testing in the development environment.
Introduction to smoke testing
Before you deploy a node, we strongly recommend that you use smoke testing to verify the correctness of its configuration and running logic. Smoke testing is mainly used to verify the following:
Whether the scheduling parameters of the node can be correctly replaced.
Whether the upstream and downstream dependencies of the node are correct.
Whether the running results of the node are as expected.
In a standard workspace, smoke testing is performed in an isolated development environment. This ensures that your online production data is not affected, even if a task involves data writing.
Go to Data Development
Go to Data Development.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose . On the page that appears, select the desired workspace from the drop-down list and click Go to Data Development.
Enable the Force smoke testing feature
The administrator of a workspace can enable the Force smoke testing feature. After this feature is enabled, a task in the current workspace must pass smoke testing before it can be deployed to the production environment.
The Force smoke testing feature is not available for workspaces in basic mode.
In the navigation pane on the left of Data Development, click the
icon to go to the Settings page.On the Settings page, choose Security Settings and Others > Smoke Testing, and turn on Force smoke testing for the workspace.
Perform smoke testing
After you develop code, you can use one of the following methods to perform smoke testing before you deploy and run a task:
When you commit a node, click the
icon in the toolbar at the top of the Data Development node editing page, and select the Yes radio button for Smoke Testing.After you submit the node, click the
icon in the toolbar at the top of the Data Development node editing page to perform smoke testing.After you commit a node, click the Smoke Testing button for the node on the Task Publishing page.
In the upper-left corner of the Operation Center page, switch to the development environment. In the navigation pane on the left, click . Then, right-click the target node and click Test in the dialog box that appears.
Configure smoke testing parameters
After you go to the smoke testing page using one of the preceding methods, you must select a data timestamp for the smoke test.
If you select today or yesterday as the business time for the smoke test, the smoke testing task waits until its scheduled time before it runs. For example, if the current time is 12:00 on June 2, 2024, the scheduled runtime for the task is 15:00, and you select June 1, 2024 as the business time for the test, the task will actually run at 15:00 on June 2, 2024. In this case, the smoke testing task must wait because its scheduled time of 15:00 has not yet arrived.
View smoke testing records
In the toolbar on the node editing page in Data Development, click the
icon to go to the View Smoke Testing Records page.NoteWhen you commit a node, select the Yes radio button for Smoke Testing. After the node is committed, you can view the smoke testing process using the preceding method.
After you click the Smoke Testing button on the node editing page, you can view the smoke testing records in the dialog box that appears after you configure the smoke testing parameters.
If you cannot find the entry in the navigation pane on the left of the Data Development page, you can add the module on the Settings page. For more information, see Change the layout: Customize the displayed modules.
On the Smoke Testing Records page, you can view information such as Test Time, Version, Tester, and Data Timestamp. Click the Initiated in DataStudio button to quickly find the smoke testing records that were triggered from the DataStudio page.
NoteIf you select Initiated in DataStudio, the displayed smoke testing records do not include the test records that were run in the development environment of Operation Center.
On this page, you can click View Log to view the detailed execution logs of a specific smoke test. You can click the Stop button to stop a record with a Status of Running.