ok let me jump in the thread. It is not really tests that are not critical it is rather that we have a function that is being implemented 2 ways (for example one implemented on CPU the other in GPU) - the whole software can work if one only is available ... so we would like to consider the build to be successful if both are there but still successful with some restriction only if one out of the two is present.
On Fri, Apr 8, 2011 at 12:13 PM, Luke Daley <[email protected]> wrote: > I'd consider moving this optional tests out into another module. Having your > build pass when tests ran but failed is a recipe for disaster. > > If you move the tests to another module you can run the core build regularly > and the extra tests when you care. > > On 08/04/2011, at 3:29 PM, Lokendra Singh wrote: > >> Hi all, >> >> My project has a set of JUnit tests. Some tests are not very critical and I >> want to report a 'Build Successful' even when those tests fail, but want to >> retport the 'Build Failed' for the critical ones. >> Any pointers? >> >> Regards >> Lokendra > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- PGP KeyID: 2048R/EA31CFC9 subkeys.pgp.net --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
