Comments on: Grails Testing Tip (DO’s, DONT’s and DOH’s): The Clean Slate Principle http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/ Results through imagination Mon, 15 Mar 2010 02:56:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: ALTERthought Blogs » Grails Testing Tip (DO’s, DONT’s and DOH’s): Fixture Data vs. Dependent Data http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19725 ALTERthought Blogs » Grails Testing Tip (DO’s, DONT’s and DOH’s): Fixture Data vs. Dependent Data Fri, 05 Sep 2008 13:48:54 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19725 [...] Upon test case completion, any Fixture Data that was added to the system should be removed, leaving the database in a clean state (see The Clean Slate Principle), containing only Dependent Data. Data should be removed in one of the following ways: [...] [...] Upon test case completion, any Fixture Data that was added to the system should be removed, leaving the database in a clean state (see The Clean Slate Principle), containing only Dependent Data. Data should be removed in one of the following ways: [...]

]]> By: Edward http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19419 Edward Tue, 26 Aug 2008 17:26:21 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19419 @Mike - cool, but typically database transactions can't roll back non-database updates such as external files, registry updates etc. I still think it's best for test suites to prepare their own test beds rather than assuming (or hoping as I put it) that the environment is ready and waiting for them. @don - so I jumped the gun? :-) I often do... @Mike – cool, but typically database transactions can’t roll back non-database updates such as external files, registry updates etc.

I still think it’s best for test suites to prepare their own test beds rather than assuming (or hoping as I put it) that the environment is ready and waiting for them.

@don – so I jumped the gun? :-) I often do…

]]> By: don http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19418 don Tue, 26 Aug 2008 17:24:35 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19418 @Mike - Yes this is the default case, however sometimes necessary to override this behavior for certain complicated scenarios (multiple datasources, etc) by setting boolean transactional = false in the test case. @Mike – Yes this is the default case, however sometimes necessary to override this behavior for certain complicated scenarios (multiple datasources, etc) by setting boolean transactional = false in the test case.

]]> By: Mike http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19417 Mike Tue, 26 Aug 2008 17:18:49 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19417 Actually - Grails test methods are wrapped in a transaction that rollsback when the test method completes - so your tests don't really have to be responsible for cleaning up any data that they insert/update Actually – Grails test methods are wrapped in a transaction that rollsback when the test method completes – so your tests don’t really have to be responsible for cleaning up any data that they insert/update

]]> By: don http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19416 don Tue, 26 Aug 2008 17:09:23 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19416 @Edward- Actually I have a couple of other posts in this series that talk about approaches for maintaining clean slate integrity between test runs (via setUp()/tearDown() methods, dbunit, and SQL scripts, etc...), but wanted to introduce the basic principle first as it is referenced in the subsequent posts. Thanks for the comment... @Edward- Actually I have a couple of other posts in this series that talk about approaches for maintaining clean slate integrity between test runs (via setUp()/tearDown() methods, dbunit, and SQL scripts, etc…), but wanted to introduce the basic principle first as it is referenced in the subsequent posts. Thanks for the comment…

]]> By: Edward http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/comment-page-1/#comment-19414 Edward Tue, 26 Aug 2008 17:04:26 +0000 http://alterlabs.com/technologies/java/grails-testing-tip-dos-donts-and-dohs-the-clean-slate-principle/#comment-19414 Sure, tests should not trash the database, but this rule is perhaps a little optimistic? (Relying on the hope that nothing upsets the database between the completion of a test and the start of another, possibly an indeterminate period of time) Practically speaking, a test suite should have a set-up function which prepares data before tests run, plus a test can check for prerequisites. Sounds like your test didn't check pre-requisites and had no associated set-up. Living in hope? Sure, tests should not trash the database, but this rule is perhaps a little optimistic? (Relying on the hope that nothing upsets the database between the completion of a test and the start of another, possibly an indeterminate period of time)

Practically speaking, a test suite should have a set-up function which prepares data before tests run, plus a test can check for prerequisites.

Sounds like your test didn’t check pre-requisites and had no associated set-up. Living in hope?

]]>