Interface use case design

What is writing about

1. Prevent missing test at test points . Clarity of organization
2. Easy to assign work , Evaluate workload and time
3. Use during interview ！

Test point of interface test

Test points are called test dimensions .

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 actual situation of users Use scenarios , carding Interface business scene .
  • When organizing business scenarios , Usually just do positive Test it （ Consistent with manual ）.
  • It is generally recommended to use the least Use cases Covering the most business scenarios .
    • Sign in —— Search for products —— Plus shopping cart —— Place an order —— payment —— evaluation

Performance testing

• Response time
• throughput
• Concurrent number
• Server resource utilization

Security testing

• Attack security . —— It has nothing to do with the test engineer .

• Business security . —— The direction of the test .

  • Whether sensitive data is encrypted

    

  • SQL Inject ： Where the user can enter data , write in SQL sentence .

    • SQL Inject security , Malicious written by the user SQL sentence , Not execute , Query the database ！

Design methods and ideas

The same as manual design

• Manual testing Corresponding Functional test points , Functions corresponding to interface test Exactly the same .

tpshop Shopping Mall Sign in 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 Shopping Mall Sign in page , Key points of interface test case design ：

1. test user name The input box corresponds to username Value Whether it is right .
2. test password The input box corresponds to password Value , Whether it is right .
3. test Verification Code The input box corresponds to verify_code Value , Whether it is right .

Different from manual design

1. Manual testing , Test whether the data written into the input box is correct . Interface test Parameters Corresponding Parameter values Whether it is right .
2. The interface test , Not just for The parameter value is carried out , You can also target Parameter itself To test .
   • Forward parameter ：
     • Required parameters ： be-all Mandatory （ Required ） Both contain .
     • Combination parameter ： be-all Mandatory + Any one or more optional parameters .
     • All parameters ： be-all Mandatory + be-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 case document 10 elements ：

• Number 、 Use case name （ title ）、 modular 、 priority 、 Preset conditions 、 Request method 、URL、 Request header 、 Request body ( Request data )、 Expected results

Analyze interface documents , With “ Login interface ” For example ：

• Request method ：post
• URL： “ system information ” Medium Protocols and domain names + /api/sys/login
• Request header ：Content-Type : application/json
• Request body ：{“mobile”:“13800000002”,“password”:“123456”}
• Expected results ： {“success”:true,“code”:10000,“message”:“ Successful operation ！”,“data”:“f5050a1b-7919-444c-9ec4-3c1a7286536d”}
  • data： The value is generated successfully by login Token data . This data Will change regularly .

Number	Use case name	modular	priority	Preset conditions	Request method	URL	Request header	Request body ( Request data ）	Expected results
login_001	Landing successful	Sign in	p1	Account number is registered	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“123456”}	Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”,“data”:“f5050a1b-7919-444c-9ec4-3c1a7286536d”}

Interface test case test point of login module ：

• The number
  • positive ：
    • Login successful
  • reverse ：
    • User name is empty
    • The user name contains special characters 、 Letter
    • User name exceeds 11 position （12 position ）
    • Insufficient user name 11 position （10 position ）
    • User name is not registered
    • The password is empty.
    • The password contains special characters 、 Letter
    • The password for 1 position
    • The password for 100 position
    • Wrong password
• Parameters （ Interface test specific ）
  • positive ：
    • Required parameters ： Correct user name + Correct password
    • Combination parameter ： Ignore
    • All parameters ： Correct user name + Correct password
  • reverse ：
    • Multiple parameters ： many abc：“123”
    • Shaoshen （ Less mobile）： No user name , Correct password
    • No arguments ： There are no parameters
    • bad parameter ( Wrong phone number parameter name )：abc:1381234567, password:”123456”

User name related 5 strip ：

login_002	User name is empty	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_003	The user name contains special characters 、 Letter	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800&#abc”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_004	User name super 11 position （12 position ）	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“138000000023”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_005	Insufficient user name 11 position （10 position ）	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“1380000000”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_006	User name is not registered	Sign in	p2	Mobile phone number that does not exist in the database	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“16700542479”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}

Password related 5 strip ：

login_007	The password is empty.	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_008	The password contains special characters 、 Letter	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“123&%rt”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_009	password 1 position	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“1”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_010	password 100 position	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“ place 100 A password consisting of characters ”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_011	Wrong password	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“888888”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}

Parameters related ：

