Unit test help avoiding *some* bugs and they prove *some* correctness. What I'm trying to say is that it is impossible to have full circle unit tests. Even national aerospace laboratories can't achieve it.
As a side note, yes in the aerospace domains many systems have proven correctness. Although this is done by working with further constraints as opposed to unit tests. As an example you can prove rather easily that a state machine will eventually reach a completion point for all possible inputs. This seems to be breaking the halting problem http://en.wikipedia.org/wiki/Halting_problem but its actually not as the state machines are not turing complete. Didn't mean to jump in but its an interesting side note (I think). Greg As a side note, On Mon, Aug 16, 2010 at 2:23 PM, Vadim Chekan <[email protected]> wrote: > On Aug 13, 11:42 am, Diego Mijelshon <[email protected]> wrote: > > On Fri, Aug 13, 2010 at 14:56, Vadim Chekan <[email protected]> > wrote: > > > On Aug 12, 7:28 pm, Diego Mijelshon <[email protected]> wrote: > > > > Seriously? > > > > > > Do you know what a unit test is? > > > > > Of course, it is a silver bullet which magically eliminates bugs. No? > > > I'm sure you know that no unit test gives any guarantee. It gives you > > > feeling that the app is in descent shape after changes, but nothing > > > more. > > > > No. Unit tests are what you use to avoid introducing new bugs AND > asserting > > correctness (among other things) > > In my BIG application, I automatically generate a small persistence test > for > > each entity (a modified ghostbuster). > > If, for example, a field name is wrong, I'll get a failing test. > > > > There's absolutely NO difference between what XML and FNH can do about > this. > > See my last point in this email too. > > Unit test help avoiding *some* bugs and they prove *some* correctness. > What I'm trying to say is that it is impossible to have full circle > unit tests. Even national aerospace laboratories can't achieve it. > They allow programmer to not be embarrassed when passing the app to > QA, but in no way they are substitution to the QA. > > > > > Have you ever used a real refactoring tool (like R#)? > > > > > I state that xml editing is not easy. And your argument that it > > > requires (or is recommended) to use R# just proves my point. > > > > If you are a professional developer, you'll use the best available tools. > > Of course you can install the .NET SDK and work in Notepad if you want, > but > > then don't complain about C# editing being hard. > > Or you use programming techniques that yield reliable code :) > > > > > Do you understand what Configuration.BuildSessionFactory does? > > > > > Builds session factory? :) What is your question really? > > > > It compiles the configuration. Just like csc.exe compiles C#. > > You said "Static check is safer then dynamic error". And that's not the > > point, because the first test I write for a NH solution is the > > "ConfigurationIsValid", which is essentially a build-time check. > > Are you saying that NH's configuration builder will catch all errors > which FNH would catch? > > > Diego > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de votre attention -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
