My plan was to actually run those unit tests (via windmill) in actual browsers. If we have Hudson + Windmill (or some other equivalent) then we can test our code in IE, Safari, etc. Running the tests from the CLI is fine, too, but if we want to test our work we need to do so in the environments we support.
On Wed, Nov 3, 2010 at 5:38 AM, Olivier El Mekki <[email protected]> wrote: > @Aaron > > For what I see, the simplest way to fully integrate mootools-runner in > hudson would be to add a junit output format to the runner. It would let > us use the xunit plugin, and it may helps for other CI tools. > > The other solution is to write an hudson plugin for mootools-runner, but > I don't know java personnaly and writing a hudson plugin seems not to be > a trivial task. > > > On 11:43 Thu 28 Oct , Aaron Newton wrote: > > It's on my todo list to do this for mootools itself. I'd be interested in > > collaborating a bit. I've been contributing to windmill a bit with plans > on > > hudston + windmill + our various test environments (there are a few). > > > > On Thu, Oct 28, 2010 at 11:04 AM, Olivier El Mekki <[email protected] > >wrote: > > > > > Hi, > > > > > > I was asked to write some mootools code for a project built in a > > > continuous integration process. > > > > > > Does anyone know if the new mootools' spec engine, mootools runner, > > > plays well with hudson? > > > > > > -- > > > Olivier El Mekki. > > > > > -- > Olivier El Mekki. >
