On 03/15/2011 02:35 PM, Asokan Pichai wrote: > On 15 March 2011 13:51, Vamsee Kanakala<[email protected]> wrote: > >> On Tuesday 15 March 2011 10:44 AM, Kenneth Gonsalves wrote: >> > > [SNIPPED] > > A curiosity question: like make, is there a facility to run only those tests > that correspond to > changed code. Even as I type this the question seems ill-defined etc., but > still .... >
Umm, that kinda defeats the purpose of TDD. When you run the test suite basically, the intention is to know that you haven't inadvertently broken something that you thought was unrelated by your latest changes. That said though, I know that at least when using nosetest you can be selective about the tests you run using different patterns such as the modulename, filename, testnames, generic regex, only the ones that failed in the last run ...etc. So typical workflow is generally run a subset of the tests during development and run the entire suite before committing changes -- or at least this is what we follow at my workplace. cheers, - steve -- random spiel: http://lonetwin.net/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
