« The hymn microformat (HMML?)So that's why Americans abandoned Brit spellings »

Various definitions of "correct functioning"


Permalink 10:46:07 am, by fumanchu Email , 110 words   English (US)
Categories: IT

Various definitions of "correct functioning"

From Coding Horror

Unit tests don't guarantee correct functioning of a program. I think it's unreasonable to expect them to. But writing unit tests does guarantee that the developer has considered, however briefly, these truly difficult testing questions. And that's clearly a step in the right direction.

It may be a step in the right direction. Here's the next step: turn those "developer considerations" into functional requirements, and then use those to define "correct functioning". Then you'll have your guarantee. It isn't the unreasonable guarantee you started with, but it's a heck of a lot better than the second gurantee you offered, Jeff. ;)


Comment from: Jeff Atwood [Visitor] · http://www.codinghorror.com/blog/

That's really outside the scope of unit testing; I think we'd need acceptance tests to verify that our software actually met the functional requirements.

04/16/05 @ 11:54
Comment from: fumanchu [Member] Email

I think I threw you by coopting the phrase "functional requirements", which often refers to the client's requirements. I'm not talking about that at all. I'm only saying that your unit tests provide stronger guarantees than simply "the developer has thought about it".

04/16/05 @ 12:13
Comment from: Baju Muslim [Visitor] · http://www.bajumuslimwanita.net

Nice post... I've following this blog

11/13/16 @ 04:46

Leave a comment

Your email address will not be revealed on this site.

Your URL will be displayed.

Please enter the phrase "I am a real human." in the textbox above.
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)
April 2018
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          


The requested Blog doesn't exist any more!

XML Feeds

powered by b2evolution free blog software