tag:blogger.com,1999:blog-9138509940389651166.post8921861611118064751..comments2023-07-30T09:24:25.865+01:00Comments on selfelected: Fail At OnceLosManoshttp://www.blogger.com/profile/08166031267431172778noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9138509940389651166.post-73462034055604161472007-11-23T09:18:00.000+01:002007-11-23T09:18:00.000+01:00Exactly.Just like unit tests don't catch all error...Exactly.<BR/>Just like unit tests don't catch all errors, Fail at once does not catch all errors.<BR/><BR/>Heck, even manual tests don't catch all errors.<BR/><BR/>The idea is to use Fail at once to write fewer unit tests to write fewer manual tests.<BR/>To in the end get the same result with less code to maintain.LosManoshttps://www.blogger.com/profile/08166031267431172778noreply@blogger.comtag:blogger.com,1999:blog-9138509940389651166.post-71212316884281254932007-11-21T23:10:00.000+01:002007-11-21T23:10:00.000+01:00// This message in English onlyI hear you and I ag...// This message in English only<BR/><BR/>I hear you and I agree up to a point. To let the compiler catch the bugs catches most programming errors but it does not catch the hard to find and often dangerously destructive ones, i.e. the logical errors. <BR/><BR/>The compiler can never know if you in your comparison used the correct comparison operand, and there is a big difference between >, >=, ==, <=, <, !=, etc. Logical errors are easily found by unit tests that check both normal and extreme value scenarios. Or you could do the same test manually but that would be long and tedious work.Anonymousnoreply@blogger.com