We have no written strategy, I'm afraid. JUnit tests can be safely dropped into testsrc and they'll be picked up by Ant, so I believe Norris should add them along with the patches if Marc was courteous enough to provide them.
If I could finally spend time to figure out why we have a bunch of JUnit tests failing in our Bamboo (or alternatively, have our JsDriver output JUnit-compatible XML results) we could finally get to a clean build which would be a great starting point for any future development... Especially since I integrated EMMA coverage metrics into the build process as well, and there''s an EMMA plugin for Bamboo that'd allow us to see if we're developing code without covering it with tests. This is all however few steps away still. But as an interim measure, JUnit tests can already be added to testsrc. Attila. On 2008.01.23., at 16:11, Marc Guillemot wrote: > Norris, > > thanks for starting to fix the issues that really matter for HtmlUnit, > this will allow us to make big steps forwards! > > I'm quite surprised that you discard the unit tests that I provided > and > add new features without appropriate tests. For me each change should > have a test to avoid future regression. > > What is Rhino's strategy concerning (unit) tests? > > Cheers, > Marc. > -- > Blog: http://mguillem.wordpress.com _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
