User Tools

Site Tools


Test EASAP functionality | Test EASAP robustness | Troubleshooting an EASAP

Test EASAP functionality

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.

Test batch files manually

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.

Need for test runs

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.

PROPERTIES

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.

  1. My EASAPs under Applications menu check EASAP Title, Author name and status
  2. EASAP Builder under Authoring menu check the selection image
  3. EASAP Builder application check the window size
  4. File/Open in EASAP Builder application check the categories in which the EASAP is located

USER INTERFACE

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.

  • cycling though inputs.
    • select each setting for a CHOICE LIST or LOGICBOX and confirm the interface responds
    • check that all Lower Bound or Upper Bound settings are functioning properly.
    • proofread labels for typographical errors
  • correct any errors found during testing in the Builder

PROCESSES

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.

OUTPUT

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.


Test runs for an EASAP

Authoring is an iterative process, modify the EASAP in the Builder then Test the change and repeat (below).

  • Log in to EASA and set mode to Author.
  • Select My EASAPs under the Applications menu, and then click on the title link for the EASAP to be tested.
  • Next, select Testing under the Authoring menu.
  • On the Testing page, click on the Test EASAP link to initiate the EASAP for testing.
  • After the EASAP window appears, click on the submit EASAP button () without changing any inputs. Click on OK once the pop-up window appears stating that your test run has been submitted successfully.
    Remember: For first run testing, you want to use default inputs that you already know will work properly with the underlying software applications.
  • Minimize the test EASAP and return your focus to the EASA Testing page. Click on the ‘Refresh’ button on your browser to update the Test Results table on the page. You should see an entry for the test run you just submitted.
  • Now monitor the run by either 1) waiting for a “Completed’ status in the Status column of the table, or 2) clicking on the View Results button in the Output column to view the progress of the results displayed in your output report.

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.


Test EASAP functionality | Test EASAP robustness | Troubleshooting an EASAP