Comments on: Continuous Testing with OS X and Rails http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/ Late at night, I value silence most of all. Mon, 13 Oct 2008 20:45:40 +0000 http://wordpress.org/?v=2.4-bleeding By: Drop http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-276 Drop Thu, 02 Feb 2006 15:11:28 +0000 http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-276 Just checking to see if any relation are out here http://swarovski.searchcar.org/daniel_swarovski/ Just checking to see if any relation are out here
http://swarovski.searchcar.org/daniel_swarovski/

]]> By: Jake http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-58 Jake Fri, 22 Jul 2005 19:51:05 +0000 http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-58 Matt - Yeah, I like to have that instant feedback on my progress. When I'm doing TDD, it helps me to know when I've successfully completed the 'goal', ie gotten all the tests passing, <em>before</em> I commit the changes to subversion. Personally I like to commit only code that fully passes the tests. That way I can svn checkout the code from anywhere and I know it will run and I can work on it. Matt - Yeah, I like to have that instant feedback on my progress. When I’m doing TDD, it helps me to know when I’ve successfully completed the ‘goal’, ie gotten all the tests passing, before I commit the changes to subversion. Personally I like to commit only code that fully passes the tests.

That way I can svn checkout the code from anywhere and I know it will run and I can work on it.

]]> By: Matt Moriarity http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-57 Matt Moriarity Mon, 18 Jul 2005 22:17:59 +0000 http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-57 This approach appears to be much more practical than something such as CIA. Most of the time, the test database is not available on the production server. This works on the local machine. Very nice, I've downloaded it and started using it. Now I can see exactly when I make changes which affect the tests. This approach appears to be much more practical than something such as CIA. Most of the time, the test database is not available on the production server. This works on the local machine. Very nice, I’ve downloaded it and started using it.

Now I can see exactly when I make changes which affect the tests.

]]> By: Jake http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-26 Jake Sun, 15 May 2005 22:13:51 +0000 http://blog.unquiet.net/archives/2005/05/14/continuous-testing-with-os-x-and-rails/#comment-26 Here's a version compiled on Tiger (10.4) using the updated Growl framework in 0.6.1: <a href="http://blog.unquiet.net/media/stakeout.tgz" rel="nofollow">stakeout & gstakeout</a> Here’s a version compiled on Tiger (10.4) using the updated Growl framework in 0.6.1: stakeout & gstakeout

]]>