We have two test frameworks currently. We have a specs runner implementation and a custom interactive test framework. The specs runner is based on JSSpec which you can find online; we have a custom implementation of this that you can find in our test repository.
http://code.google.com/p/jsspec/ http://github.com/mootools/mootools-core-specs In addition to this we have a test framework that asks the user to perform tasks and verify the result - this is useful for asking questions a computer can't easily answer or for running tests against functionality that may have asynchronous actions (like ajax requests). For example, "does the effect transition smoothly" and "can you drag the handle and resize the box" are not the kinds of questions you can answer with JSSpec (which answers questions that have measurable, immediate output like, "is 2+2 = 4?"). This can be found here: http://github.com/anutron/mootools-unittester demo: http://www.clientcide.com/TestFramework/ In addition to these two frameworks, I also use windmill at work: http://www.getwindmill.com/ We have this connected to our integrated test server (which is running Hudson) so that every time someone pushes new changes to our master branch Hudson fires up a browser and it clicks around to ensure our application still works. Windmill allows you to simulate dragging, clicking, typing, whatever. We even capture the video output of the screen so that we can watch a playback if there's a failure. On Mon, Feb 1, 2010 at 8:39 AM, Eneko Alonso <[email protected]> wrote: > How does the Mootools team do unit testing? > Via browser? Command line with V8 or Rhino? > > Any suggestions? >
