Estimated completion time→10 minutes.

In this practical session, we will test the EASAP from the previous sessions. Then we will Publish the EASAP for other users on EASA→User→Applications.

• Start EASA and log in.
• Set Mode→Author
• Select EASA→Applications→My EASAPs
  • Click on our EASAP
• Under EASA→Authoring→Testing
  • Click on the Test EASAP link on the page that appears.

After the EASAP window appears:

• Click on the Submit EASAP button () in the upper right corner.

A pop-up window will appear when the EASAP has been submitted successfully.

• Click OK

• Now close the EASAP window, and focus back on the EASA→Authoring→Testing which will look something like the following:

• Locate the application that we just submitted in the testing table
• Click the browser’s refresh button to see the run.
  • (The Date and Application columns should provide enough information to find it.)

• Examine the Status
• Once ‘Completed’, view the results by clicking on the

icon under Output ().

Now let’s look at the files that will help to diagnose problems we may encounter getting an EASAP to run properly.

• Click on the Browse Files icon () for the latest run under the Files column

A pop-up window will appear that will look like the following figure:

• In this window, look for the err1-runplate.txt file in the list.

This file should have a Size of 0.0 kb to the right of the file name. If the number is greater than zero, then click on the link for the file and examine the error messages given in the file. Contact the instructor or EASA support representative if the cause of these messages cannot be identified. At this point, we may need to go back to EASAP Builder and make changes to the EASAP based on suggestions from the EASA support person. Then resubmit the EASAP for another test. Iterate in this way until all errors in the err1-runplate.txt file are eliminated.

Note: Depending on the type of underlying software driven, not all messages captured in the diagnostic files, such as err1-runplate.txt, will need to be eliminated. Often, software applications send other types of messages to the standard error stream.

• Finally, look to see that a PLATE.OUT file has been created.

If not, then there is a problem with either the EASAP or the input file, plate.txt.

• Open this file and check if all object references were replaced correctly.

The file should look like the following:

If the input file does not look like the one above and the cause of the problem cannot be identified, contact the instructor or EASA support representative. Again we may need to go back to the Builder and make changes to the EASAP or make modifications to the template file plate.txt in the template editor. Then resubmit the EASAP for another test. Iterate in this way until the object references in the plate.txt file get replaced properly and a valid PLATE.OUT file is produced.

At this point, we have successfully completed an EASAP run.

• Close the file browsing window

Examine the reported results:

• Click on the View Results button () in the Output column.

The report will look similar to what was shown in Practical Session 1 and when we developed the Output branch in Practical Session 5.

If the report does not appear correctly, please contact the instructor or EASA support representative for assistance. Again, we may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. We will NOT have to resubmit the EASAP for another test: just save your changes in the Builder and then click on the Re-generate report using the latest version of this EASAP link to see an updated report. Iterate in this way until the report appears as expected.

The EASAP will now be ready for publishing.

• Select EASA→Authoring→Publish
• Add a relevant comment in the input area
• Click on the Publish button

Following the initial Publish, an Author may choose from Major Revision, Minor Revision and Unpublish options.

A new window will state ‘The EASAP has been successfully published.’

Let's check whether our EASAP will be visible to Users on the EASA system.

• Set EASA→Set Mode→User in the browser.

• Now click on the EASA→Applications tab
  • Select ‘Training’ as the Category

The EASAP will now be visible in the EASA→Applications table.

• Open up the EASAP, modify some inputs and then submit it to run as a User.

Confirm the output from the EASAP run is available at:

• EASA→Results→My Results

• Finally, Log Out of EASA.