Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm building an application at the moment and something I want to do is document input validation rules and system/error messaging in a readable format so that it can be used for SIT/UAT etc.

Currently I'm just using an excel table along the lines of the following which doesn't seem ideal:

Form  |  Section  |  Field Name  |  Rule  |  Valid Data  |  Message

Checkout | Personal Details | First Name | Required | - | Please enter your first name
Checkout | Personal Details | First Name | Format | A-Z,a-z,-,' | Please limit your name to valid characters (A-Z,a-z,-,')

Are there any standards or good examples for documenting validation rules and system/error messaging?

share|improve this question
I've something similar in the past (although I don't have an example around). Consider adding things like max length, target db table+column, etc – Joe Strazzere May 14 '14 at 21:39
up vote 1 down vote accepted

Using Excel or a database does have the benefit of being available for use in automated test cases down the road, from which you can pull expected values. Added to source control or posted to a sharepoint site for easy transfer within the proper audience, this is a flexible and useful way to document these expected messages.

However, if you're looking for alternatives, you could always set the message, rule, and other pertinent information in the test case itself as a parameter row.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.