= 27d567bc2d48d9f40e9ccc20ea370b15)
lukstafi comments on Coding Rationally - Test Driven Development - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (82)
We are slowly moving towards languages with contracts (like Spec#), where "unit tests" are replaced by "contract tuning" + "functional tests".
I know about functional programming, but it took a few tries with the google-fu to get information on contract tuning and Spec#, so I'm posting links:
http://en.wikipedia.org/wiki/Design_by_Contract
http://en.wikipedia.org/wiki/Spec_Sharp
BTW, functional programming and functional tests are not related concepts.
...and so we meet again, what I know for sure that just ain't so. Thanks for the correction; and "black-box testing" seems googleabler. One thing unclear from wikipedia (and further references, the most in-depth of which considered HVAC) is the difference between a functional test and a unit test.