Equivalence class and boundary value of software test case design method

It seems that these two are used, and then some scenarios, some process-related use cases are separately pulled out to form scenario use cases, imitating users' common operations

demand:

Login function
Mobile phone number and password login, the password length cannot be less than 6 digits and cannot exceed 12 digits

Equivalence class

Effective equivalent:
mobile phone number 15576152333, password lll1234, click the login button. Login successfully.
Mobile phone number 15576152339, password lll12349876, click the login button. Landed successfully

Invalid equivalence class

Mobile phone number 155761523**, password lll1234, click the login button. The format of the mobile phone number is incorrect.
Mobile phone number 15576152333, password lll1236 (wrong password), click the login button. The password is incorrect. The
phone number is empty and the password is lll1234. Click the login button. The phone number cannot be empty. The
phone number is 15576152333 and the password is empty. Click the login button. password can not be blank

Boundary value
Mobile phone number 15576152333, password lll1234, click the login button. Log in successfully.
Mobile phone number 1557615233, password lll1234, click the login button. The format of the phone number is incorrect. The
phone number is 15576523312 and the password is lll1234. Click the login button. The format of the mobile phone number is incorrect.
Mobile phone number 15576152333, password lll18, click the login button. The password format is incorrect.
Mobile phone number 15576152333, password ll0123456789l, click the login button. Incorrect password format

Guess you like

Origin blog.csdn.net/aaaaaaaaanjjj/article/details/115298850
Recommended