Check Output Automatically

Check output automatically is a method for TacticalTesting. One of the requirements of testing is to be able to do something and make sure that you get the right result. But we all know that because we write hard programs, it's hard to tell whether the result is correct or not. The first step is to provide better support. The sort of stuff I am talking about is not rocket science, but it seems that only automated testing requires it. Here are some examples:

Please tell me I have been looking in the wrong place for this sort of code.

-- JohnFarrell

P.S. Thinking outside the dots, a better example is:

See also JournallingPattern


moved here from UnitTests

In the last month I have been writing UnitTests for parts of my code, and I have to say that CheckOutputAutomatically is so much more effective that it should be compulsory.

The advantages are:

The disadvantages are: I am a pretty good programmer, and pretty arrogant about how few bugs there are in my code. When my UnitTests started failing, I was pretty appalled at how talentless I was. Now that I have got the UnitTests in, I can afford to be arrogant again :-). But I no longer claim that there are no bugs in my code when I haven't got a UnitTest for it.

-- JohnFarrell


CategoryTesting


EditText of this page (last edited January 7, 2003) or FindPage with title or text search