Test results from local test runs are stored in the result archive store (RAS) on the machine where the tests were run. The RAS directory contains all elements of a test, including the test results, run logs, and test artifacts. Inside the RAS directory you can find the run.log which stores event records from a test run on your local machine. You can also view the images folder in the zos3270 directory to see the terminal interactions from a test run.

Viewing results in the run log

You can view the results of your test runs in the run.log file by completing the following steps:

1. Navigate to your .galasa directory
2. Open the run.log file by selecting ras > results > run.log
3. Expand the run.log file to view a record of the events from the test run.

Viewing 3270 terminal interactions

To view 3270 terminal screens and recorded web requests and responses that are generated from running tests you need to first update the 3270.terminal.output property in the cps.properties file on your local machine. To do this, complete the following steps:

1. Navigate to your .galasa directory
2. Open the cps.properties file, for example in VS Code.
3. Edit the zos3270.terminal.output property to include .png files as well as json by adding the value png to the property. For example, zos3270.terminal.output=json,png.

3270 terminal screens, and recorded web requests and responses for test runs are now stored as .png files in the ras > results > artifacts > zos3270 > images folder.

You can then view the terminal interactions from your test runs in the images folder in the zos3270 directory by completing the following steps:

1. Navigate to your .galasa directory
2. Open the images folder by selecting ras > results > artifacts > zos3270 > images
3. Expand the images folder to view test artifacts stored from the run, for example, terminal screens, and recorded web requests and responses.

Next steps

Take a look at the Exploring Galasa SimBank online or Exploring Galasa SimBank offlinedocumentation. Galasa SimBank is a component that is distributed with Galasa. SimBank simulates a mainframe application and is designed to help you to learn Galasa's basic principles of operation before you start connecting Galasa to your own mainframe application-under-test.