Jean-Baptiste Quenot wrote:
Mmm actually I don't really agree, making the build fail should
not be intentional. We could have some convention like for
example naming the failing unit test methods after bugTestXXX()
instead of testXXX() to make it obvious that the test does not run
and that there is a bug.
Sorry for this, this is probably my fault. ;-)
Having failing unit tests for days on end is definitely bad - it
massively reduces the utility of your continuous integration server.
I originally intended this to be fixed pretty rapidly, hence the
immediate tender for ideas on how to fix it on IRC and the dev mailing
list. Once it wasn't, I should have commented the test out and made
appropriate notes on the JIRA issue.
We have a bug tracker to work out what bugs need fixing before we do a
release, so commenting things doesn't shove them into "a big black hole
where no one is looking at it". It's a bug we currently have scheduled
for fixing before we push 1.3.0-rc1 out. That most definitely makes it
on the immediate radar.
Regards,
Al
--
Alastair Maw
Wicket-biased blog at http://herebebeasties.com
