[Laszlo-dev] proposed unit test architecture
jgrandy at laszlosystems.com
Fri Mar 31 11:07:28 EST 2006
Yes! Here's a candidate list of low-level unit tests that could be
relatively easily converted. The first is specifically for our Class/
UserClass regime; it could be extended but covers the basics.
On Mar 31, 2006, at 2:58 AM, P T Withington wrote:
> 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
>> 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
>> 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.
>> Laszlo-dev mailing list
>> Laszlo-dev at openlaszlo.org
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
More information about the Laszlo-dev