You are currently viewing Test Cases For Error Messages

Test Cases For Error Messages

4.2/5 - (13 votes)

Test Cases required for testing the Error messages

Table of Contents

  1. Check spellings for the error message correct or not.
  2. Verify that the grammar for the error messages correct.
  3. Verify the error message for blank input is shown.
  4. Verify an error message for uploading an empty file shown or not.
  5. Check an error message should be shown for the maximum or upper limit.
  6. Verify if the error message shown for the files not supportable by the tool.
  7. As an error message is shown for blank input or limit after it user should be able to click and interact with the software.
  8. Verify confirmation message on email registration.
  9. Verify an error message should be shown in case if the user adds minimum words or content than the allowed limit.
  10. Check the error message should be shown for the invalid URL.
  11. A proper error message should be shown for invalid captcha.
  12. Verify and check a proper error message should be shown if captcha is not loaded.
  13. Verify and check that the same format should be used for displaying all the error messages. It may include uppercase, lower case, or sentence case.
  14. verify error message position should be aligned.
  15. 500 error message page should be shown to the user.
  16. Red color is used for displaying the error message to the user.
  17. For info and confirmation blue or green color can be used.
  18. Verify the time duration for the error message shown.

Characteristics of the test cases.

Here we are going to discuss about the key characteristics for writing the error messages. And test cases commonly used for websites, desktop software and mobile applications. 

Characteristics for good error message majorly includes.

  • An error message should be concise, understandable and well explained to the user.
  • An error message should be clearly displaying the instructions and should not be ambiguous.
  • Error messages should be written in gracefully and do not blame the user.
  • Error messages vary from field to field. These should be properly aligned specifically for the field on which an error message is encountered.
  • Describe the user clear directions. Users should not feel blocked and jammed.