Comments on: Unit Testing An NHibernate Application

By: A1104201

A1104201 — Thu, 03 Mar 2011 10:18:00 +0000

ghd planchas ghd ghd IWC led lights

By: Davy Brion

Davy Brion — Mon, 25 Jan 2010 06:02:04 +0000

@RT

you’re right on all counts

By: RT

RT — Mon, 25 Jan 2010 01:02:44 +0000

Just following up on my earlier post…

First things first…It should be constructor instead of construction in my previous post.

Second, I’ll try to answer my own question…The ActiveSessionManager should be implemented without a IRequestState paramater because in a Unit testing environment there is no thread safety issue and there is nothing sysnonymous to HttpContext.Current.Items as in an ASP.net environment. We still need to store the session somewhere; so, we can store it just a private variable in ActiveSessionManager and modify the Current property accordingly.

Am I right?

I’m trying to learn this technology without a mentor.

Thanks

By: RT

RT — Mon, 25 Jan 2010 00:38:41 +0000

Hi,

I was scratching my head over something in your posts here..BTW, great posts…

You instantiate ActiveSessionManager in this class without any parameters. On the other hand, ActiveSessionManager has a single construction with IRequestState as a parameter. So, the code will not compile. Am I missing something?

Thanks.

By: Weekly Links #83 | GrantPalin.com

Weekly Links #83 | GrantPalin.com — Sun, 13 Dec 2009 22:57:41 +0000

[...] Unit Testing An NHibernate Application Integration testing more like, but still very useful information for creating automated tests for a .NET project that uses NHibernate. [...]

By: Grant Palin

Grant Palin — Mon, 07 Dec 2009 23:47:36 +0000

So, so grateful. Straight to the bookmarks.

This post fills an important piece of the NHibernate puzzle that I am currently working on. I’ve known that it is important to test as much of your code as possible, but I didn’t know how you would do it with NH involved. It seems clear to me that integration tests, rather than unit tests, are appropriate in this situation, and the transaction-rollback technique makes more sense.

There are other pieces in the NH puzzle that have yet to be filled, but this important one is done now. I’ll be referring back to this post – and your other posts on NH – once my new project gets a little further along.

By: Renana

Renana — Mon, 07 Dec 2009 12:39:50 +0000

Great post, great timing.

I just entered the world of unit testing and ActiveRecords. I was writing test with the “new database” scenario and will switch to the “rollback” scenario which will suit me more since I prefer to do my testings on a bit more complex database.

Thanks,
Renana

By: Joe

Joe — Mon, 07 Dec 2009 09:43:20 +0000

Cool,

I’ve been using MBUnit for testing and this has a nice little attribute [RollBack] that will rollback any transactions on the database.

Thanks, Joe

By: Jonathan Adams

Jonathan Adams — Mon, 07 Dec 2009 09:18:23 +0000

Great post Davy, one point, these are Integration tests not unit tests and should be run away from your unit tests.

But great post !

By: Reflective Perspective - Chris Alcock » The Morning Brew #492

Reflective Perspective - Chris Alcock » The Morning Brew #492 — Mon, 07 Dec 2009 08:35:15 +0000

[...] Unit Testing An NHibernate Application – Davy Brion talks about two means of doing having Unit Tests which test an NHibernate applications interactions with a database, test that rollback the database changes, and test which create a new database for each test/fixture, showing how each can be achieved [...]

By: Davy Brion

Davy Brion — Mon, 07 Dec 2009 06:02:49 +0000

@Sean,

i’ll post the base class for the CRUD tests later today

By: Sean Gough

Sean Gough — Mon, 07 Dec 2009 01:42:41 +0000

Wow, your timing couldn’t be better as I just started experimenting with this last week. So thanks a ton for posting this! I agree that testing CRUD ops is key, but it always seems messy when I actually try to do it thoroughly. Can you shed some light on how you test each entity automatically?