Talk:AMO:Developers/JavaScriptTesting

Is optimizing the JavaScriptTesting framework for testing Ajax Widgets too complicated?

I'd argue we should optimize the framework for a much simpler set of tests, like unit tests and integration tests that use the DOM. Testing widgets that use Ajax to talk to a server is a much nastier test case, This more advanced case can be solved with Mocks or Selenium driven browsers... etc. These Ajax widget tests will run more slowly than pure unit tests. We may want to treat them as a different class of automated test. Our baseline use of QUnit or another unit testing framework should make it easy to test basic JS code. Aking 14:32, 15 November 2010 (PST)