Comments on: Fixing my testing workflow https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/ Matt Wynne taking it one tea at a time Wed, 21 Aug 2019 12:55:30 +0000 hourly 1 https://wordpress.org/?v=6.2 By: Oriol Gual https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1339 Wed, 01 Jun 2011 20:11:02 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1339 We used it everyday (together with Spork) and I haven’t noticed any problems with it, it works well even with minitest/spec. Maybe you should try the newest version and see if it works for you 🙂

]]> By: Matt https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1338 Tue, 31 May 2011 18:02:48 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1338 Hi Oriol,

I’ve found Guard comes the closest to what I want, but both the rspec and cucumber drivers seem to be buggy and don’t always seem to find tests that are failing. Maybe I should give them some love.

]]> By: Oriol Gual https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1337 Tue, 31 May 2011 17:46:03 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1337 I really like to use guard instead of autotest. It provides different tools to watch changes to various events, not only cucumber and specs (plus, if a test fails, it will continue to run that one until is green, and then run the whole suite). Give it a try: https://github.com/guard/guard

]]> By: Elliot Winkler https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1331 Sat, 28 May 2011 05:29:12 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1331 Yeah, I would agree that it seems like we have a lot of testing tools, but none of them are really that smart, you’re still left to do the grunt work. I like your autotest idea — my biggest problem with it has always been that it runs ALL the tests after a failure, which is completely retarded in my opinion — that should be done right before you commit, not as you’re testing. I haven’t seen any sort of attempt to make the Cucumber workflow faster, so an improvement on that would be welcome, I’m sure. Same goes for Jasmine tests, now that I think about it. And no one’s tried to lump them all together under one roof. Go for it!

]]> By: Matt https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1328 Fri, 27 May 2011 22:04:57 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1328 In reply to Matt Snyder.

Hi Matt,

Last time I tried autotest it was really scrappy, but I’ve heard it’s come on a lot recently. Should I give it another shot?

]]> By: Matt https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1327 Fri, 27 May 2011 22:03:51 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1327 Hi Lisa,

No, this is during my day-to-day TDD workflow, before I push any code to CI.

]]> By: Matt Snyder https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1326 Fri, 27 May 2011 18:01:36 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1326 Matt

Have you tried using autotest for your test runner? It should handle the list of failed tests and only running those failed tests until they pass.

  • Matt
]]> By: Lisa Crispin https://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/comment-page-1/#comment-1325 Fri, 27 May 2011 17:28:55 +0000 http://blog.mattwynne.net/2011/05/27/fixing-my-testing-workflow/#comment-1325 Are you running these tests in your CI? We run all our various automated tests (in Canoo WebTest, FitNesse and JUnit) in Hudson, and the tools we use have results that lend themselves for plugging into Hudson. That way we can easily investigate failures, and Hudson keeps all the history for us of each build’s results. And all our tests are in SVN so we can see what changed between updates. But, I don’t use RSpec or Cucumber, maybe they don’t have hudson or other CI plug-in capability?

]]>