Microsoft | patterns & practices | Developer Network | Enterprise Library | Acceptance Testing Guide | Personal Site
Over a year ago, Robert Martin and I wrote a paper on exploring and disambiguating requirements with acceptance tests. In it we formulate the equivalence hypothesis - as formality increases, acceptance tests and requirements become indistinguishable. At the limit, acceptance tests and requirements are equivalent. IEEE Software magazine published it in the January/February’08 issue (http://www.computer.org/portal/cms_docs_software/software/homepage/2008/s1mel.pdf).
As usual, comments are welcomed.
PingBack from http://msdnrss.thecoderblogs.com/2008/01/22/tests-and-requirements-requirements-and-tests-a-mobius-strip/
Good short article on the subject. We came hard and manual way to the similar conclusions with one of our projects. There is no automation tools used though. Any idea how FIT goes along with the VSTS/TFS testing functionality?
Excellent article de Grigori Melnik et Bob Martin sur les tests unitaires, les tests d'acceptation, FIT
As I was going through postings from our internal agile discussion forum (yes, we do have one at Microsoft
This is a good paper. Thanks for writing it.
Can you or anyone else point us to how we would implement this vision inside of TFS / MSF Agile?
Our team is sort of struggling with these distinctions right now.