Test plans in projects

Enable the application

Project owners or project administrators can click Menu > App Center in the upper-right corner of the project interface or click the + button in the project navigation bar. Search for Test Plan in the App Center and click Enable to start using it in the project. Agile R&D projects have this application enabled by default.

Create and edit test plans

Click Create Test Plan in the left sidebar to begin.

In the dialog box that appears, enter a Test Plan Name. Optionally set a Start Time and End Time, then click Create.

You can edit or delete existing test plans from the menu. Create and name test plans based on product iteration cycles.

Click the ... button in the upper-right corner of a test plan card to open the menu. Select Edit Test Plan to modify the Test Plan Name, Start Time, or End Time, then click Confirm to save. Select Delete Test Plan to remove the plan. The system will show the number of test cases in the plan. Confirming deletion removes all associated test cases.

Create test cases

You can create test cases in three ways: plan from the test case library, create manually, or import in bulk.

1. Plan cases from the test case library

Click Plan Cases in a test plan to open the test case library panel. Browse by group or search for target cases on the left side of the panel. Check the cases you want to add and click Confirm. The selected cases are added to the current test plan.

Scenario 1: This iteration requires optimizing the project template feature. Testers can click Plan Cases to select existing project template-related test cases from the test case library, add them directly to the test plan, and then adjust test details and steps based on the current update.

Scenario 2: During regression testing, testers consider that new features might affect existing functionality. They can plan relevant test cases from the test case library into the test plan to complete regression testing.

2. Import test cases in bulk

Click the three dots in the upper-right corner of the test case list and select Batch Import. Fill in the information using the import template and upload the file to import multiple test cases at once. You can import from spreadsheet files or mind map files.

Spreadsheet files support xls, xlsx, and csv formats. Mind maps support .xmind format. You can import up to 500 test cases at a time. In Xmind files, mark test cases with the prefix tc:, use tc-p1: or tc-p2: to indicate priority levels, and use pc: to mark preconditions. You can also include step and expected result information. Up to 8 levels of grouping are supported. Root node information is not imported.

3. Create test cases manually

Click Create Case to open the detailed settings page. Set values for fields such as status, preconditions, steps, case type, and case priority.

Case Type options include Automated Testing, Performance Testing, Configuration, Installation and Deployment, Security, API Testing, and Other. Case Priority options range from P0 to P5. Case Status options include To Be Reviewed, Not Executed, Passed, Blocked, and Failed.

Click an existing test case to open its details page. From the case menu in the upper-right corner, you can Copy Case, Move Case, Delete Case, Copy Link, or Submit Bug.

Submit Bug lets testers report defects found during test execution. When selected, it creates a work item linked to the relevant project and iteration, making defect tracking and resolution easier.

After clicking Submit Bug, a Create Task dialog box appears. The task type defaults to Bug · To Do. The comment field includes a template with sections for reproduction steps, actual results, expected results, and problem screenshots. The system auto-fills the current test case’s preconditions and steps.

Edit test cases

1. Edit test cases in bulk

Use batch operations when you need to frequently update test statuses or assign executors across many test cases. Select multiple cases at once to perform bulk actions such as Change Status or Assign Executor.

Scenario: During weekly test review meetings, testers verify each test case. After the meeting, they can batch-update statuses and assign executors in one step.

The batch operation bar also supports Change Case Priority. Click More to reveal additional options: Move Case, Copy Case, and Move to Recycle Bin.

2. Filter and sort test cases

Scenario: When dealing with many test cases, testers can filter by priority, type, or other dimensions to find relevant cases quickly. They can also select My Cases Only to view only cases assigned to themselves, reducing time spent searching. Sorting helps prioritize high-priority or older cases.

Filtering: Filter by executor, status, creator, participant, case type, case priority, and tags.

Sorting: Sort by case priority (high to low) or creation time (newest to oldest).

3. Save cases to the test case library

Newly created test cases in a test plan—or updated versions of existing ones—can be synced back to the test case library. Use the Quick Filter – Not Synced to Library option to quickly find unsynced cases and click Sync to Library to update and preserve them.

Export test cases

In a test plan, click the three dots in the upper-right corner to see the Batch Export option.

You can export either All Cases in This Test Plan or All Cases in the Current Group. After confirming the export, you receive a .csv file containing all fields from the executed cases.

The exported .csv file includes these fields: Title, Group, Status, Executor, Preconditions, Steps, Expected Results, Case Type, Case Priority, and Tags.

Tips:

• Export is currently supported only for test cases in project test plans.

• The import and export templates differ.

Configure your test workflow

Test statuses include Start, In Progress, and End states. Add, remove, or modify statuses as needed, define transition rules, and drag to reorder them.

Scenario: After development completes, developers run self-tests. If passed, they update the status to Self-Test Passed, which then flows to testers. Testers update the status to Passed or Blocked based on results.

To configure: Click Menu > Project Settings > Test Plan Settings in the upper-right corner of the project.

In Test Plan Settings, click the Test Plan Workflow Settings card. In the workflow panel that opens, click the gear icon (⚙) next to the target workflow to edit it.

The Workflow Configuration dialog includes five default statuses: To Be Reviewed (start), Not Executed (in progress), Passed (end), Blocked (in progress), and Failed (in progress). In the transition area, use check boxes to define allowed transitions between statuses. Self-transitions (diagonal) are disabled by default.

Tips:

• You cannot create new test workflows.

• You cannot modify or create new test case task types.