Testing testing testing
November 5th, 2005 at 10:35 pm
If I develop a (software) system for you, at your request, and I ask you to evaluate that system, you should do more than just load it up, look at it, determine that it appears, in a visual sense, to have all the features you asked for, and call it done. I’m not looking for formal acceptance testing here, but just the mere appearance of a text box labeled “Foo:” and a button saying “Bar!” does not mean that
- my foos are the sort of foos you think of when you think of foos,
- my idea of bar-ing matches your idea of bar-ing,
- the baz thing you wanted to happen with the bar-ed foos ever happens at all, or
- things aren’t otherwise quuxed up in all manner of unforeseen ways.
Because you haven’t bothered to test the system!
maxg
Both comments and trackbacks are closed.
This is a test of the new, upgraded, and hopefully working comment system…do not be alarmed, this is just a test.
Mike Z. | November 7th, 2005 at 05:17 pm
Yet more testing
Mike Z. | December 14th, 2005 at 04:48 am
Hmm…a Heisenbug, perhaps?
Mike Z. | December 14th, 2005 at 04:48 am