login_012	Required parameters （ All parameters ）	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“mobile”:“13800000002”,“password”:“123456”}	Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”,“data”:"f5050a1b-7919-444c-9ec4- 3c1a7286536d "}
login_013	Multiple parameters	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“abc”:“123”,“mobile”:“13800000002”,“password”:“123456”}	Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”,“data”:"f5050a1b-7919-444c-9ec4- 3c1a7286536d "}
login_014	Shaoshen （ Less mobile）	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}
login_015	No arguments	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json		{“success”:false,“code”:99999,“message”:“ I'm sorry , The system is busy , Please try again later ！”,“data”:null}
login_016	bad parameter （mobile Wrong parameter name ）	Sign in	p2	——	POST	{ agreement + domain name }/api/sys/login	Content-Type:application/json	{“abc”:“13800000002”,“password”:“123456”}	Status code ：200 {“success”:false,“code”:20001,“message”:“ Wrong user name or password ”,“data”:null}

Business scenario test cases

• How to use , How to design business .
• With the least number of test cases , Try to cover as many interfaces as possible .

Analyze test points

in the light of “ Employee management ” Business scenario ：

• Sign in —— Add employees —— Query employees —— Modify employees —— Query again —— Delete employee —— Query employee list

Add employees

• Request method ：post

• URL： { agreement + domain name }/api/sys/user

• Request header ：

  • Content-Type： application/json
  • Authorization： Bearer f5050a1b-7919-444c-9ec4-3c1a7286536d （ Specific data source Successful login returns In response body data Value ）

• Request body （ Request data ）：{“username”:“ Einstein ”,“mobile”:“17289432100”,“timeOfEntry”:“2021-07-12”,“formOfEmployment”:1,“departmentName”:“ test 0607”,“departmentId”:“1412421425733664768”,“workNumber”:“234”,“correctionTime”:“2021-07-30T16:00:00.000Z”}

  

• Expected results ：

  • Status code ：200
  • {“success”:true,“code”:10000,“message”:“ Successful operation ！”, “data”:{“id”:“113749504”}}

Use case name	modular	priority	Preset conditions	Request method	URL	Request header	Request body ( Request data ）	Expected results
Add employees	Employee management	p0	Login successful	post	{ agreement + domain name }/api/sys/user	Content-Type： application/json, Authorization： Bearer f5050a1b-7919-444c-9ec4-3c1a7286536d	{“username”:“ Einstein ”,“mobile”:“17289432100”,“timeOfEntry”:“2021-07-12”,“formOfEmployment”:1,“departmentName”:“ test 0607”,“departmentId”:“1412421425733664768”,“workNumber”:“234”,“correctionTime”:“2021-07-30T16:00:00.000Z”}	Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”, “data”:{“id”:“113749504”}}

Query employees

• Request method ：GET
• URL： { agreement + domain name }/api/sys/user/:target
• Request header ：
  • Content-Type： application/json
  • Authorization： Bearer f5050a1b-7919-444c-9ec4-3c1a7286536d （ Specific data source Successful login returns In response body data Value ）
• Request body :
  • nothing
• Return the data ：
  • Status code ：200
  • {“success”: true,
    “code”: 10000,
    “message”: “ Successful operation ！”,
    “data”: { Details of the employee queried } }

emp_manager_002	Query employees	Employee management	p1	Login successful	GET	{ agreement + domain name }/api/sys/user/:target	Content-Type： application/json, Authorization： Bearer f5050a1b-7919-444c-9ec4-3c1a7286536d		Status code ：200 {“success”: true, “code”: 10000, “message”: “ Successful operation ！”, “data”: { Details of the employee queried } }

Modify employees

emp_manager_003	Modify employees	Employee management	p0	Login successful	PUT	{ agreement + domain name }/api/sys/user/:target	Content-Type： application/json, Authorization： Bearer xxx	{“username”:“ Peppa Pig ”}	Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”, “data”:{“id”:“xxx”}}

Returns... In the data id , representative Modified employee id （ It's a data that changes ）.

Delete employee

emp_manager_004	Delete employee	Employee management	p0	Login successful	delete	{ agreement + domain name } /api/sys/user/:target	Content-Type： application/json, Authorization： Bearer xxx		Status code ：200 {“success”:true,“code”:10000,“message”:“ Successful operation ！”,“data”:null}

Query employee list

emp_manager_005	Query employee list	Employee management	p0	Login successful	GET	{ agreement + domain name } /api/sys/user?page=1&size=10	Content-Type： application/json, Authorization： Bearer xxx		Status code ：200 { “success”: true, “code”: 10000, “message”: “ Successful operation ！”, “data”: { “total”: xxxx, “rows” [ {},{},… 10 Details of employees ] } }