From 90b13eab9dc7626600488b6a21246e00d019e60b Mon Sep 17 00:00:00 2001 From: king_he <6384784@qq.com> Date: Thu, 30 Jun 2022 08:12:51 +0000 Subject: [PATCH] update en/device-dev/subsystems/subsys-testguide-test.md. Signed-off-by: king_he <6384784@qq.com> --- en/device-dev/subsystems/subsys-testguide-test.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/en/device-dev/subsystems/subsys-testguide-test.md b/en/device-dev/subsystems/subsys-testguide-test.md index ead55bf03f..60bdfb48f0 100644 --- a/en/device-dev/subsystems/subsys-testguide-test.md +++ b/en/device-dev/subsystems/subsys-testguide-test.md @@ -230,14 +230,14 @@ Example: - *B* indicates the test case name, which is in the *Function*\_*No.* format. The *No.* is a three-digit number starting from **001**. - *C* indicates the test case level. There are five test case levels: guard-control level 0 and non-guard-control level 1 to level 4. Of levels 1 to 4, a smaller value indicates a more important function verified by the test case. - > **NOTE** - > - The expected result of each test case must have an assertion. - > - The test case level must be specified. - > It is recommended that the test be implemented step by step according to the template. - > The comment must contain the test case name, description, type, and requirement number, which are in the @tc.*xxx*: *value* format. The test case type @**tc.type** can be any of the following: + Note the following: + - The expected result of each test case must have an assertion. + - The test case level must be specified. + - It is recommended that the test be implemented step by step according to the template. + - The comment must contain the test case name, description, type, and requirement number, which are in the @tc.*xxx*: *value* format. The test case type @**tc.type** can be any of the following: | Test Case Type | Code | - | ------------|------------| + | ------------ |------------ | | Function test | FUNC | | Performance test | PERF | | Reliability test | RELI | -- GitLab