Creating a Manual Test Case

Prerequisites

You have been assigned a role (except the O&M manager, viewer, and participant) that has permissions to create test cases. For details, see User roles and permissions.

Constraints

For Scrum and IPD projects, work items that can be added to manual test cases as requirements are epics, features, and stories.

For Kanban projects, the default requirement work items can be added to manual test cases as requirements.

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 following table describes the main configuration items of manual test cases.

   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. : Add a row. : Copy the row and paste it to the next row. : Delete the row.
   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. You can enter a custom ID. If left blank, it will be automatically generated. In the navigation pane, choose Settings > Testing. Click the Test Case Settings tab, locate the row of ID, and click in the Operation column. In the displayed dialog box, enter the prefix, auto-increment start value, and connector. Click OK. Test cases will be automatically numbered by this rule. The test case ID can be changed as required at the test case list page. An ID can contain 3 to 128 characters.
   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. Two views are provided for editing test steps:
   • Text view. Click Text on the segmented button and enter test steps and expected results in the two text boxes.
   • Table view. Click Table on the segmented button and enter test steps and expected results in the table. To add more rows, click in the Operation column.

3. Click the Requirements tab. Click Associate With Requirement on the right of the page. In the displayed dialog box, select the requirements to be associated and click OK.
4. Click Save.

Related Topics

• Adding Test Cases to a Test Plan and Creating a Manual Test Suite: Add test cases to test plans and suites to assign execution tasks to testers.
• Managing Test Cases: Import and export manual test cases and associate requirements or bugs.