Creating a Manual Test Case

Prerequisites

You have the permission to create test cases (that is, you have other system roles except the viewer and participant in the project).

Procedure

Manual test cases are used to manage test scenarios and steps. You can manage manual test cases on the Test Cases > Manual Test page.

1. Log in to the CodeArts homepage, search for your target project, and click the project name to access the project.
2. On the navigation bar, choose Testing > Testing Case.
3. The test case library is displayed by default. On the Manual Test tab page, click Create on the left.

   

4. Enter the name, description, prerequisites, and test steps as required, and click Save.

   The main configuration items of the manual test cases are as follows.

   Configuration Item	Mandatory	Description
   Name	Yes	Name of a test case. You can describe its test scenario or function.
   Description	No	Brief description of a test case. You can enter the test scope, test objectives, test policy, test methods, test tools, test data, test metrics, and test environments of the current test case.
   Prerequisites	No	Prerequisites for executing the current test case.
   Test Steps	No	Step description and expected result.
   Tag	No	Tag for the current test case as required. Each test case can be associated with a maximum of 10 tags, which should be separated by spaces.
   ID	No	Test case ID, which can be customized. If this item is left blank, a test case ID is automatically generated.
   Case Level	No	Test case level based on the importance of the scenario or function. L0: verification of underlying functions. Each module should have 10 to 20 test cases. L0 test cases account for 5% of all test cases. L1: verification of basic functions for inherited features or before iteration acceptance. L1 test cases account for 20% of all test cases. L2: verification of important features for manual tests in non-regression versions. L2 test cases account for 60% of all test cases. L3: verification of minor and non-important functions, and exception tests on basic and important functions. L3 test cases account for 15% to 20% of all test cases. L4: verification of special input, scenarios, and threshold conditions. L4 test cases account for less than 5% of all cases.
   Module	No	Module of the current test case. The module list comes from the project settings. For details, see Setting Modules.
   Version	No	Version number of the current test case.
   Iteration	No	Iteration to test the current test case.
   Processor	No	Person who needs to complete the test task.
   Associated Requirement	No	It is recommended that test cases be bidirectionally associated with test requirements. If the current test case is used to test a specific requirement and the requirement has been recorded in the ProjectMan service, click Associated Requirement to associate the test case with the requirement work item. NOTE: Test cases can be associated only with Epic, Feature, and Story work items of a Scrum project and default Requirement work items of a Kanban project.
   Folder	No	Association with a feature directory.
   Attachment	No	Attachment related to the current test case. You can associate an existing file on the Documents page or upload an attachment from the local PC.