This looks great. Hopefully one of the first things we test is the class implementation.
On 2006-03-30 19:28 EST, Benjamin Shine wrote: > As promised, here is a sketch of my plan for an automated unit test > infrastructure. I plan to have something to check in tonight or > tomorrow. Currently I have scripted tests in lzx succeeding and > failing. > > THE DRIVING PROBLEM: How do we know that the LFC is correct in the > DHTML runtime, as we develop the DHTML LFC? > > NEARBY GOALS > * Automate tests to detect errors in runtime <x>. > * Make tests run fast. > * Create useful logs of test results. > > PROPOSED SOLUTION: > (See the attached diagram.) > The proposed solution uses ant, rhino and dojo to execute the tests > in the same java vm, headless. > It tests the LFC dhtml with the dojo unit test framework by using > the BUFakeDOM. > The BUFakeDOM is part of the dojo source distribution. > This solution will also support using ant and rhino to invoke the > existing lzunit tests in the browser, a la, "ant testsafari", "ant > testfirefox" > > LEGACY TESTS: > LzUnit tests which assume that there are things like windows and > events will not work in rhino/fake dom without a lot of work. > LzUnit tests that deal with the lfc, nodes, classes, etc, should > work in rhino/fake dom. > > STATUS: I've put all the pieces together a few at a time, and now > I'm working on automating putting them together with ant. > > UNKNOWN PARTS: I haven't yet figured out how to get the dojo unit > test framework to generate a logged report. > > > <unit_test_plan.png> > _______________________________________________ > Laszlo-dev mailing list > [email protected] > http://www.openlaszlo.org/mailman/listinfo/laszlo-dev _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
