Test Case Management App
The Test Case Management app is designed for managing test case libraries during the development process. It supports features such as creating and editing test case groups and performing batch imports. This allows testers to standardize and build a reusable collection of test cases, eliminating the repetitive authoring and information-sharing difficulties common in traditional project management. It serves as a dedicated 'arsenal' for testers.
Step 1: Create a test case library
Click the nine-dot icon in the upper-left corner and select "Test Case Management" from the Dock menu to enter the app.
Click the blue "Create Test Case Library" button or the creation card in the upper-right corner. Enter a name and an optional description to create a new test case library.
The functional hierarchy is as follows:
Test case library > test case group > test case. You can create multiple libraries, and each library can contain multiple groups to manage your test cases.
Step 2: Create and configure test case groups
After entering a test case library, the left-side navigation pane displays the test case group information.
You can create groups to further refine and categorize test cases. For example, you can create a test case library for each major functional module of your product, and then create a group for each feature within that module to keep your product's testing content clear and organized.
In the left-side navigation pane, click Add Group. In the Create Group dialog box that appears, enter a Group Name and click Create.
Step 3: Create a test case
Test cases can be created manually or imported in batches. Batch import supports both Excel and mind map files.
1. Manually create a test case
Within each test case group, click "Create Test Case" to open the details page. Here, you can configure the test case's "prerequisite", "steps", "test case type", and "test case priority".
Prerequisite: Specifies the conditions and system state that must be met before executing the test case. It can also be used for notes.
Steps: The steps and expected results are the core of a test case. They describe the detailed execution process and the expected behavior of the application.
Test case type: By default, there are eight types: functional testing, automated testing, performance testing, configuration-related, security deployment, security-related, API testing, and others.
Test case priority: The default priorities are P0–P5. A lower number indicates a higher execution priority.
2. Batch import test cases
Many testing teams use spreadsheets or mind maps to write test cases. However, these files can be easily damaged or lost, making it difficult to build a lasting and manageable test asset repository. To address this problem, you can batch import your test files into the Teambition test case library. We support importing data from spreadsheet files and .xmind mind map files, reducing creation effort and helping you quickly generate test cases.
Click "Batch Import", fill in the required information using the import template, and then upload your file.
Spreadsheet imports support xls, xlsx, and csv formats. You must first download and fill out the import template before uploading. You can import up to 500 test cases at a time. If a row contains fields that do not conform to the rules, the system skips the entire test case in that row. For mind map imports, use the tc: prefix to mark the test case name, tc-p1: to mark the test case priority, and tc-p2-functional testing: to mark the test case type. You can also add prerequisites, steps, and expected results. The system supports up to 8 levels of groups, and the root node is not imported. You can import up to 500 test cases at a time.
Step 4: More test case operations
For example, when test cases are reusable (e.g., for performance or security testing) or when a test lead is dividing tasks, you can select one or more test cases and move or copy them to other libraries.
From the menu in the upper-right corner of the test case details page, you can select "Copy Test Case", "Move Test Case", and "Delete Test Case".
Clicking Copy Test Case opens the "Copy to" dialog box, where you must select a destination test case library and group. The system then creates a new test case with identical content. Clicking Move Test Case opens the "Move to" dialog box, where you must select a destination test case library and group. You might lose some maintainer information when moving test cases across libraries. Clicking Delete Test Case opens a confirmation dialog box warning that the data cannot be recovered.
Use case: When a test lead is assigning testing tasks, they can select multiple test cases and assign them to the appropriate testers by using the "Set Maintainer" option.
Step 5: Add test cases to a test plan
After a test lead creates a test plan in a project, they can add the required test cases from the test case library to the plan. This allows for test case reuse and reduces the effort of creating new ones from scratch.
In a test case library, select the test cases you want to add to a plan. Click the Add to Plan button. In the Select Test Plan dialog box that appears, choose the target project and test plan (for example, Test Plan App V1.0), and then click OK. The selected test cases will be added to the specified test plan.