Comments on: Testing CRUD Operations With NHibernate http://davybrion.com/blog/2009/12/testing-crud-operations-with-nhibernate/ Trying to walk that thin line between intelligence and ignorance Thu, 29 Jul 2010 20:54:12 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Ere Thrice the Sun Done Salutation to the Dawn « Search And Destroy http://davybrion.com/blog/2009/12/testing-crud-operations-with-nhibernate/comment-page-1/#comment-25039 Ere Thrice the Sun Done Salutation to the Dawn « Search And Destroy Fri, 15 Jan 2010 11:03:14 +0000 http://davybrion.com/blog/?p=2015#comment-25039 [...] by kilfour on January 15, 2010 A while ago davy brion posted a nice base class for nhbirnate crud tests, which i eagerly [...] [...] by kilfour on January 15, 2010 A while ago davy brion posted a nice base class for nhbirnate crud tests, which i eagerly [...]

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #493 http://davybrion.com/blog/2009/12/testing-crud-operations-with-nhibernate/comment-page-1/#comment-23125 Reflective Perspective - Chris Alcock » The Morning Brew #493 Tue, 08 Dec 2009 08:41:19 +0000 http://davybrion.com/blog/?p=2015#comment-23125 [...] Testing CRUD Operations With NHibernate - Davy Brion shares a simple base class which provides the groundwork for testing Create Read Update and Delete functionality of NHibernate types [...] [...] Testing CRUD Operations With NHibernate – Davy Brion shares a simple base class which provides the groundwork for testing Create Read Update and Delete functionality of NHibernate types [...]

]]> By: Davy Brion http://davybrion.com/blog/2009/12/testing-crud-operations-with-nhibernate/comment-page-1/#comment-23122 Davy Brion Tue, 08 Dec 2009 06:09:38 +0000 http://davybrion.com/blog/?p=2015#comment-23122 @Grant the class shown in this post is only useful to test the correctness of your mappings by making sure that CRUD operations work for all entities. and as mentioned in the previous post, we also write tests for each specific custom query that we write. our higher level code (the one that indees communicates with repositories for all NH-related tasks) is always tested with mocked repositories. @Grant

the class shown in this post is only useful to test the correctness of your mappings by making sure that CRUD operations work for all entities. and as mentioned in the previous post, we also write tests for each specific custom query that we write.

our higher level code (the one that indees communicates with repositories for all NH-related tasks) is always tested with mocked repositories.

]]> By: Grant Palin http://davybrion.com/blog/2009/12/testing-crud-operations-with-nhibernate/comment-page-1/#comment-23118 Grant Palin Mon, 07 Dec 2009 23:52:30 +0000 http://davybrion.com/blog/?p=2015#comment-23118 Just came from your previous post. This is a nice follow-up, another worthy of bookmarking! Supposing that you follow the multi-layer approach to your project, this code would be used in testing persistence with NHibernate, right? So higher-level code which would normally interact with NH-backed repositories would actually interact with fake version of such, just so you can keep the different test types separate...Am I right?? Just came from your previous post. This is a nice follow-up, another worthy of bookmarking!

Supposing that you follow the multi-layer approach to your project, this code would be used in testing persistence with NHibernate, right? So higher-level code which would normally interact with NH-backed repositories would actually interact with fake version of such, just so you can keep the different test types separate…Am I right??

]]>