> If the test runner tests were incorporated in a "make source" build > (perhaps with "make source-test") then we could invoke them from a > source version using injected code from Selenium; alternatively if > they were included in a "make build-test" version as well then we > could test the build compilation (probably quite important given the > compression that is done).
Now that I've got the TestRunner app working here (after the compilation problems) I've come across an issue with it - it runs the tests totally independently of the application. The code I wanted to test had some static functions. I had added some debug logging to these by getting our global application object and calling debug on that. However, this failed in the TestRunner app. I know that unit tests should be carried out independently of other functions, and this might be the only instance of wanting to run the tests in the application environment; however I can also foresee wanting to probe with direct calls when the UI has been used to set up some state in the application. This would be white-box testing rather than unit tests. Adding the layer to the testRunner interface would allow this. Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
