- Format: table with columns: 模块, 标题, 前置条件, 步骤描述, 预期结果, test1测试人员, test1测试结果, buglink, PRE测试人员, PRE测试结果, buglink
- Language:
模块 columns: Chinese, if the part of docs is 中控后台PC text => this is a part testcase related to 中控后台PC web, and then the column should display with format: 代理后台-AGBE/**** Example: 代理后台-AGBE/个人资料/账号活动
if the part of docs is 代理后台PC text -> this is a part testase related to 代理后台PC web, and then the column should displays with format 中控后台-ADBE/. Example: 中控后台-ADBE/代理管理/代理详情/登录信息
标题, 前置条件, 步骤描述, 预期结果, test1测试人员, test1测试结果, buglink, PRE测试人员, PRE测试结果, buglink: Chinese.
Please fill in the uploaded data according to the following rules:
1. Module: Enter the name of an existing module in the test case library. Please start from the first-level module and fill in the complete list (all test cases do not belong to modules). Separate levels with "/", for example: Level 1 Module/Level 2 Module/Level 3 Module, up to 10 levels. If not filled in, it will be automatically included in 'No Module Test Cases'.
2. Number: The number format is: Test Library Identifier-XX, where XX represents a number, such as "QLD-3". If the number exists in the test case management, the test case will be overwritten; if the number does not exist or is not filled in, a new test case will be created.
3. Title: Required field, cannot be empty.
4. Maintainer: Enter the name or username of a team member. If there are members with the same name in the team, one member will be randomly selected by default.
5. Test Case Type: Optional values: Functional Test, Performance Test, Configuration Related, Installation and Deployment, Interface Test, Security Related, Compatibility Test, UI Test, Other.
6. Importance: Optional values: P0, P1, P2, P3, P4. 7. Test Type: Optional values: Manual, Automatic.
8. Estimated Working Hours: Numeric type, e.g., 10, can be empty.
9. Remaining Working Hours: Numeric type, e.g., 10, can be empty.
10. Associated Work Items: Enter the associated requirement number. When entering multiple values, please separate them with "|".
11. Preconditions: Optional.
12. Step Description: Text. Please enter steps with numbers, e.g., 1.xxx, 2.xxx; enter in groups, adding "→" before sub-steps, e.g., 1.xxx, →1.xxx; each group or step cell should have a new line.
13. Expected Result: Text. Keep the numbers corresponding to the steps, e.g., 1.xxx, 2.xxx; grouped expected results do not need to be filled in, adding "→" before sub-expectations, e.g., 1. Empty, →1.xxx; each expected result cell should have a new line.
14. Followers: Enter the names or usernames of team members. If there are members with the same name in the team, one member will be randomly selected by default. When entering multiple values, please separate them with "|".
15. Remarks: Optional.
16. Custom Attributes: Use attribute names created in the system. Not required.
17. Tags: Multiple tags can be imported. You need to import tags that exist in the system and separate them with ",".
Tips:
1. A maximum of 5000 tags can be imported at a time.
2. "Title" is a required field. If a required field is empty, it will not be imported.
*******Importance*******
STRICT RULES:
- Do NOT assume or invent functionality.
- One test case validates one behavior only.
- Test user-visible behavior only.
STRUCTURE RULES:
- Mandatory fields: ID, Title, Preconditions, Steps, Expected Result, Priority
- Steps must be actionable and sequential
- Expected Result must describe outcome, not steps
VALIDATION RULES:
- Create negative test cases for each validation rule
- Separate validation rules into separate test cases
- Verify error messages if mentioned
QUALITY RULES:
- No duplicate test cases
- Use clear, unambiguous language
- Assign priority based on business impact
