Comments on: Testing Hibernate mappings: Setting up test data http://www.markhneedham.com/blog/2008/10/30/testing-hibernate-mappings-setting-up-test-data/ Thoughts on Software Development Sat, 11 Feb 2012 23:17:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: TDD: Driving from the assertion up at Mark Needham http://www.markhneedham.com/blog/2008/10/30/testing-hibernate-mappings-setting-up-test-data/comment-page-1/#comment-39327 TDD: Driving from the assertion up at Mark Needham Mon, 14 Jun 2010 23:17:45 +0000 http://www.markhneedham.com/blog/?p=561#comment-39327 [...] test in question was an integration test and we were following the approach of saving the test object directly through the NHibernate session and then loading it again through a [...] [...] test in question was an integration test and we were following the approach of saving the test object directly through the NHibernate session and then loading it again through a [...]

]]> By: Anders S http://www.markhneedham.com/blog/2008/10/30/testing-hibernate-mappings-setting-up-test-data/comment-page-1/#comment-1155 Anders S Thu, 06 Nov 2008 13:14:32 +0000 http://www.markhneedham.com/blog/?p=561#comment-1155 I agree with Kris. I would prefer doing it with Hibernate over SQL. I have experienced severe pain after refactorings on a project where too much was set up with SQL. I agree with Kris. I would prefer doing it with Hibernate over SQL. I have experienced severe pain after refactorings on a project where too much was set up with SQL.

]]> By: Kris Kemper http://www.markhneedham.com/blog/2008/10/30/testing-hibernate-mappings-setting-up-test-data/comment-page-1/#comment-1063 Kris Kemper Sat, 01 Nov 2008 22:32:51 +0000 http://www.markhneedham.com/blog/?p=561#comment-1063 I prefer the approach of using Hibernate to setup test data. Injecting data using sql quickly results in hard to maintain test code, and it won't tell you when you violate validation logic that happens on the domain object (if you validate before save). Using sql to inject data is best used when you need to test some condition that you can can't get to via hibernate. In practice, I'm not too bothered by the fact that you test a save and a load, you can always write test helpers when the application save logic differs from what you want to do. In the end, when you are using SQL to inject, you are really testing that the SQL works as well, but that check provides less value since it (probably) isn't used by the production code. I prefer the approach of using Hibernate to setup test data. Injecting data using sql quickly results in hard to maintain test code, and it won’t tell you when you violate validation logic that happens on the domain object (if you validate before save).

Using sql to inject data is best used when you need to test some condition that you can can’t get to via hibernate.

In practice, I’m not too bothered by the fact that you test a save and a load, you can always write test helpers when the application save logic differs from what you want to do.

In the end, when you are using SQL to inject, you are really testing that the SQL works as well, but that check provides less value since it (probably) isn’t used by the production code.

]]>