Michelle,
Sorry, swap that again. I made another change to the test framework.
This is really a piece of crap. The way it's structured with all these
<ant/> calls, you can't get any return codes or properties, so when the
ui-test is run, you can never get any information back from it. I can
tell this was thrown together to run the Eclipse IDE tests, but then
they offered it publicly to be helpful.
If a test class fails, I have it collecting the results first and then
failing. Since we only have one class, everything runs through AllTests
and we get a final report.
--
Patrick
On Sat, 2008-08-02 at 09:11 -0400, Michelle S Osborne wrote:
> Nice work! I swapped yours in and also updated our test eclipse to the 64-bit version. I know how to get nicely formatted html reports from junit results now too, so I'll add that to the build.
>
> Michelle
>
> ----- Original Message -----
> From: Patrick Winters <pat...@ny...>
> Date: Saturday, August 2, 2008 2:43 am
> Subject: Failing with tests
> To: git...@li..., 'Michelle S Osborne' <ms...@ny...>
>
> > Michelle,
> > I inspected the test-framework plugin and found the ant library to
> > explicitly NOT fail on error. I modified this, re-zipped it. If you
> > swap
> > out the current zip for this one we should get a property set if a test
> > fails. This way all the tests will get run, we should get a full report,
> > and I set it fail at the very end.
> >
> > http://cs.nyu.edu/~pcw216/work/gitclipse/eclipse-test-framework-3.3.2.zip
> > --
> > Patrick
> >
> >
> >
> >
|
