Creating a Manual Test Case

Creating a Manual Test Case

1. Log in to the CodeArts homepage, search for your target project, and click the project name to access the project.
2. In the navigation pane, choose Testing > Testing Case.
3. Baseline and Test case library are displayed by default. On the Manual Test tab page, click Create Case 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	Description
   Name	(Mandatory) Enter 1 to 128 characters. Describe the test scenario or function.
   Description	Brief description of a test case. 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	Prerequisites for executing the current test case.
   Test Steps	Step description and expected result.
   Tag	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	Test case ID, which can be customized. If this item is left blank, a test case ID is automatically generated.
   Case Level	Test case level based on the importance of the scenario or function. The default level is L2. 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 sprint 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	Module of the current test case. The module list comes from the project settings. For details, see Adding Work Item Modules.
   Version	Version number of the current test case.
   Sprint	Sprint to test the current test case.
   Processor	Person who needs to complete the test task.
   Associated Requirement	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 CodeArts Req service, click Associate to associate the test case with the requirement work item.
   Folder	Associated feature directory. The test case is in the Other directory by default.
   Attachment	Attachment related to the current test case. You can associate an existing file from the Files page or upload an attachment from the local PC.
   Custom Field	Customized fields set in the Settings page. For details, see Test Case Fields.

Editing Test Case Details

Take a Scrum project as an example. Related requirements have been recorded in the project management module for the current sprint.

Before testing, the tester creates a manual test case for the corresponding function in the test case library based on front-end requirements, and associates them.

1. After the operations described in Creating a Manual Test Case are complete, choose Testing Design > Manual Test, click the name of the test case to be edited, and click the Details tab.
2. Edit the test details as required.
   • In the table under Test Steps, click the blank area in the Test Steps Description and Expected Result columns and enter information. Click in the Operation column to add a step and enter the step description and expected result.
   • Click Associate on the right of the page. In the dialog box that is displayed, select the requirement to be associated and click OK.