Et1 Test Harness: Component Architecture
This is the Deployment Version (runs from built code). Go to the Developer Version (runs from source code).

Architecture Document

JavaScriptdoc

Supported Platforms:
Verification Targets:
  1. Functionality Test
    1. Verify that no JavaScript errors occur in any of the steps on this page, and that the behavior is as stated/expected.
    2. Click on the button "Create 'Rest the Body' Component'. The "Rest the Body Component" should appear. Click the 'Destroy This Component' button. The "Rest the Body Component" should disappear.
    3. Repeat the step above five times.
    4. Click on the button "Create 'Work the Day' Component'. The "Work the Day Component" should appear. Click 'Destroy This Component'. The "Work the Day Component" should disappear.
    5. Repeat the step above five times.
    6. Click on the button "Create 'Rest the Body' Component'. Click the 'Create Next Component' button. The "Work the Day Component" should appear.
    7. In "Rest the Body Component", click the "Destroy This Component" button. The "Rest the Body" Component should disappear.
    8. In "Work the Day Component", click the "Destroy This Component" button. The "Work the Day" Component should disappear.
    9. Click on the button "Create 'Work the Day' Component'. The "Work the Day Component" should appear.
    10. In the "Work the Day Component", click on "Create Sub-Components". The "Meeting Component" should appear inside the "Work the Day Component". Inside the "Meeting Component", the "Presentation Component" should appear. The "Applause Component" should appear inside the "Presentation Component" and the "Coffee Component" should appear alongside the "Presentation Component" (underneath it, but not inside it). A JavaScript 'alert' dialog should appear with some user-text on it. Click 'ok'.
    11. In the "Work the Day Component", click 'Destroy This Component'. The "Work the Day Component" should disappear.
  2. Memory Leak and Repetition Test
    1. Open Firefox (v3 or current), Internet Explorer (v.6 if still somewhat current), Safari (v3.1.2 or current).
    2. Ensure that each browser has only the test harness open: No other pages.
    3. Wait about 45 seconds. Next record the memory usage for each browser. On Windows, use the Task Manager for this. On Mac use the Activity Monitor, which can be found in 'Finder' -> 'Applications' -> 'Utililities'.
    4. Perform the Functionality Test, above, on each browser.
    5. For Safari, come back to this task in about 30 minutes. The rest can be done after a wait of about five minutes. Record the memory usage for each browser. In some tests, browsers such as Firefox 3.0.5 will show no increase over 500K in two repeated memory test runs, whereas in others a 3 to 6mb increase will be registered. None of the browsers except for IE 6 and IE 7 should show significant, consistent ( > 6m ) increased memory allocation.