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. > > 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. > > 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. 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]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
