FAQ

Using test management in a project

Projex includes a test plan management module for planning and executing test plans. In your project settings, go to navigation services and enable the testing switch. You can then manage test plans directly from the project navigation menu.

Adding custom fields to a test case

Testhub supports custom test case fields to help your team classify and manage cases. In global settings, open the test case field section to add fields such as text, number, and single-select.

The page has two built-in, single-select list fields: priority and type. After you click New Field and add a review status field, a green "Operation successful" message appears at the top of the list.

After you add a new field, add it to the template in the Test Case Template section, where you can set whether the field is required. When you create test cases, you can set this field and filter by it in test case design and test plans.

By default, the test case template includes fields such as owner (single-user selection, required), priority (single-select list), type (single-select list), tag (multi-select list), and review status (single-select list). Each field can be edited or deleted individually.

Test case import errors

Many testing teams use Excel or Xmind to manage test cases. Alibaba Cloud DevOps supports importing these files, though errors can occur on the first attempt. If an import fails, the system provides a detailed explanation. Click the button next to the Failed status to download a file listing each failed test case and the reason. Common reasons include:

• A required field is empty.

• The test case directory format is incorrect (directory levels must be separated by a vertical bar "|").

• The value of a single-select field is outside the allowed options. For example, if the valid values for priority are "P0, P1, P2, and P3", entering "High" will cause an error.

• The owner does not exist or is entered incorrectly. User name attributes are easily confused, such as a login name (typically an email), a nickname, and a display name. To avoid this error, first create a test case in the UI, check the user names available in the owner selection box, and then use that exact format in your Excel or Xmind file.

If a small number of test cases fail to import, copy them into a separate Excel file, correct the errors, and re-import only the failed cases. If a large proportion of test cases fail, delete the partially imported cases by using bulk actions, fix the original file, and then re-import the full, corrected file to maintain the original test case order.

On the test case library page, click bulk actions in the upper-right corner to open the bulk action history dialog box. This dialog box shows the test case import history, including the action type, operator, time, and status (successful or failed).

Modifying a test case during execution

During test case execution, you can update execution results, create bugs, and add notes. However, you cannot directly modify the test case content. To modify the test case, click View Source Test Case in the upper-right corner. This takes you to the test case library where you can make your changes.

Testhub treats test cases as important assets and separates design from execution to encourage reuse. A single test case from the library can be used across multiple projects, so unrestricted modifications could disrupt testing elsewhere. Design and review test cases before execution. If a change is necessary during execution, the test case owner must return to the test case library to make modifications and preserve the integrity of the test case.

When you execute a test case in a test plan, the center pane displays the test case details (such as title and prerequisite) in read-only mode. The right-side panel is divided into two sections: execution results (where you can set the execution status and executor) and test case information (which displays attributes such as owner, priority, type, and tag).