Comments on: Unit Testing Delete Actions in Grails http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/ Wed, 16 Dec 2009 22:09:57 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: j pimmel http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-67 j pimmel Wed, 09 Sep 2009 01:56:14 +0000 http://www.caffeinated.at/?p=80#comment-67 Minor, but my preference is to separate testing domain object constraints using unit tests and then use integration tests for queries/HQL and anything else really. .-= j pimmel´s last blog ..<a href="http://feedproxy.google.com/~r/actualise/tech/~3/daR-liK0k2U/" rel="nofollow">Selenium has evolved; enter Bromine</a> =-. Minor, but my preference is to separate testing domain object constraints using unit tests and then use integration tests for queries/HQL and anything else really.
j pimmel´s last blog ..Selenium has evolved; enter Bromine My ComLuv Profile

]]> By: Flo http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-66 Flo Mon, 07 Sep 2009 18:56:28 +0000 http://www.caffeinated.at/?p=80#comment-66 Oh yes, I actually ran into that problem with Criteria and HQL! Oh yes, I actually ran into that problem with Criteria and HQL!

]]> By: Flo http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-65 Flo Mon, 07 Sep 2009 18:55:54 +0000 http://www.caffeinated.at/?p=80#comment-65 To be honest it was not my decision but a requirment to unit test those classes. After playing around a bit I encountered some situations where i needed to rewrite the controller code to make the test pass which I think is really annoying and error-prone. Also I had some issues regarding dynamic methods like countBy* which is not provided in current version but has been added to git head by Graeme recently. I would also favour integration tests I think. To be honest it was not my decision but a requirment to unit test those classes. After playing around a bit I encountered some situations where i needed to rewrite the controller code to make the test pass which I think is really annoying and error-prone. Also I had some issues regarding dynamic methods like countBy* which is not provided in current version but has been added to git head by Graeme recently. I would also favour integration tests I think.

]]> By: Burt Beckwith http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-64 Burt Beckwith Sun, 06 Sep 2009 17:57:34 +0000 http://www.caffeinated.at/?p=80#comment-64 I didn't say I don't test domain classes, I said I use integrations tests for those. I want them to run in a database, otherwise their persistence isn't really tested, only constraints, etc. to the extent that the testing plugin has implemented that. How would you test domain class methods that use HQL or Criteria queries using mocks? Having tested the domain classes, then I'm comfortable mocking them out to test controllers, services, etc. since they're tested and just a dependency - I'm only concerned that the controller logic is correct when testing controllers, I don't worry about the domain classes and just mock out their return values. I didn’t say I don’t test domain classes, I said I use integrations tests for those. I want them to run in a database, otherwise their persistence isn’t really tested, only constraints, etc. to the extent that the testing plugin has implemented that. How would you test domain class methods that use HQL or Criteria queries using mocks?

Having tested the domain classes, then I’m comfortable mocking them out to test controllers, services, etc. since they’re tested and just a dependency – I’m only concerned that the controller logic is correct when testing controllers, I don’t worry about the domain classes and just mock out their return values.

]]> By: Flo http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-61 Flo Sat, 05 Sep 2009 08:17:48 +0000 http://www.caffeinated.at/?p=80#comment-61 Hi Burt! Thanks for your reply! Normally the delete operation would be somewhere deep in a controller, as it was in my real case. So you think it makes no sense mocking domain classes and unit testing them? The testing plugin would be pretty useless then...? Indeed you rely on the testing framework but it has been tested itself. Don't you have to trust in an implementation when using a framework? IMHO I think you can test business logic quite good! I'm quite new to that topic so thanks for your feedback! Hi Burt! Thanks for your reply! Normally the delete operation would be somewhere deep in a controller, as it was in my real case. So you think it makes no sense mocking domain classes and unit testing them? The testing plugin would be pretty useless then…? Indeed you rely on the testing framework but it has been tested itself. Don’t you have to trust in an implementation when using a framework? IMHO I think you can test business logic quite good! I’m quite new to that topic so thanks for your feedback!

]]> By: Burt Beckwith http://www.caffeinated.at/2009/09/unit-testing-delete-actions-in-grails/comment-page-1/#comment-60 Burt Beckwith Fri, 04 Sep 2009 23:16:22 +0000 http://www.caffeinated.at/?p=80#comment-60 I don't test domain classes using mocks, you're just testing the mocking framework with code like this. I prefer to use integration tests for domain class tests, and use mocks only when testing classes that depend on domain classes (controllers, services, etc.) since I know that they work since they're already tested. I don’t test domain classes using mocks, you’re just testing the mocking framework with code like this. I prefer to use integration tests for domain class tests, and use mocks only when testing classes that depend on domain classes (controllers, services, etc.) since I know that they work since they’re already tested.

]]>