General test case writing specification

　　 The software test case obtains the content of the software test case , secondly , According to the software test writing method , Put it into the document , They are the relationship between form and content , Good test cases are not only convenient for yourself and others to view , And it can help design more carefully .

　　 A good test case must contain enough content , These contents can be divided into eight elements ： Use case number 、 Test project 、 Test title 、 Importance level 、 Preset conditions 、 Test input 、 Operation steps 、 Expected output .

　　1、 Use case number

　　1) The rules ： Is a string of characters and numbers , Have uniqueness 、 Legibility .

　　2) Case number of test cases in different stages

　　-- System test cases ： Product number _ST_ System test item name _ System test subkey name _XXX( Specific use case serial number )

　　-- Integration test cases ： Product number _IT_ Integration test item name _ Integration test subitem name _XXX( Specific use case serial number )

　　-- Unit Test Case ： Product number _UT_ Unit test item name _ Unit test subitem name _XXX( Specific use case serial number )

　　2、 Test project

　　1) The rules ： Corresponding to the test sub item name in the test case number

　　2) Specific rules of test case projects in different stages

　　__ System test cases ： Corresponding to a function point ( A functional test )、 Performance indicators ( Performance testing ) Controls in the interface (GUI test ) etc. , Software requirement items

　　__ Integration test cases ： Integrated module function name or internal interface name

　　__ Unit Test Case ： The name of the function being tested

　　

　　​

　　3、 Test title (TestCase Title)

　　1) The rules ： Reflect the starting point of the test 、 Concerns and expected test results of test cases ;

　　 String the test item and test title together to indicate that it is in “ Test title ” Test in case “ Test project ”.

　　4、 Importance level / Priority (TestCase Priority)

　　1) meaning ： The importance level of use cases is generally divided into 3 Level ： high 、 in 、 low , Specific division basis ：

　　(1) High level ： Ensure the basic functions of the system 、 The core business 、 Important features 、 Test cases with high frequency of actual use ;

　　(2) Medium level ： Corresponding to test cases with high and low importance ;

　　(3) Low level ： Corresponding to the actual use frequency is not high , Test cases of modules or functions that have little impact on the business functions of the system .

　　2) The priority role of test cases

　　(1) Facilitate the development of test procedures ( The order in which test cases are executed ) That is, the test process ;

　　(2) In regression testing, different methods can be selected according to priority ;

　　(3) automated testing

　　(4) Defect report severity and priority

　　5、 Preset conditions (Test Pre_condition)

　　1) meaning ： Test cases need to meet some preconditions when executing , Otherwise, the test case cannot be executed , These preconditions are preset conditions , There are two situations when setting preset conditions ：

　　(1) Environment settings , For example, testing word Document opening function , You need to prepare open documents in advance , This is the preset condition .

　　(2) First run other test cases , For example, test the function of ATM , There are test cases for inputting account information and inputting withdrawal amount , Then the preset conditions of the latter can be written as test cases for inputting correct account information .

　　2) Be careful (PS)： Test preset conditions -- For a single use case

　　 Test environment -- For all use cases ( Problems with the test environment can cause test activities to hang / Pause )

　　6、 Test input (Test Input) 1) meaning ： It refers to the external information that needs to be processed during test execution .

　　2) The rules ： Avoid descriptive language , Be specific ;

　　 According to the specific situation of software test cases , There is manual input 、 file 、 Database records, etc .

　　7、 Operation steps (Operation/Execute Steps) 1) The rules ： The operation steps required to execute the current test case , It is necessary to give a clear description of each step , The test case executor can complete the test case execution according to the operation steps .8、 Expected output (Expected Results) 1) meaning ： The expected output is a very important part of the test case , To judge whether the tested object works normally , All need to be judged by the expected output .

　　 When writing the expected output, you can consider the following three aspects ：

　　(1) Interface display ( After the operation steps are executed , Prompt information displayed on the interface )

　　(2) Database changes ( After the operation steps are executed , The records in the database will change accordingly )

　　(3) Changes in relevant information ( After the operation steps are executed , Some information related to the tested object will change )

　　 For more information on testing techniques, please pay attention to ： Shenzhen duosurveyor software and Technical Service Co., Ltd