Complete functional testing of software independently (2)

Complete functional testing of software independently (2)

（12.13）

1. Design test points for exhaustive scenarios (equivalence class division method)

1. The concept of equivalence class division method:
   • Description: The data has common characteristics, success or failure
   • Classification:
     • Valid: 6-8 digits
     • Invalid: less than 6 digits, more than 8 digits
   • step:
     • Clear needs
     • Confirm valid or invalid
     • Extract data and write test cases

2. Design test points (boundary values) for limited boundary rules

1. Requirement: Determine whether the number is less than -99 or greater than 99. If it is less than -99 or greater than 99, an error will be prompted.

2. The concept of boundary value analysis

   • Boundary range node: Values ​​exactly equal to, just greater than, and just less than the boundary are used as test data

     • Upper point: exactly equal to, point on the boundary

     • Distant points: the two closest points to the still point (just greater than, just less than)

     • Inner point: Point within the range (data within the interval, generally the centered point)

     

   • Use case design steps

     • Clarify needs
     • Determine valid and invalid equivalence classes (take requirements as an example, including non-data)
     • Determine the boundary range (range limit 7 points)
     • Extract data and write test cases

   • Case (verify whether the title length is legal, the title length is greater than 0 and less than or equal to 30 characters, italics can be optimized, open inside and outside)

     use case number	Use case title	Project/Module	priority	Preconditions	Test steps	Test Data	expected results
     title_001	Illegal (the title is a 15-digit non-string)	title	P1	Open the program	1. Enter the title 2. Click Verify	012345678912345 (Title: 15 digits)	illegal
     title_002	Illegal (title is empty)	title	P1	Open the program	1. Enter the title 2. Click Verify	Title: empty	illegal
     title_003	Legal (30 characters)	title	P0	Open the program	1. Enter the title 2. Click Verify	Title: 30 characters	legitimate
     title_004	Legal (1 character)	title	P0	Open the program	1. Enter the title 2. Click Verify	Title: 1 character	legitimate
     title_005	Legal (29-bit string)	title	P0	Open the program	1. Enter the title 2. Click Verify	Title: 29 characters	legitimate
     title_006	Legal (15-digit string)	title	P0	Open the program	1. Enter the title 2. Click Verify	Title: 15 characters	legitimate
     title_007	Illegal (31-bit string)	title	P1	Open the program	1. Enter the title 2. Click Verify	Title: 31 characters	illegal

     Case 2: (Verify 6 to 10 digit natural numbers, italics can be optimized, open inside and outside closed)

     use case number	Use case title	Project/Module	priority	Preconditions	Test steps	Test Data	expected results
     title_001	Illegal (8-bit non-natural number)	Number	P1	Open the program	1. Enter the title 2. Click Verify	123456a	illegal
     title_002	Legal (6-digit natural number)	Number	P0	Open the program	1. Enter the title 2. Click Verify	123456	legitimate
     title_003	Legal (10 digit natural number)	Number	P0	Open the program	1. Enter the title 2. Click Verify	0123456789	legitimate
     title_004	Illegal (5-digit natural number)	Number	P1	Open the program	1. Enter the title 2. Click Verify	12345	illegal
     title_005	Legal (7-digit natural number)	Number	P0	Open the program	1. Enter the title 2. Click Verify	1234567	legitimate
     title_006	Legal (9-digit natural number)	Number	P0	Open the program	1. Enter the title 2. Click Verify	123456789	legitimate
     title_007	Illegal (11-digit natural number)	Number	P1	Open the program	1. Enter the title 2. Click Verify	12345678900	illegal
     title_008	Legal (8-digit natural number)	Number	P0	Open the program	1. Enter the title 3. Click Verify	12345678	legitimate

   • Applicable scene

     • Single input box (bounds + equivalent)

3. Design test points (scenario method) for multiple conditionsdependencies

1. Requirement: Verify the function of "if the user is in arrears or shuts down, he is not allowed to be called"

2. Basic knowledge of decision table method

   • Description: Various combinations of conditions, testing of mutual constraints between input conditions and output results
   • Definition: A tool for expressing multi-condition logical judgments in the form of tables
   • composition
     • Condition pile: All conditions in the problem, the order does not matter.
     • Action piles: Possible operations in the problem. There is no constraint on the order of operations.
     • Conditional item: List the values ​​corresponding to the condition, all possible true and false values.
     • Action items: List the condition items and the action results that should be taken under various value conditions.

3. Use case design steps

   • Clarify needs
   • draw decision table
   • Extract data and write use cases

4. Case

   

4. Scenario method

4. Scenario method

   • For any test, first run through the business, such as testing the shopping software from logging in, browsing products, adding to the shopping cart, placing an order, and review the process.

   • Flowchart (drawn by the developer): (Web version tool https://processon.com)

     

   • Case

     

5. Error inference method

1. Definition: Inferring possible problems through experience

2. Thoughts: Make a list

3. Scenario: tight time and large workload