How much should I test? (2) -- Do not let the details go.

Suppose we are testing a webpage input box for an email address. The following describes the requirements:

After entering an "email" in the text box, click "save". If the correct email address is entered, the email address is transferred to the next page. Otherwise, a message box is displayed, "The email you entered is not a qualified email. Please enter it again ". After clicking the "OK" button, the focus falls back into the email address input box, And the cursor is placed behind the last text in the text box. No selected text. The original input text content remains unchanged.

So how much should we test?

1. Do you want to test the messages displayed in the dialog box?

2. Click OK in the dialog box to test?

3. Click the close button in the dialog box to test?

4. Do I need to test the focus fall?

5. Do you want to test the cursor position?

6. Do you want to test the selected text?

7. Do you want to test the text content in the text box?

 

The answer is: test.

 

If there are omissions in the test, it is likely to become the omission point of the bug.

Think about how many bugs in your project are detected by others (test groups and customers) because the tests are insufficient.

Therefore, the test should be as comprehensive as possible.

From the two perspectives of comprehensive test case design types and Test details in the previous chapter, will the testing work hours be quite expanded?