AppStructure, region Test Page

Source image Reference image
Test results
Initiate Test Purpose Test Result Comments
Done on load Get initial 'region' values NA "Passed" if getAppStructureAttr values are correct. See Note 1.
Set initially-unspecified 'region' (big plane). NA "No errors" if no error executing setAppStructureAttr. See Note 2.
Reset already-specified 'region' (fleet). NA "No errors" if no error executing setAppStructureAttr. See Note 3.
Retrieve current 'region' values. NA "Passed" if getAppStructureAttr values are correct. See Note 4.
Remove 'viewcontext' attributes: NA See Note 5 to interpret result.

Note 1. At test start, a 'region' APS Attribute on the fleet of six small planes has extent as indicated by the larger dashed rectangle. There is no 'region' on big_plane initially. The first (onload) test is passed if the getApsStructureAttr values are correct for fleet and big_plane objects. To visually verify viewer behavior, look at screentips. The screentip "Fleet" should be seen with the cursor anywhere in the fleet region (larger dashed rectangle), other than directly on a small plane. No screentip should be seen with the cursor around the big_plane, other than over the big_plane.

Caveat! Visual viewer result does not imply the same DOM-specific test result. For example, the DOM can be correct, but visual viewer behavior incorrect.

Note 2. "No errors" only means that there were no exceptions upon test execution. Test 4 can numerically verify that correct values were set, assuming that test 1 (getAppStructureAttr) passed. For visual viewer verification that the initial value (no 'region') was replaced on big_plane, look at its screentip. "Big Plane" should be seen with the cursor anywhere in the phantom (dash-dot-dot) rectangle.

Note 3. "No errors" only means that there were no exceptions upon test execution. Test 4 can numerically verify that correct values were set, assuming that test 1 (getAppStructureAttr) passed. For visual viewer verification that the initial value (larger dashed rectangle) is replaced on fleet, look at screentip. The new region is enlarged vertically to the VDC Extent, so you should see the "Fleet" screentip with cursor above and below the larger dashed rectangle.

Note 4. "Passed" means that getAppStructureAttr returned the same 'region' values on fleet and big_plane as were set in tests 2 and 3.

Note 5. Interpretation of Test Result: