Comments on: Plug-in Development Workflow http://aniszczyk.org/2007/12/30/plug-in-development-workflow/ work. life. open source. diatribes. Fri, 03 Feb 2012 17:01:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Chris Aniszczyk (zx) http://aniszczyk.org/2007/12/30/plug-in-development-workflow/comment-page-1/#comment-575 Chris Aniszczyk (zx) Thu, 03 Jan 2008 19:36:00 +0000 http://aniszczyk.org/2007/12/30/plug-in-development-workflow/#comment-575 It all depends on your workflow :)<br/><br/>I'm a fan of test-driven development but to a certain extent. I'm almost a realist and writing all your tests before you write any "business code" is just crazy. I say do a mix of both with eclmma mixed in and you'll have your code coverage on the fly and fill in the blanks when the time comes. It all depends on your workflow :)

I’m a fan of test-driven development but to a certain extent. I’m almost a realist and writing all your tests before you write any “business code” is just crazy. I say do a mix of both with eclmma mixed in and you’ll have your code coverage on the fly and fill in the blanks when the time comes.

]]> By: Chris Aniszczyk (zx) http://aniszczyk.org/2007/12/30/plug-in-development-workflow/comment-page-1/#comment-2667 Chris Aniszczyk (zx) Thu, 03 Jan 2008 19:36:00 +0000 http://aniszczyk.org/2007/12/30/plug-in-development-workflow/#comment-2667 It all depends on your workflow :)I'm a fan of test-driven development but to a certain extent. I'm almost a realist and writing all your tests before you write any "business code" is just crazy. I say do a mix of both with eclmma mixed in and you'll have your code coverage on the fly and fill in the blanks when the time comes. It all depends on your workflow :) I’m a fan of test-driven development but to a certain extent. I’m almost a realist and writing all your tests before you write any “business code” is just crazy. I say do a mix of both with eclmma mixed in and you’ll have your code coverage on the fly and fill in the blanks when the time comes.

]]> By: asimismo http://aniszczyk.org/2007/12/30/plug-in-development-workflow/comment-page-1/#comment-574 asimismo Thu, 03 Jan 2008 18:12:00 +0000 http://aniszczyk.org/2007/12/30/plug-in-development-workflow/#comment-574 Chris, it seems there's a mistake in your diagram. The test step is supposed to come before you write the Java code. Or, more clearly, writing the test comes before writing the Java code.<br/><br/>;-) Chris, it seems there’s a mistake in your diagram. The test step is supposed to come before you write the Java code. Or, more clearly, writing the test comes before writing the Java code.

;-)

]]> By: asimismo http://aniszczyk.org/2007/12/30/plug-in-development-workflow/comment-page-1/#comment-2666 asimismo Thu, 03 Jan 2008 18:12:00 +0000 http://aniszczyk.org/2007/12/30/plug-in-development-workflow/#comment-2666 Chris, it seems there's a mistake in your diagram. The test step is supposed to come before you write the Java code. Or, more clearly, writing the test comes before writing the Java code.;-) Chris, it seems there’s a mistake in your diagram. The test step is supposed to come before you write the Java code. Or, more clearly, writing the test comes before writing the Java code.;-)

]]>