Hi,
It looks like these tests got checked in even though they don't run as
yet. Can they be commented out until they are operational? Currently
they are causing the full test run to fail, which is not the end of
the world but is something we should probably avoid.
Ethan
On Tue, Nov 10, 2009 at
@Ethan: Why shouldn't the full test run. This is perfect for the
Hudosn-based environment. I think it would better to have some sort of
a maven flag that allows you to run your tests but not the whole test
suite. No idea how this might work, because I'm not a maven expert.
D.
On Fri, Nov 13,
On Fri, Nov 13, 2009 at 6:50 AM, Ethan Jewett esjew...@gmail.com wrote:
Hi,
It looks like these tests got checked in even though they don't run as
yet. Can they be commented out until they are operational? Currently
they are causing the full test run to fail, which is not the end of
the
With regard to running tests on Hudson, I think failing tests are
perfect, but the tests need to run through without exceptions (they
can fail, but they can't have uncaught exceptions ... I think) or they
will severely reduce the usability of the test suite and of the Hudson
integration. Is
If you look at the console message from the last build
(http://hudson.zones.apache.org/hudson/job/ESME/lastBuild/console),
you do a see an error but a different one than Ethan mentioned. What
is strange is that I have never seen this error during my local
builds.
Even stranger is that Hudson says
Vassil,
That's fair, but something is wrong, because this exception is
resulting in no test results at all (on either my system or on
Hudson). It's as if the test runner doesn't catch the exception and
instead of converting it to a test failure it just gives up on the
whole test suite.
If the
That's fair, but something is wrong, because this exception is
resulting in no test results at all (on either my system or on
Hudson). It's as if the test runner doesn't catch the exception and
instead of converting it to a test failure it just gives up on the
whole test suite.
If the new
Vassil,
Yeah, it's not the same error. My mistake for not checking the actual
Hudson error message. That complicates the whole matter. I'm actually
getting a complete build failure when I do mvn test, which I think
is due only to the test failures. When I do mvn jetty:run, it's
fine.
The other
PS -- What's the ETA for the new templates?
Joy (the designer) has converted all pages and is currently testing in
IE6.
We should have the templates by the end of this week.
/Anne
On 11. nov. 2009, at 01.04, David Pollak wrote:
Folks,
I started writing some ESME tests and got very
On Wed, Nov 11, 2009 at 1:40 AM, Anne Kathrine Petterøe
akpette...@gmail.com wrote:
PS -- What's the ETA for the new templates?
Joy (the designer) has converted all pages and is currently testing in IE6.
We should have the templates by the end of this week.
Woo Hoo!
/Anne
On 11.
Folks,
I started writing some ESME tests and got very cranky with Lift's TestKit
(what kind of fool wrote those APIs anyway... oh, look, here's a mirror and
I'm looking at the fool).
I spent a couple of hours cleaning up the Lift TestKit APIs so that tests
will look like:
Login in {
11 matches
Mail list logo
