CNZBA registration module test case

[FenWangNZ]

Requirements: Required fields include name, password, email, etc.

Use case 1: Verify that required fields can be null

• The required items are left blank in turn to see if the system processing meets expectations (the system will prompt to enter the next required item)
• Until all required fields are not empty, it can be saved correctly

Use case 2: Verification of fields with special character requirements

• Enter all required fields to see the system response (the system will prompt that required fields cannot be empty)
• If there are other special characters, the system will prompt that the required items cannot be special characters, please enter characters or numbers similar to the prompt

Use case 3: Verification of valid boundary values of registration items

• The input character is equal to the maximum, minimum, and middle value allowed in the field. The system prompts that the registration is successful.

Use case 4: Invalid boundary value verification for registration items

• The number of characters entered does not belong to the length of the boundary value, and the system prompts a warning such as please re-enter.

Use case 5: Check the uniqueness of registered users

Use case 6: Verify that the registration password is the same (whether the same password is entered)

Use case 7: Check the system expires (for example, after filling in the information, do not register, register after more than 10 minutes, whether the system exits over time)

Use case 8: Case verification (case sensitive: for example, if abc is successfully registered, an error will be reported when logging in with ABC, so you can register another ABC; case insensitive: logging in with ABC is successful, and you can no longer register ABC)

Use case 9: Verification of page switching (enter the registration item, do not register, go back, and then go forward to see if the password is cleared)

Use case 10: Perform shortcut keys such as enter, tab, etc., copy and paste, database, UI interface testing, performance verification

Summary:

• For the verification of text boxes, I generally use the scenario method. The ultimate goal is to create an effective use case, but when entering each input box, combine the equivalence class, boundary value, and error speculation method for the input box Verification, such as verifying the abnormal ones such as blanks, special characters, and boundaries first, see the system prompts. Then ensure that all data are entered correctly. Then enter the effective value. Finally, the operation was successful.

• It looks like 5 use cases, but in fact it can be said to be 5 test suites, each with different test data.

  Note:

• I personally feel that the shortcut keys, copy and paste, and UI in Example 10 can be tested during the 1-9 test. The performance cannot be tested at this time, and the performance test can be performed after the system is stable.

[FenWangNZ]

Modify after discussion with Stephen