The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January/February (2008 vol.25)
pp: 54-59
Robert C. Martin , Object Mentor Inc.
Grigori Melnik , University of Calgary and Microsoft
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.
INDEX TERMS
acceptance testing, requirements engineering, executable specification, FIT, Framework for Integrated Testing, FitNesse
CITATION
Robert C. Martin, Grigori Melnik, "Tests and Requirements, Requirements and Tests: A M?bius Strip", IEEE Software, vol.25, no. 1, pp. 54-59, January/February 2008, doi:10.1109/MS.2008.24
REFERENCES
1. D. Gause and G. Weinberg, Exploring Requirements, Dorset House, 1989, p. 249.
2. D. Graham, "Requirements and Testing: Seven Missing-Link Myths," IEEE Software, vol. 19, no. 5, 2002, pp. 15–17.
3. B. Hetzel, The Complete Guide to Software Testing, QED Information Sciences, 1983.
4. G. Meszaros, "Agile Regression Testing Using Record &Playback," Companion of the 18th Ann. ACM SIGPLANConf. Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA03), ACM Press, 2003, pp. 353–360.
5. R. Janicki, D. Parnas, and J. Zucker, Tabular Representations in Relational Documents, Communications Research Laboratory, McMaster University, 1995, p. 5.
6. R. Mugridge and W. Cunningham, Fit for Developing Software, Prentice Hall, 2005.
7. I. Alexander and N. Maiden, Scenarios, Stories, Use Cases through the Systems Development Life-Cycle, John Wiley &Sons, 2004, p. 5.
8. C. Potts, K. Takahashi, and A. Antón, "Inquiry-Based Requirements Analysis," IEEE Software, vol. 11, no. 2, 1994, pp. 21–32.
9. G. Melnik, F. Maurer, and M. Chiasson, "Executable Acceptance Tests for Communicating Business Requirements: Customer Perspective," Proc. Agile 2006 Conf., IEEE CS Press, 2006, pp. 35–46.
10. C. Kaner, "On Scenario Testing," Software Testing and Quality Eng. Magazine, Sept./Oct. 2003, pp. 16–22.
11. E. Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software, Addison-Wesley, 2004, p. 376.
12. K. Weidenhaupt t al., "Scenarios in System Development: Current Practice," IEEE Software, vol. 15, no. 2, 1998, pp. 34–45.
13. M. Fowler, "Continuous Integration," www.martinfowler.com/articlescontinuousIntegration.html , May 2006.
10 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool