Topic on Talk:Requests for comment/Unit testing

I am not sure whether we should drop Selenium completely. Selenium tests do test the application as a whole. While I agree that a lot of things that are currently tested with Selenium can be substituted with QUnit or similar, I still think that selenium tests should be used to check more complex interaction patterns, e.g. to test a file uploader or GUI elements that interact via AJAX with the server.

Also, keep in mind that selenium tests are quite easy to record. While experienced developers like us probably tend to write the tests instead of recording, I think that we can actually reduce the barrier for others.

Both QUnit and TestSwarm are written with asynchronous and ajax support in mind. Our current test suite is in a static html-file, we're currently finishing up a to instead run these tests on Special:QUnitTest or something like that. But that's something on our end, not in QUnit.

File uploads are more complicated though, yes. But that is integration testing (or smoke testing), not unit testing. For unit testingæ' we want to and already have dropped Selenium. For integration testing, unless we find a better alternative, we should probably stick to Selenium.

Anyway, one thing at a time. Right now we're trying to clean up and get an infrastructure going on for Unit testing. Feel free to start an RFC for integration/smoke testing. There have been some alternatives, but it's an interesting topic to take next.