<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I used to do the same... and BOOM (in a CI fail sense) is what usually happens.<div><br></div><div>Sometimes I do:</div><div> while work_still_to_do?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- code</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- commit</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- run the tests I think will have changed locally</div><div> run: git fetch && git checkout master && (git merge my_feature && rake && git push && cap qa deploy && nabaztag-say 'card_owner... ... Please check my_feature in qa') || (git reset --hard origin/master && git checkout my_feature && nabaztag-say 'Get back to work Tom... ... you are not as good as you think you are'</div><div><br></div><div>then take a 15min break.</div><div><br></div><div>The real difference here is that I get to take more breaks.</div><div><br></div><div><div><div>On 20 Jul 2009, at 15:21, Matthew Rudy Jacobs wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">My approach is;<br><br>- run the tests I think will have changed locally<br>- run all the tests every time on CI<br><br>B00M!<br><br><div class="gmail_quote">2009/7/20 Matt Wynne <span dir="ltr"><<a href="mailto:matt@mattwynne.net">matt@mattwynne.net</a>></span><br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br> On 17 Jul 2009, at 12:03, Paul Battley wrote:<br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> 2009/7/17 Matt Wynne <<a href="mailto:matt@mattwynne.net" target="_blank">matt@mattwynne.net</a>>:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'd quite like to spread the word about my lazy Cucumber runner:<br> <a href="http://github.com/mattwynne/cucover/tree/master" target="_blank">http://github.com/mattwynne/cucover/tree/master</a><br> </blockquote> <br> That's a great idea. I just tried it out. Unfortunately, it seems to<br> make everything run so slowly that I'd be better off just running all<br> the features ...<br> <br> Paul.<br> </blockquote> <br></div> Yes... unfortunately it's more of a proof of concept right now - I don't use it myself day-to-day as too much of our stuff runs out of process for me to be able to use it reliably. But I had noticed about the speed - I'm not sure how much that's unavoidable RCov overhead and how much is my naive first-pass implementation which is chattering away to disk all the time.<br> <br> If you have a significant number of features though, focussed regression runs are a big time-saver, especially when you're refactoring and lose track of what you might have broken. That's the theory anyway... :)<div class="im"> <br> <br> cheers,<br> Matt Wynne<br> <br> <a href="http://mattwynne.net" target="_blank">http://mattwynne.net</a><br> +447974 430184<br> <br> _______________________________________________<br></div><div><div></div><div class="h5"> Chat mailing list<br> <a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br> <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br> </div></div></blockquote></div><br> _______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></blockquote></div><br></div></body></html>