The most critical aspect of a good Acceptance Test is a set of good requirements. Without solid, well-defined requirements, you can’t know what to test the application against – specifically – the set of expected features that the application or system must fulfill.
We’ve seen requirements ranging from lists of very detailed items to broad features. The very detailed lists, such as “the XML command must contain the following elements…” are especially important when your system needs to interface with other systems being defined elsewhere or you need to deliver specific functionality to your end-users. Effective requirements also specify how the system should react to certain situations and power failure.
To learn how to create the proper system requirements for an effective Acceptance Test, read the entire article here.