Comments on: Evaluating Frameworks http://technovangelism.com/blog/2009/04/14/evaluating-frameworks/ Technova for short Wed, 07 Apr 2010 17:32:56 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Nick http://technovangelism.com/blog/2009/04/14/evaluating-frameworks/comment-page-1/#comment-48 Nick Wed, 15 Apr 2009 06:43:53 +0000 http://technovangelism.com/blog/?p=195#comment-48 <p>Grails does have unit and integration testing built in. Whenever you create a new class, Grails automatically generates the test files (unit and integration) associated with the file. Functional testing is handled by plugins, thankfully.</p> <p>The framework having tests on itself would be great for less-mature frameworks. There are portions of Grails that I would like to change, and an built-in test suite would ensure that I do not break other parts of the framework when making modifications.</p> Grails does have unit and integration testing built in. Whenever you create a new class, Grails automatically generates the test files (unit and integration) associated with the file. Functional testing is handled by plugins, thankfully.

The framework having tests on itself would be great for less-mature frameworks. There are portions of Grails that I would like to change, and an built-in test suite would ensure that I do not break other parts of the framework when making modifications.

]]> By: erik http://technovangelism.com/blog/2009/04/14/evaluating-frameworks/comment-page-1/#comment-49 erik Tue, 14 Apr 2009 16:28:31 +0000 http://technovangelism.com/blog/?p=195#comment-49 <p>Rails, and I assume Grails, comes with a huge test suite on itself. Check out http://github.com/rails/rails/tree/master and look inside the folders and you'll find a "test" directory that is filled with tests. In fact, when contributing code to Rails, the core team will not accept your changes unless it comes with a testcase(s) proving your changes work.</p> Rails, and I assume Grails, comes with a huge test suite on itself. Check out http://github.com/rails/rails/tree/master and look inside the folders and you’ll find a “test” directory that is filled with tests. In fact, when contributing code to Rails, the core team will not accept your changes unless it comes with a testcase(s) proving your changes work.

]]> By: David http://technovangelism.com/blog/2009/04/14/evaluating-frameworks/comment-page-1/#comment-47 David Tue, 14 Apr 2009 15:47:37 +0000 http://technovangelism.com/blog/?p=195#comment-47 <p>One thing I've been pondering lately is testing of the framework itself. I love that Rails/Grails/etc does a lot of the work for me, but when I think of testing, I realize I place a lot of faith in the framework/language itself. Do you see any value in frameworks coming with built-in tests on itself?</p> One thing I’ve been pondering lately is testing of the framework itself. I love that Rails/Grails/etc does a lot of the work for me, but when I think of testing, I realize I place a lot of faith in the framework/language itself. Do you see any value in frameworks coming with built-in tests on itself?

]]>