Sweet!! I'm off for the weekend... will take a look when I'm back. alex
On Fri, Jan 15, 2010 at 10:59 AM, Antoine Toulme <anto...@lunar-ocean.com>wrote: > See BUILDR-363, and my patch there. > > On Thu, Jan 14, 2010 at 10:42, Antoine Toulme <anto...@lunar-ocean.com > >wrote: > > > OK, I'll use that. Thanks! > > > > > > On Thu, Jan 14, 2010 at 10:38, Alex Boisvert <alex.boisv...@gmail.com > >wrote: > > > >> On Thu, Jan 14, 2010 at 10:22 AM, Daniel Spiewak <djspie...@gmail.com > >> >wrote: > >> > >> > I don't think that JUnit has anything like this. If I were you, I > would > >> > look to rspec for inspiration. When we finish running tests for a > >> project, > >> > grab the list of test names which failed and save it to a file (maybe > >> > target/failed-tests?). Then have your run-failed-tests task (maybe > >> > test:failed?) read that file and only run those tests, rather than > usin > >> the > >> > test provider to determine the set of all tests in that project. Even > >> > better, you could still grab the list of all tests and then intersect > it > >> > with the set of failed tests. That way, you avoid running a > >> > previously-failed test which no longer exists. > >> > > >> > >> Yep, I'd take the same approach too. > >> > >> This way, the re-run task can be generic across test frameworks. > >> > >> alex > >> > > > > >
