[fundamentals of interface testing] Part V - detailed explanation of interface use case design

Interface test point

The test point is called the test latitude .
1. A functional test
Single interface function
Business scenario functions
2. Performance testing
Response time
throughput
Concurrency number
Server resource utilization
3. Security testing
Whether sensitive data is encrypted
SQL Inject
other

• A functional test

  Single interface function
  A single business module in manual testing , Generally, it corresponds to an interface
  Log in to business –> Login interface
  Join the shopping cart business –> Join the shopping cart interface
  Order business –> Order interface
  Payment business –> Payment interface
  With tools 、 Code . Bypass the front-end interface , The data needed to organize the interface , Expand the interface test .
  Business scenario functions
  According to the user's actual use scenario , Sort out the interface business scenarios
  When organizing business scenarios , Generally, you only need to do a positive test ( Consistent with manual )
  It is generally recommended to cover the most business scenarios with the least use cases
  Sign in - Search for products - Plus shopping cart - Place an order - payment – evaluation

• Performance testing

  Response time
  throughput
  Concurrency number
  Server resource utilization

• Security testing

  Attack security ： Completed by professional safety test engineer .
  Business security ：
  Whether sensitive data is encrypted （ for example ： The login password ）
  SQL Inject
  Browser developer tools
  

Design methods and ideas

• The same as manual design

Manually test the corresponding function test points , It is consistent with the functional safety corresponding to the interface test
tpshop Mall login page , Key points of manual function test case design ：
1. Whether the page layout meets the requirements
2. Test user name input box , Whether the input data is correct
3. Test password input box , Whether the input data is correct
4. Test verification code input box , Whether the input data is correct
tpshop Mall login page , Key points of interface test case design ：
1. Test the corresponding of the user name input box username Is the value of
2. Test the... Corresponding to the password input box password Value , Whether it is right
3. Corresponding to the test verification code input box verify_code Value , Whether it is right

• Different from manual work :

1. Manual testing , Test whether the data written into the input box is correct , Whether the parameter value corresponding to the interface test parameter is correct
2. The interface test , Not just for parameter values , You can also test the parameters themselves .
Forward parameter ：
Required parameters ： All required ( Required ) Both contain
Combination parameter ： All required + Any one or more optional parameters
All parameters ： All required + All optional parameters
Reverse parameter ：
Multiple parameters ： There are one or more required parameters ( You can specify any )
Shaoshen ： One or more required parameters are missing
No arguments ： There are no required parameters
bad parameter ： Parameter name input error

Single interface test cases ：
Manual test case documentation 8 The big thing
Number 、 Use case name ( title )、 modular 、 priority 、 Preset conditions , Test data , Operation steps , Expected results
Interface test document elements ：
Number , Use case name ( title ), modular , priority , Preset conditions , Request method ,URL, Request header , Request body ( Request data )、 Expected results

User name related test cases

Password related test cases

Parameter related test cases
Business process test cases
Other omissions