Jorg Heymans wrote: > We aren't providing snapshot builds and people want to try out the new > features. This currently means they have to compile themselves. Failing > unit tests are a hurdle that might stop their attempt to explore > completely - the huge 'BUILD FAILED' banner at the end doesn't always > convey the right message. > > > So, suggestions: > > We should start providing snapshots again and push the archetype as main > entry point for those wanting to explore.
Why can't we just get the test suite to run through? - If the test is no longer applicable, remove the test. - If the test fails because the test is wrong, fix the test. - If the test fails because the testee is broken, fix the testee. - If fixing the testee is too much effort, disable the block. - If the block is too important to be disabled, spend the effort to fix it. - When all tests pass, then it may be time to invite beta testers. - Write more tests. Am I too naïve? IMHO our current image problem is that there are too frequent BUILD FAILED even without running the tests. Cheers, Alfred. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.
