First, the proper start-to-finish functioning of the EASAP should be tested using a set of default inputs that are known to run the underlying software properly.
The set of default inputs should be used in a manual test of your batch files before using them in a test of your EASAP. Ideally, this manual test should be performed before even generating the EASAP.
Not all components of an EASAP require test runs to ensure proper functioning. When we examine the four main branches of the EASAP Tree, we see that the functioning of the objects on the first two, PROPERTIES and USER INTERFACE, can be inspected visually without submitting a run. The real need for test runs is driven by the remaining two branches, PROCESSES and OUTPUT. The following sections describe how you can inspect, test and refine the different branches of your EASAP.
Settings in the two objects found on the Properties branch, Application and Category, can be checked at various locations on EASA web pages without making test runs. The list below provides locations where proper functioning of the PROPERTIES branch settings can be checked.
GUI objects on the Tree under USER INTERFACE may be inspected visually by clicking EASA→Authoring→Testing→Test EASAP.
The EASAP opens showing the user interface a User will see.
The only way to know that this branch is operating properly is to perform test runs until the underlying software applications are being run properly by your EASAP. You will create test runs as described below and perform troubleshooting as needed as described in Troubleshooting an EASAP until a successful test run without any problems has been performed.
To finalize the design of the Output branch at least one test run needs to be completed in which all processes are working properly and all the required output files are generated. Once this test run has been completed, you can make changes to the Output branch by adding, modifying and deleting objects in EASAP Builder, save the EASAP and then inspect the effects of your changes using the “Regenerate Report…” link via the View Results buttons in the Output column of Test Results table.
Note: After the first test run is completed, you do not need to perform more runs to see changes that you make to the Output branch.
Authoring is an iterative process, modify the EASAP in the Builder then Test the change and repeat (below).
If the EASAP test runs as expected and provides expected results, then you have successfully tested and demonstrated an end-to-end run of your EASAP. At this time, you can move to testing your EASAP for robustness Test EASAP robustness or continue to develop your EASAP if this test was just an interim test during its construction. However, if the EASAP test does not run as expected, then you will need to start troubleshooting your EASAP using techniques presented in the following section.