http://www.pathf.com/blogs/2009/06/cucumber-rocks-but-its-not-a-replacement-for-unit-tests/ Running commentary about agile development, user experience design and Ajax. Fri, 05 Mar 2010 19:33:43 -0600 http://wordpress.org/?v=2.8.4 hourly 1 http://www.pathf.com/blogs/2009/06/cucumber-rocks-but-its-not-a-replacement-for-unit-tests/comment-page-1/#comment-6706 Ennuyer.net » Blog Archive » 2009-06-15- Today’s Ruby/Rails Reading Mon, 15 Jun 2009 19:47:52 +0000 http://www.pathf.com/blogs/?p=2665#comment-6706 [...] Agile Ajax » Cucumber Rocks - But it’s not a replacement for unit tests » Pathfinder Developmen... [...] [...] Agile Ajax » Cucumber Rocks – But it’s not a replacement for unit tests » Pathfinder Developmen… [...]

]]> http://www.pathf.com/blogs/2009/06/cucumber-rocks-but-its-not-a-replacement-for-unit-tests/comment-page-1/#comment-6648 Piotr Sarnacki Thu, 11 Jun 2009 11:01:46 +0000 http://www.pathf.com/blogs/?p=2665#comment-6648 Jason: Do you functional test all of the controllers? I often leave code without functional testing while using cucumber if controller isn't doing anything special (standard CRUD for example). When there's something that I can't move to model nor I can't easily check with cucumber without complicating things I create functional test for this particular action. What do you think about this approach? Jason: Do you functional test all of the controllers? I often leave code without functional testing while using cucumber if controller isn’t doing anything special (standard CRUD for example). When there’s something that I can’t move to model nor I can’t easily check with cucumber without complicating things I create functional test for this particular action. What do you think about this approach?

]]> http://www.pathf.com/blogs/2009/06/cucumber-rocks-but-its-not-a-replacement-for-unit-tests/comment-page-1/#comment-6646 Jamie Wed, 10 Jun 2009 21:26:13 +0000 http://www.pathf.com/blogs/?p=2665#comment-6646 This exactly how we work at SonicIQ. I've actually found that we generally skip functional tests using this technique as the Cucumber specs catch what we would usually write functional tests for. As you say, unit tests are still a must. This exactly how we work at SonicIQ. I’ve actually found that we generally skip functional tests using this technique as the Cucumber specs catch what we would usually write functional tests for. As you say, unit tests are still a must.

]]>