From 70b511cf717057924202f132fc6762a69b183504 Mon Sep 17 00:00:00 2001 From: Shuduo Sang Date: Fri, 15 May 2020 11:31:12 +0800 Subject: [PATCH] Update How-To-Run-Test-And-How-To-Add-New-Test-Case.md --- ...ow-To-Run-Test-And-How-To-Add-New-Test-Case.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/tests/How-To-Run-Test-And-How-To-Add-New-Test-Case.md b/tests/How-To-Run-Test-And-How-To-Add-New-Test-Case.md index e7a758988f..246ab0ea37 100644 --- a/tests/How-To-Run-Test-And-How-To-Add-New-Test-Case.md +++ b/tests/How-To-Run-Test-And-How-To-Add-New-Test-Case.md @@ -218,3 +218,18 @@ def checkAffectedRows(self, expectAffectedRows): > appropriate without additional > burden.   +### CI Covenant submission adoption principle. + +- Every commit / PR compilation must pass. Currently, the warning is treated + as an error, so the warning must also be resolved. + +- Test cases that already exist must pass. + +- Because CI is very important to support build and automatically test + procedure, it is necessary to manually test the test case before adding it + and do as many iterations as possible to ensure that the test case provides + stable and reliable test results when added. + +> Note: In the future, according to the requirements and test development +> progress will add stress testing, performance testing, code style, +> and other features based on functional testing. -- GitLab