Is there some actual problem we are trying to solve
here? Because if there is, no-one has pointed it out yet.
The point of the failing tests is to remind and nag us to
get them fixed. If we hide the failures we remove that
incentive.
There has been a bunch of handwaving about how this could
theoretically be a problem for continuous integration ... except that
we are doing continuous integration and it is not causing
any problems!
It seems there are some people here who have read a
couple of books by Kent Beck and think that their job as a software
developer is to enforce their Holy Perfect Process on everyone. That's perfectly
fine, but we are practical people running an actual serious software project
here, and we don't have time for trying to impress people by how aGiLe we
are.
Thanks for your input, this is the end of
the thread.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erik Bertelsen
Sent: Sunday, June 11, 2006 12:35 PM
To: Max Andersen
Cc: hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] questions regarding development setup
2006/6/11, Max Rydahl Andersen <[EMAIL PROTECTED]>:
Hi all,
what about a version of runTest() that silently accepts test failures for tests that are expected to fail and report them as 'failures' if they suddenly start to succeed.
This will have the intended result that a test run is silent if everything works out as expected and if a test that is expected to fail suddenly succeeds, it will show up in the test report.
If the success of the test was intentional because the problem was solved, the test should of course be changed to a normal non-failure-expected test. If the success was an unintentional consequence of some code change, then the developer can investigate whether the problem was really solved or just disguised and possibly alter the test.
- Erik
as i mentioned at the bug we could actually implement this by doing a
custom impl of HibernateTestCase.runTest()
/max
Hi all,
what about a version of runTest() that silently accepts test failures for tests that are expected to fail and report them as 'failures' if they suddenly start to succeed.
This will have the intended result that a test run is silent if everything works out as expected and if a test that is expected to fail suddenly succeeds, it will show up in the test report.
If the success of the test was intentional because the problem was solved, the test should of course be changed to a normal non-failure-expected test. If the success was an unintentional consequence of some code change, then the developer can investigate whether the problem was really solved or just disguised and possibly alter the test.
- Erik
_______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
