Once an Author has an EASAP working, it is time to test it and analyze its functioning.
Examine the EASAP's correctness by varying inputs and submitting multiple runs.
Following each test run the above data is stored as a row on the EASA→Author→Authoring→Testing page.
The watch tab shows the values of any objects in the EASAP as it runs.
Any SCALAR, LIST, EXPLICIT or CONSTANT object can be added to the 'Watch' list.
On the left side of the watch tab, type the prefix of an object name and click <TAB> or <ENTER> to see matching names. Click the plus icon to add an object to the watch list. Click refresh button after changing a value in the EASAP to see objects and their dependents update.
Click on an object's dependents to follow an error as it propagates.
Forward and backward links allow the Author the ability to traverse the dependency tree for a particular object.
ACTION's often involve I/O such as DATABASE ACTION, EXPORT TO PDF, the various EXCEL ACTION's, and EMAIL ACTION.
These I/O ACTIONS as well as implicit updates to most DATA PROCESSING objects are blocking in that the EASAP waits, doing nothing until the I/O process has completed or until all the implicit objects have been updated.
Profile gives the Author a powerful insight into the operational behavior of an EASAP. A detailed performance profile is an important window into why an EASAP is running slow.
Profile includes ACTION's that don't involve I/O but might have lengthy local-computation, or stalled-processing due to user interface ACTION's that may need reexamination.
Additionally, profile includes objects which are implicitly updated, without an explicit ACTION.
For an EASAP with a large number of implicit DATA PROCESSING objects, performance issues may require moving away from these object to explicit LIST DOR VALUE and SCALAR DOR VALUE's and updating their values through SET VALUE and VALUE CHANGED ACTION's.
Below is an example of running a profile on the Stock Screener tutorial example.
From the profile tab below, we see that a DATABASE ACTION runs each each time a User pushes Search Stock Data, in this case it has been pushed twelve times for a total of 277ms.