Galasa for Visual Studio Code
This extension is directly linked to the Java Extension Pack to be able to compile your Java-workspace and to build Galasa-tests using Maven for Java. This is installed simultaneously with the Galasa extension.
Prerequisites
- Java JDK 8 is mandatory, any later versions will not work
- Maven needs to be installed, any version compatible with JDK 8
What is Galasa?
Galasa is an open source deep integration test framework for teams looking to give more power to their testers. What makes Galasa a deep integration test framework is its ability to support tests that cross system boundaries and reach into remote layers inaccessible to other testing tools.
Galasa has been architected to ensure that the routine tasks of writing and executing tests are straightforward. The more complex parts of tests (such as provisioning) are abstracted into other components that can be written by experts and easily distributed to the team.
Overview of the Galasa extension features
User configuration
- Maven-local: If you have a local Maven repository to pull from you can specify this here to take priority over the remote Maven repository
- Maven-remote: URI for remote Maven Repository
- Overrides: A boolean that enables if you want to use your
overrides.propertis in .galasa
- Requestor: Defining the name of the Requestor when Requesting a Galasa Run
- Version: The currently built Galasa version, you would like to use
Launching a Galasa Test
There are multiple ways to launch a Galasa test in this extension, you are able to use the incode-button or are able to press the button in the upper-right side corner of your screen.
Running a Galasa test requires you to have built the whole of Galasa for the version that you are currently writing a test for.
Click the Debug Galasa Test to start debugging your test. Or you can press the Galasa-icon in the upper-right corner to run the same opened test.
Setting up custom Environment Properties
Environment properties are there for you to define specific properties that are to be used in overrides.properties-file in your .galasa-folder. These properties allow you to define specific meta-data for certain tests. You are able to switch between these environments and add properties with their associated values as you wish. If you have utilised an environment of properties fully you are able to even delete this environment.
- Creating a new environment
- Opening and activating this new environment and adding necessary environment variables for a Galasa test
- These environment variables are the utmost layer of overriding your cps.properties
Looking at your run-history
You are presented a historic-view of all your Galasa runs. You can interact with them in a couple of ways.
- Double clicking on a run will give you an overview of the test-structure
- Showing a list of the generated-artifacts in the artifacts tab. You are then able to open these files and visualise them.
- Showing a run log
- Deleting a run log
Artifact viewer
Visualising artifacts that are generated by running a Galasa test.
In this tab you are able to access your terminal screens and other test artifacts such as log files and general files captured by the utilised Galasa managers.
Generating a testing-environment for running Simbank
Simbank simulates a mainframe application. It has been created to show off the hybrid and scalable capabilities of the Galasa Framework without having to deal with the complexities of connecting to an actual mainframe. It is a perfect start to learn and/or understand how the framework operates.
Simbank has been built inside the extension to showcase some of Galasa's capabilities and help you start writing your own Galasa tests.
You can connect with the Simbank-environment using a 3270-emulator and are able to interact it by running the provisioned Galasa tests.
This functionality is visible on the TEST RUNNER tab
All Galasa-related files can be found in the .galasa folder under your user's root.
Click the rocket-icon under local runs to launch an instance of Simbank running locally on your machine using the Java 8 JDK.
Initialise your Galasa environment. (Setup Galasa Workspace icon under local runs) This should have been done during the first launch of the Galasa extension, but can become malformed during runtime of the extension.
Initialise your workspace with the Simbank manager and the accompanied Galasa tests. (Create Simbank examples icon). You are able to give this package a desired name. YOUR_PACKAGE_NAME
First, perform a mvn install on YOUR_PACKAGE_NAME.manager, then mvn install on YOUR_PACKAGE_NAME.tests.
Set up your cps.properties with the correct properties to be able to run one of the provisioned tests. The cps.properties is used for personalising specific elements for running Galasa Tests. For running the IVT you will need to set up the following code. These cps.properties allow your tests to be performed on your locally running instance of Simbank that we had previously activated.
zos.dse.tag.SIMBANK.imageid=SIMBANK
zos.dse.tag.SIMBANK.clusterid=SIMBANK
simbank.dse.instance.name=SIMBANK
simbank.instance.SIMBANK.zos.image=SIMBANK
zos.image.SIMBANK.ipv4.hostname=127.0.0.1
zos.image.SIMBANK.telnet.port=2023
zos.image.SIMBANK.webnet.port=2080
zos.image.SIMBANK.telnet.tls=false
zos.image.SIMBANK.credentials=SIMBANK
zosmf.server.SIMBANK.images=SIMBANK
zosmf.server.SIMBANK.hostname=127.0.0.1
zosmf.server.SIMBANK.port=2040
zosmf.server.SIMBANK.https=false
You can also reach the Simbank instance using your 3270-emulator of choice.
Credentials must be coupled with these tests through the use of the credentials.properties file also in .galasa
secure.credentials.SIMBANK.username=IBMUSER
secure.credentials.SIMBANK.password=SYS1
Refresh the test runner tab and you should be able to see the provisioned Simbank Galasa Tests.
Run these Simbank tests by pressing the run-icon next to any test and look at the process in the popped-up terminal.
License
EPL 2.0
