| Authors | Martin, R.C., Melnik, G. |
| Source | IEEE SoftwareVolume 25Issue 1 (2008) |
| URL | http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/mags/so/&toc=comp/mags/so/2008/01/mso01toc.xml&DOI=10.1109/MS.2008.24 |
| Keywords | Requirements, Acceptance Testing |
| Abstract | Writing acceptance tests early is a requirements-engineering technique that can save businesses time and money and help them better respond to change. An equivalence hypothesis states that concrete requirements blend with acceptance tests so that you should be able to specify and verify system behavior using tests. Several examples in the FIT (Framework for Integrated Testing) demonstrate the approach. (from IEEE web site) |
This articled shows that FIT (Framework for Integrated Testing) style acceptance test definitions can be used as a mechanism for developing system acceptance tests before the system is actually built. The idea is to get the stakeholders to define the acceptance tests in a simple, table driven format that can then be used to drive the system and prove that it meets its requirements.
The article shows how to define scenarios that the system must meet. The scenarios are written in a logical fashion that should allow anyone to understand and adapt for different types of testing. Simultaneous access to the system can also be specified and tested using this method.
The article presents the notion that the software requirements written in this format are actually acceptance tests, and the acceptance tests are the requirements. It's an interesting concept, and one that has some merit.