diff --git a/src/data/nav.yaml b/src/data/nav.yaml index ab80c6eb..7a758d98 100644 --- a/src/data/nav.yaml +++ b/src/data/nav.yaml @@ -52,18 +52,18 @@ - title: Debugging a test locally path: /docs/cli-command-reference/cli-runs-local-debug - title: Viewing test results locally - path: /docs/cli-command-reference/viewing-test-results-cli - - title: Exploring Galasa SimBank online - path: /docs/cli-command-reference/simbank-cli - - title: Exploring Galasa SimBank offline - path: /docs/cli-command-reference/simbank-cli-offline + path: /docs/cli-command-reference/viewing-test-results-cli + - title: Exploring Galasa SimBank + path: /docs/running-simbank-tests/exploring-simbank-tests + items: + - title: Running Galasa SimBank online + path: /docs/running-simbank-tests/simbank-cli + - title: Running Galasa SimBank offline + path: /docs/running-simbank-tests/simbank-cli-offline - title: Running the SimBank tests online - path: /docs/cli-command-reference/running-simbank-tests-cli + path: /docs/running-simbank-tests/running-simbank-tests-cli - title: Running the SimBank tests offline - path: /docs/cli-command-reference/running-simbank-tests-cli-offline - - title: Exploring the supplied SimBank tests - path: /docs/exploring-simbank-tests - items: + path: /docs/running-simbank-tests/running-simbank-tests-cli-offline - title: The SimBank IVT path: /docs/running-simbank-tests/simbank-IVT - title: BasicAccountCreditTest diff --git a/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md b/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md index 0e56ac04..6572788f 100644 --- a/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md +++ b/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md @@ -6,13 +6,39 @@ title: "CLI prerequisites online" The following section explains more about the software prerequisites that you need so that you are ready to install Galasa from the Galasa CLI repository in GitHub. -## Prerequisites -| Software | Description | +### Java JDK + +Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. + + +### Maven + +You must install either Maven or Gradle in order to build Galasa projects, which are hierarchical file structures that provide the ability to store and run Galasa tests. + +### Gradle + +You must install either Maven or Gradle in order to build Galasa projects, which are hierarchical file structures that provide the ability to store and run Galasa tests. + +The following table shows the current compatibility between Gradle and Galasa versions: + + +| Gradle release | Compatible Galasa version | | :---- | :-------- | -| Java JDK | Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation.| -| Maven or Gradle | You must install either Maven or Gradle in order to build Galasa projects. Galasa projects are hierarchical file structures that provide the ability to store and run Galasa tests. All Galasa versions are compatible with Gradle releases 6.9.x. Remember to add Gradle to your Path. You can check by running `echo $PATH` on Mac or Unix, or `echo %PATH%` on Windows (PowerShell). | -| 3270 emulator | Optional. Although you do not need a 3270 emulator to run a Galasa test (even if it tests a 3270 application) you can use one to [explore Galasa Simbank online](../cli-command-reference/simbank-cli), a simulated version of an application that helps you get acquainted with Galasa before connecting to a real mainframe to run your own tests. There are many such emulators available but IBM's Personal Communications (PCOMM) is frequently used, as is IBM's Host on Demand software, which includes support for Windows, Linux and MacOS.| +| 6.8.x | All | +| 6.9.x | All | +| 7.x.x | All | +| 8.x.x | 0.36.0 or later | + + +If you are upgrading to Gradle version 8 from an earlier version, see the `Upgrading tests to compile using Gradle version 8` section in the [Upgrading](../upgrading) documentation to understand the changes you need to make to create Galasa projects and build and compile Galasa test code. + +Remember to add Gradle to your PATH. You can check by running `echo $PATH` on Mac or Unix, or `echo %PATH%` on Windows (PowerShell). + + +### 3270 emulator + +Optional. Although you do not need a 3270 emulator to run a Galasa test (even if it tests a 3270 application) you can use one to [run Galasa Simbank online](../running-simbank-tests/simbank-cli), a simulated version of an application that helps you get acquainted with Galasa before connecting to a real mainframe to run your own tests. There are many such emulators available but IBM's Personal Communications (PCOMM) is frequently used, as is IBM's Host on Demand software, which includes support for Windows, Linux and MacOS. ## Next steps diff --git a/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md b/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md index 90adec30..1ac3f8f7 100644 --- a/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md +++ b/src/markdown-pages/docs/cli-command-reference/runs-local-debug.md @@ -125,4 +125,4 @@ galasactl runs submit local --debug Read the [Viewing test results locally](viewing-test-results-cli) documentation to learn how to view the output of your test runs in your local environment. -Take a look at the [Exploring Galasa SimBank online](simbank-cli) or [Exploring Galasa SimBank offline](simbank-cli-offline)documentation. Galasa SimBank is a component that is distributed with Galasa. SimBank simulates a mainframe application and is designed to help you to learn the basic principles of Galasa's operation before you start connecting Galasa to your own mainframe application-under-test. \ No newline at end of file +Take a look at the [Exploring Galasa SimBank](../running-simbank-tests/exploring-simbank-tests) documentation. 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. \ No newline at end of file diff --git a/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md b/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md index 58ce4cad..3cdda364 100644 --- a/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md +++ b/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md @@ -72,14 +72,7 @@ where: - `--log` specifies that debugging information is directed somewhere, and the `-` means that it is sent to the console (stderr). - `--gherkin` specifies the path where the CLI tool can find the Gherkin file containing the Gherkin tests. The path must be specified in a URL form, ending in a `.feature` extension. For example,`file:///Users/myuserid/gherkin/MyGherkinFile.feature` or `file:///C:/Users/myuserid/gherkin/MyGherkinFile.feature`. - -Examples of Galasa Managers in GitHub that have Gherkin support currently available are the -Core Manager, and the -zos3270Terminal Manager. For more information about these Managers, see the [Manager](../managers) documentation section. - - - -For more information about Gherkin, see the Cucumber website. +For more information about the Gherkin support currently available, see the Galasa CLI Gherkin documentation. ## Overriding the path to the default local Maven repository diff --git a/src/markdown-pages/docs/cli-command-reference/viewing-test-results-cli.md b/src/markdown-pages/docs/cli-command-reference/viewing-test-results-cli.md index c428c3fa..2ae476ab 100644 --- a/src/markdown-pages/docs/cli-command-reference/viewing-test-results-cli.md +++ b/src/markdown-pages/docs/cli-command-reference/viewing-test-results-cli.md @@ -31,4 +31,4 @@ You can then view the terminal interactions from your test runs in the `images` ## Next steps -Take a look at the [Exploring Galasa SimBank online](simbank-cli) or [Exploring Galasa SimBank offline](simbank-cli-offline)documentation. 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. \ No newline at end of file +Take a look at the [Exploring Galasa SimBank](../running-simbank-tests/exploring-simbank-tests) documentation. 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. \ No newline at end of file diff --git a/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md b/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md index b51c6df4..dcba9058 100644 --- a/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md +++ b/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md @@ -7,17 +7,44 @@ title: "CLI prerequisites offline" The following section explains more about the software prerequisites that you need to install so that you are ready to install the zipped distribution for Galasa for running offline. -## Prerequisites +### Java JDK +Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. -| Software | Description | +### Gradle + +Required to install the offline zipped distribution. You can also build Galasa projects using Gradle. (You can build projects using Maven if you prefer). Galasa projects are hierarchical file structures that provide the ability to store and run Galasa tests. + +The following table shows the current compatibility between Gradle and Galasa versions: + + +| Gradle release | Compatible Galasa version | | :---- | :-------- | -| Java JDK | Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. | -| Gradle | Required to install the zipped distribution. You can also build Galasa projects using Gradle. (You can build projects using Maven if you prefer). Galasa projects are hierarchical file structures that provide the ability to store and run Galasa tests. All Galasa versions are compatible with Gradle releases 6.9.x.| -| Maven | You must install either Maven or Gradle in order to build Galasa projects. Galasa projects are hierarchical file structures that provide the ability to store and run Galasa tests. You do not explicitly need to install Maven because the Galasa plugin downloads and installs it silently during its own installation and configuration. | -| Docker | Required if using the Docker image. If you want to deploy the Docker image that is provided in the zip file, you will need to have Docker installed. | -| 3270 emulator | Optional. Although you do not need a 3270 emulator to run a Galasa test (even if it tests a 3270 application) you can use one to [explore Galasa Simbank offline](simbank-cli-offline), a simulated version of an application that helps you get acquainted with Galasa before connecting to a real mainframe to run your own tests. There are many such emulators available but IBM's Personal Communications (PCOMM) is frequently used, as is IBM's Host on Demand software, which includes support for Windows, Linux and MacOS.| +| 6.8.x | All | +| 6.9.x | All | +| 7.x.x | All | +| 8.x.x | 0.36.0 or later | + + +If you are upgrading to Gradle version 8 from an earlier version, see the `Upgrading tests to compile using Gradle version 8` section in the [Upgrading](../upgrading) documentation to understand the changes you need to make to create Galasa projects and build and compile Galasa test code. + +Remember to add Gradle to your PATH. You can check by running `echo $PATH` on Mac or Unix, or `echo %PATH%` on Windows (PowerShell). + + + + +### Maven + +You must install either Maven or Gradle in order to build Galasa projects, which are hierarchical file structures that provide the ability to store and run Galasa tests. + + +### Docker + +Required if using the Docker image. If you want to deploy the Docker image that is provided in the zip file, you will need to have Docker installed. + +### 3270 emulator +Optional. Although you do not need a 3270 emulator to run a Galasa test (even if it tests a 3270 application) you can use one to [run Galasa Simbank online](../running-simbank-tests/simbank-cli), a simulated version of an application that helps you get acquainted with Galasa before connecting to a real mainframe to run your own tests. There are many such emulators available but IBM's Personal Communications (PCOMM) is frequently used, as is IBM's Host on Demand software, which includes support for Windows, Linux and MacOS. ## Next steps diff --git a/src/markdown-pages/docs/ecosystem/ecosystem-authentication.md b/src/markdown-pages/docs/ecosystem/ecosystem-authentication.md index 5ead4c22..dc527631 100644 --- a/src/markdown-pages/docs/ecosystem/ecosystem-authentication.md +++ b/src/markdown-pages/docs/ecosystem/ecosystem-authentication.md @@ -36,7 +36,7 @@ To log out of a Galasa Ecosystem using galasactl, you can use the `galasactl aut ### Listing personal access tokens -You can retrieve a list of all active personal access tokens in the Ecosystem by using the `galasactl auth tokens get` command. This information is useful if you need to revoke or delete an access token, for example, if a user moves to a new role, or loses a laptop with their access token on it. +You can retrieve a list of all active personal access tokens in the Ecosystem by using the `galasactl auth tokens get` command. This information is useful if you need to query active tokens with a view to revoking a particular token, for example, if a user moves to a new role, or loses a laptop with their access token on it. The token ID, creation date, username, and description information is returned, as shown in the following example: @@ -49,5 +49,29 @@ tokenid created(YYYY/MM/DD) user description Total:2 ``` -The returned token list is sorted in creation date order, with the earliest creation date first. The description information matches the description that is provided by the user when creating a new access token from the Web UI. +The returned token list is sorted in creation date order, with the earliest creation date first. The description information matches the description that is provided by the user when creating a new access token from the Galasa Web UI. + + +### Revoking personal access tokens + +If a user moves to a new role, or loses a laptop with their personal access token on it, you can log into the Galasa Ecosystem and revoke their access token by using the `galasactl auth tokens delete` command. This ensures that the Ecosystem and systems-under-test remain secure. + +You can retrieve a list of available personal access tokens that have been created, along with their token IDs, by running the `galasactl auth tokens get` command, as described in the previous section. + + +Run the following command to revoke a personal access token with the token ID `myId`: + +``` +galasactl auth tokens delete --tokenid myId +``` + +*Note:* The `galasactl auth tokens delete` command revokes personal access tokens that a user creates through the Galasa Web UI. When a user runs a CLI command that talks to the Ecosystem, the CLI uses the personal access token to get a JSON Web Token (JWT). A JWT is a separate, temporary token that identifies a user and is used in galasactl commands to talk to the API server. JWTs cannot be revoked, but they do expire, so a user can continue to run CLI commands after revoking their personal access token until their JWT expires. You can remove the JWT that is stored on a user's machine instead of having to wait for the JWT to expire, by running the `galasactl auth logout` command on that machine. + +For more information about JWTs, see the `Configuring Dex` section in the [Installing an Ecosystem using Helm](ecosystem-installing-k8s) documentation. + + + + + + diff --git a/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md b/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md index 5dddab24..1967f7e9 100644 --- a/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md +++ b/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md @@ -53,8 +53,8 @@ Complete the following steps to install a Galasa Ecosystem by using Helm: helm repo add galasa https://galasa-dev.github.io/helm ``` - If the repository exists, run the ```helm repo update``` command to get the latest versions of the packages and then run ```helm search repo galasa``` to see the available charts.
- _Note:_ The Galasa Ecosystem Helm chart deploys three persistent volumes (PVs). If you need to provide a Kubernetes storage class for these PVs, download the values.yaml file and update the `storageClass` value in the file with the name of a valid storage class on your cluster. If you are deploying to minikube, you can optionally use the standard storage class that is created for you by minikube, but this is not required. -1. Download the values.yaml file if you have not done so already, and edit the values of the following properties: + _Note:_ The Galasa Ecosystem Helm chart deploys three persistent volumes (PVs). If you need to provide a Kubernetes storage class for these PVs, download the values.yaml file and update the `storageClass` value in the file with the name of a valid storage class on your cluster. If you are deploying to minikube, you can optionally use the standard storage class that is created for you by minikube, but this is not required. +1. Download the values.yaml file if you have not done so already, and edit the values of the following properties: - Set `galasaVersion` to the version of Galasa that you want to run. (See the [Releases](/releases) documentation for released versions). To ensure that each pod in the Ecosystem is running at the same level, do not use `latest` as the Galasa version. - Set `externalHostname` to the DNS hostname or IP address of the Kubernetes node that is used to access the Galasa Ecosystem services. If you are deploying to minikube, the cluster's IP address can be retrieved by running `minikube ip`. @@ -225,14 +225,14 @@ You can then deploy your Galasa tests to a Maven repository and set up a test st ## Upgrading the Galasa Ecosystem -Get the latest version of the Ecosystem chart and upgrade the Galasa Ecosystem to use the newer version of Galasa - for example version 0.35.0 - by running the following command: +Get the latest version of the Ecosystem chart and upgrade the Galasa Ecosystem to use the newer version of Galasa - for example version 0.36.0 - by running the following command: On Mac or Unix: ```console helm repo update \ helm upgrade galasa/ecosystem --reuse-values \ ---set galasaVersion=0.35.0 --wait +--set galasaVersion=0.36.0 --wait ``` On Windows (Powershell): @@ -240,7 +240,7 @@ On Windows (Powershell): ```console helm repo update ` helm upgrade galasa/ecosystem --reuse-values ` ---set galasaVersion=0.35.0 --wait +--set galasaVersion=0.36.0 --wait ``` where:
diff --git a/src/markdown-pages/docs/ecosystem/ecosystem-manage-cps.md b/src/markdown-pages/docs/ecosystem/ecosystem-manage-cps.md index 7fcd445f..fdfb44ef 100644 --- a/src/markdown-pages/docs/ecosystem/ecosystem-manage-cps.md +++ b/src/markdown-pages/docs/ecosystem/ecosystem-manage-cps.md @@ -103,9 +103,9 @@ Property values that are returned from secure namespace types are redacted, so p | `--format raw` | The output from `galasactl properties get` is returned in a form that makes it easy for scripting to digest the individual pieces of data available. Returned values are separated by pipes, without formatting or header information.| -### Retrieve all properties from a namespace +### Retrieve properties from a namespace -To retrieve all properties that are stored in the `framework` namespace in summary format, use the following command:

+To retrieve properties that are stored in the `framework` namespace in summary format, use the following command:

`galasactl properties get --namespace framework` diff --git a/src/markdown-pages/docs/first-steps/exploring-simbank-tests.md b/src/markdown-pages/docs/first-steps/exploring-simbank-tests.md deleted file mode 100644 index c25a2de5..00000000 --- a/src/markdown-pages/docs/first-steps/exploring-simbank-tests.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -path: "/docs/exploring-simbank-tests" -title: "Exploring the supplied SimBank tests" ---- - -Galasa SimBank comes with a selection of prepared Galasa tests. You can find out more about these tests in the following sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. - -A good place to start is with the [SimBank IVT](/docs/running-simbank-tests/simbank-IVT) documentation. You can then move on to look at the other tests that are provided with Galasa. diff --git a/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md b/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md index 0da6768d..8b110a7e 100644 --- a/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md +++ b/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md @@ -140,7 +140,7 @@ The following are properties used to configure the Galasa Ecosystem Manager. | Required: | No | | Default value: | None | | Valid values: | Valid URL | -| Examples: | galasaecosystem.isolated.full.zip=http://cicsk8sm.hursley.ibm.com:31210/galasa-isolated-full-maven-repo.zip | +| Examples: | galasaecosystem.isolated.full.zip=https://resources.galasa.dev/isolated.zip | @@ -154,7 +154,7 @@ The following are properties used to configure the Galasa Ecosystem Manager. | Required: | No | | Default value: | None | | Valid values: | Valid URL | -| Examples: | galasaecosystem.isolated.mvp.zip=http://cicsk8sm.hursley.ibm.com:31210/galasa-isolated-mvp-maven-repo.zip | +| Examples: | galasaecosystem.isolated.mvp.zip=https://github.com/galasa-dev/isolated/releases/download/v0.36.0/galasa-isolated-mvp-0.36.0.zip | diff --git a/src/markdown-pages/docs/managers/sdv-manager.md b/src/markdown-pages/docs/managers/sdv-manager.md index c4305970..bd16e5fc 100644 --- a/src/markdown-pages/docs/managers/sdv-manager.md +++ b/src/markdown-pages/docs/managers/sdv-manager.md @@ -13,7 +13,7 @@ This Manager is at Alpha level.
# Overview -Create an automated integration test in Galasa and use the SDV Manager to obtain a report of the Security Definitions that would have been required if **Resource Security** and **Command Security** were turned on. +Create an automated integration test in Galasa and use the **Security Definition Validation (SDV)** Manager to obtain a report of the Security Definitions that would have been required if **Resource Security** and **Command Security** were turned on. To achieve this, your tests should be **role-based**. Users belonging to particular roles should be used throughout your tests. Their interactions on each unique CICS region under test and the resulting Security Definitions of those interactions, will be recorded. diff --git a/src/markdown-pages/docs/managers/zos-manager.md b/src/markdown-pages/docs/managers/zos-manager.md index cfc15b2b..bd04d158 100644 --- a/src/markdown-pages/docs/managers/zos-manager.md +++ b/src/markdown-pages/docs/managers/zos-manager.md @@ -218,7 +218,7 @@ The following properties are used to configure the z/OS Manager. | Required: | No | | Default value: | None | | Valid values: | A valid IP Host ID | -| Examples: | zos.image.[tag].iphostid=sysa.ibm.com
| +| Examples: | zos.image.[tag].iphostid=sysa.example.com
| diff --git a/src/markdown-pages/docs/managers/zos3270terminal-manager.md b/src/markdown-pages/docs/managers/zos3270terminal-manager.md index f2d4e91c..f8af6b91 100644 --- a/src/markdown-pages/docs/managers/zos3270terminal-manager.md +++ b/src/markdown-pages/docs/managers/zos3270terminal-manager.md @@ -24,7 +24,7 @@ Examples of using colour support and screen sizing are available in the [Code sn When running a Galasa test with the Galasa CLI, terminal images are logged to the run log and PNG representations of the terminal screens can also be saved to the Result Archive Store (RAS) as the outputs are now controlled by the `zos3270.terminal.output` CPS property. -The zos3270Terminal Manager supports Gherkin keywords. +The zos3270Terminal Manager supports Gherkin keywords. *Note:* The feature for saving PNG representations of the terminal screens to the RAS is available in the current release as experimental code only. diff --git a/src/markdown-pages/docs/running-simbank-tests/basic-account-credit-test.md b/src/markdown-pages/docs/running-simbank-tests/basic-account-credit-test.md index 83816d86..079acb87 100644 --- a/src/markdown-pages/docs/running-simbank-tests/basic-account-credit-test.md +++ b/src/markdown-pages/docs/running-simbank-tests/basic-account-credit-test.md @@ -2,7 +2,7 @@ path: "/docs/running-simbank-tests/basic-account-credit-test" title: "BasicAccountCreditTest" --- -This test updates a Galasa SimBank account using web services and examines the changes via some 3270 screens, illustrating how to use web services to interface with the SimBank application, and how to create and use Java methods that you do not wish to be recognized as test methods. +This test updates a Galasa SimBank account using web services and examines the changes via some 3270 screens, illustrating how to use web services to interface with the SimBank application, and how to create and use Java methods that you do not wish to be recognized as test methods. The SimBank Basic Account Credit test is available in the Galasa simplatform repository in GitHub. To run this test, follow the same steps as for `SimBankIVT.java` but using the test class name `BasicAccountCreditTest` instead of `SimBankIVT`. diff --git a/src/markdown-pages/docs/running-simbank-tests/batch-accounts-open-test.md b/src/markdown-pages/docs/running-simbank-tests/batch-accounts-open-test.md index d9240ee5..104a49c7 100644 --- a/src/markdown-pages/docs/running-simbank-tests/batch-accounts-open-test.md +++ b/src/markdown-pages/docs/running-simbank-tests/batch-accounts-open-test.md @@ -2,7 +2,7 @@ path: "/docs/running-simbank-tests/batch-accounts-open-test" title: "BatchAccountsOpenTest" --- -This test uses the z/OS Batch Manager (which in the background, invokes z/OSMF) to add a set of accounts to the Galasa SimBank system via a z/OS batch job. +This test uses the z/OS Batch Manager (which in the background, invokes z/OSMF) to add a set of accounts to the Galasa SimBank system via a z/OS batch job. The SimBank Batch Accounts Open test is available in the Galasa simplatform repository in GitHub. When you installed Galasa, some of the configuration information set in the `overrides.properties` file is specific to the z/OSMF and z/OS Batch Managers. Confirm that the file - it's located in your `.galasa` folder - contains, in its entirety: diff --git a/src/markdown-pages/docs/running-simbank-tests/exploring-simbank-tests.md b/src/markdown-pages/docs/running-simbank-tests/exploring-simbank-tests.md new file mode 100644 index 00000000..127b67f9 --- /dev/null +++ b/src/markdown-pages/docs/running-simbank-tests/exploring-simbank-tests.md @@ -0,0 +1,13 @@ +--- +path: "/docs/running-simbank-tests/exploring-simbank-tests" +title: "Exploring Galasa SimBank" +--- + +Distributed with Galasa, SimBank is a component that simulates a mainframe application. It sits above another component called SimPlatform. As delivered, SimBank implements a sample banking application against which you can configure and run a set of provided tests in preparation for running your own tests against an *actual* mainframe application. You can also practice writing some new tests to run against the SimBank banking application. + +By exercising the Galasa framework against SimBank, you can pre-empt a lot (but not all) of the work and learning necessary to eventually hook your own tests up with a genuine mainframe environment. If the provided SimBank tests do not work, then it is unlikely that you will be able to run your own tests on a mainframe application. In summary, SimBank helps you to understand Galasa's basic principles of operation before you learn how to connect Galasa to your own mainframe application-under-test. Start by installing Galasa Simbank, either using the +[Running Galasa SimBank online](simbank-cli) documentation if you are working with the Galasa CLI repository in GitHub, or the [Running Galasa SimBank offline](simbank-cli-offline) documentation if you are using the Galasa zipped distribution. + +Galasa SimBank comes with a selection of prepared Galasa tests. You can find out more about these tests in the following sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. A good place to start is with the [SimBank IVT](simbank-IVT) documentation. You can then move on to look at the other tests that are provided with Galasa. Sample SimBank tests are available in the Galasa simplatform repository in GitHub. + + diff --git a/src/markdown-pages/docs/running-simbank-tests/provisioned-account-credit-tests.md b/src/markdown-pages/docs/running-simbank-tests/provisioned-account-credit-tests.md index 4e463c51..cd895730 100644 --- a/src/markdown-pages/docs/running-simbank-tests/provisioned-account-credit-tests.md +++ b/src/markdown-pages/docs/running-simbank-tests/provisioned-account-credit-tests.md @@ -2,7 +2,7 @@ path: "/docs/running-simbank-tests/provisioned-account-credit-tests" title: "ProvisionedAccountCreditTests" --- -To run this test, follow the same steps as for `SimBankIVT.java` but using the test class name `ProvisionedAccountCreditTests` instead of `SimBankIVT`. +To run this test, follow the same steps as for `SimBankIVT.java` but using the test class name `ProvisionedAccountCreditTests` instead of `SimBankIVT`. The SimBank Provisioned Account Credit test is available in the Galasa simplatform repository in GitHub. This test performs the same function as `BasicAccountCreditTest.java` but has an improved design which includes the use of a provisioned account object, which, once declared as: ```java diff --git a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli-offline.md b/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli-offline.md similarity index 91% rename from src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli-offline.md rename to src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli-offline.md index 1539a7ba..5805ddf9 100644 --- a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli-offline.md +++ b/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli-offline.md @@ -1,5 +1,5 @@ --- -path: "/docs/cli-command-reference/running-simbank-tests-cli-offline" +path: "/docs/running-simbank-tests/running-simbank-tests-cli-offline" title: "Running the SimBank tests using the CLI offline" --- @@ -10,7 +10,7 @@ You can explore Galasa further with Galasa Simbank. Galasa Simbank is a simulate - A test that uses a provisioned account object to perform the same test as `BasicAccountCreditTest.java` in an improved test design - `ProvisionedAccountCreditTests.java`. - A test that exercises the z/OS Batch Manager by simulating the submission of a JCL job to add a number of accounts to the SimBank system - `BatchAccountsOpenTest.java`. -The following sections explain how to run the `SimBankIVT` test class by using the CLI. Make sure that you have installed the Galasa CLI tool and Java version 11 JDK, and have set the JAVA_HOME environment variable, as described in the [CLI prerequisites offline](zipped-prerequisites) documentation. +The following sections explain how to run the `SimBankIVT` test class by using the CLI. Make sure that you have installed the Galasa CLI tool and Java version 11 JDK, and have set the JAVA_HOME environment variable, as described in the [CLI prerequisites offline](../cli-command-reference/zipped-prerequisites) documentation. ## Updating the overrides and credentials property files @@ -50,7 +50,7 @@ In order to run the Galasa SimBanks tests you need to add some configuration inf The SimBank tests are located in the `maven` directory of the `isolated.zip` downloadable file. Complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0`. -Remember to initialise your local environment by running the `galasactl local init` command and to start the SimPlatform server by running the `run-simplatform.sh` script, as described in the `Launching SimBank` section in the [Exploring Galasa SimBank using the CLI offline](simbank-cli-offline) documentation. +Remember to initialise your local environment by running the `galasactl local init` command and to start the SimPlatform server by running the `run-simplatform.sh` script, as described in the [Running Galasa SimBank using the CLI offline](simbank-cli-offline) documentation. You are now ready to run a local Galasa test offline with just the contents of the zipped distribution. @@ -72,7 +72,7 @@ galasactl runs submit local --log - ` ``` Note that the `--localMaven` flag refers to the `maven` directory inside the _isolated.zip_ as these are all the Maven artifacts that should be needed to run the test, including the `dev.galasa.simbank.obr` artifact which is passed to the `--obr` flag and the `SimBankIVT` test class which is passed to `class`. 1. The `SimBankIVT` test class runs, and the terminal displays its progress through to completion, with an Exit code of `0`. -1. View the results of the test runs in your terminal. You can also view results in the `run.log` file in the result archive store (RAS). 3270 terminal interactions can be viewed in the `artifacts` directory in the RAS. Find out more in the [Viewing test results locally](viewing-test-results-cli) documentation. +1. View the results of the test runs in your terminal. You can also view results in the `run.log` file in the result archive store (RAS). 3270 terminal interactions can be viewed in the `artifacts` directory in the RAS. Find out more in the [Viewing test results locally](../cli-command-reference/viewing-test-results-cli) documentation. To run other SimBank tests, for example `BasicAccountCreditTest`, replace the test class name in the `--class` parameter. Remember to update the `--localMaven` flag value to the location of the `maven` directory as well. For example: @@ -98,4 +98,4 @@ galasactl runs submit local --log - ` ## Next steps -Explore the SimBankIVT test and the other SimBank tests in the [Exploring the supplied SimBank tests](/docs/exploring-simbank-tests) sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. \ No newline at end of file +Explore the SimBankIVT test and the other SimBank tests in the [Exploring Galasa SimBank](exploring-simbank-tests) sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. \ No newline at end of file diff --git a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md b/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md similarity index 94% rename from src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md rename to src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md index 609e1fd3..e750fe6c 100644 --- a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md +++ b/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md @@ -1,5 +1,5 @@ --- -path: "/docs/cli-command-reference/running-simbank-tests-cli" +path: "/docs/running-simbank-tests/running-simbank-tests-cli" title: "Running the SimBank tests using the CLI" --- @@ -10,7 +10,7 @@ You can explore Galasa further with Galasa Simbank. Galasa Simbank is a simulate - A test that uses a provisioned account object to perform the same test as `BasicAccountCreditTest.java` in an improved test design - `ProvisionedAccountCreditTests.java`. - A test that exercises the z/OS Batch Manager by simulating the submission of a JCL job to add a number of accounts to the SimBank system - `BatchAccountsOpenTest.java`. -The following sections explain how to run the `SimBankIVT` test class by using the CLI. Make sure that you have installed the Galasa CLI tool and Java version 11 JDK, and have set the JAVA_HOME environment variable, as described in the [CLI prerequisites online](cli-prereqs) documentation. +The following sections explain how to run the `SimBankIVT` test class by using the CLI. Make sure that you have installed the Galasa CLI tool and Java version 11 JDK, and have set the JAVA_HOME environment variable, as described in the [CLI prerequisites online](../cli-command-reference/cli-prereqs) documentation. ## Updating the overrides and credentials property files @@ -48,9 +48,9 @@ In order to run the Galasa SimBanks tests you need to add some configuration inf ## Running the SimBank IVT test class by using the CLI -The SimBank tests are held in the Galasa simplatform repository in GitHub. To start running the tests you need to clone the repository, if you have not already done so. To find out how to clone the cli repository, follow the instruction in the `Launching SimBank` section in the [Exploring Galasa SimBank online](simbank-cli) documentation. +The SimBank tests are held in the Galasa simplatform repository in GitHub. To start running the tests you need to clone the repository, if you have not already done so. To find out how to clone the cli repository, follow the instruction in the [Running Galasa SimBank online](../running-simbank-tests/simbank-cli) documentation. -After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.35.0`. +After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.36.0`. You can find the version of the `dev.galasa.simbank.obr` that you are using by looking in the `pom.xml` file in the `dev.galasa.simbank.obr` folder. The `dev.galasa.uber.obr` is the OBR that contains all the bundles that are needed for Galasa to work including Managers, any required dependencies, the framework, etc. The version of the `dev.galasa.uber.obr` depends on which version of Galasa you have installed. @@ -123,4 +123,4 @@ galasactl runs submit local --log - ` ## Next steps -Explore the SimBankIVT test and the other SimBank tests in the [Exploring the supplied SimBank tests](/docs/exploring-simbank-tests) sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. \ No newline at end of file +Explore the SimBankIVT test and the other SimBank tests in the [Exploring Galasa SimBank](exploring-simbank-tests) sections. Follow the flow of logic in these classes and understand more about the Java that is used to create them, including how to use Galasa annotations and review documented test methods. \ No newline at end of file diff --git a/src/markdown-pages/docs/running-simbank-tests/simbank-IVT.md b/src/markdown-pages/docs/running-simbank-tests/simbank-IVT.md index f9c67946..73afb612 100644 --- a/src/markdown-pages/docs/running-simbank-tests/simbank-IVT.md +++ b/src/markdown-pages/docs/running-simbank-tests/simbank-IVT.md @@ -3,7 +3,7 @@ path: "/docs/running-simbank-tests/simbank-IVT" title: "The SimBank Installation Verification Test" --- -This basic test logs on to Galasa SimBank and examines an account. +This basic test logs on to Galasa SimBank and examines an account. The SimBank IVT test is available in the Galasa simplatform repository in GitHub. ## Exploring the `SimBankIVT` test class @@ -11,7 +11,7 @@ Even without any prior knowledge of Galasa, if you know a little Java, you will The class is first annotated with `@Test` - informing the framework that a method or (as in this case) a class is a test. -Next at the beginning of the test class proper, several Galasa Managers are declared via annotations, together with their corresponding public interfaces - `@ZosImage`, `@Zos3270Terminal` and so on. Using the `imageTag="SIMBANK"` argument with `@ZosImage` allows you to associate an instance of a Manager with a set of configuration properties. In this example, the associated configuration properties are the ones that are set in the `overrides.properties` file, as described in the [Running the SimBank tests online](/docs/cli-command-reference/running-simbank-tests-cli) and [Running the SimBank tests offline](/docs/cli-command-reference/running-simbank-tests-cli-offline) documentation. +Next at the beginning of the test class proper, several Galasa Managers are declared via annotations, together with their corresponding public interfaces - `@ZosImage`, `@Zos3270Terminal` and so on. Using the `imageTag="SIMBANK"` argument with `@ZosImage` allows you to associate an instance of a Manager with a set of configuration properties. In this example, the associated configuration properties are the ones that are set in the `overrides.properties` file, as described in the [Exploring the SimBank tests online](running-simbank-tests-cli) and [Exploring the SimBank tests offline](running-simbank-tests-cli-offline) documentation. ```java @Test diff --git a/src/markdown-pages/docs/cli-command-reference/simbank-cli-offline.md b/src/markdown-pages/docs/running-simbank-tests/simbank-cli-offline.md similarity index 89% rename from src/markdown-pages/docs/cli-command-reference/simbank-cli-offline.md rename to src/markdown-pages/docs/running-simbank-tests/simbank-cli-offline.md index e3fc7976..c71265d3 100644 --- a/src/markdown-pages/docs/cli-command-reference/simbank-cli-offline.md +++ b/src/markdown-pages/docs/running-simbank-tests/simbank-cli-offline.md @@ -1,13 +1,8 @@ --- -path: "/docs/cli-command-reference/simbank-cli-offline" +path: "/docs/running-simbank-tests/simbank-cli-offline" title: "Exploring Galasa SimBank offline" --- -Distributed with Galasa, SimBank is a component that simulates a mainframe application. It sits above another component called SimPlatform. As delivered, SimBank implements a sample banking application against which you can configure and run a set of provided tests in preparation for running your own tests against an *actual* mainframe application. You can also practice writing some new tests to run against the SimBank banking application. -By exercising the Galasa framework against SimBank, you can pre-empt a lot (but not all) of the work and learning necessary to eventually hook your own tests up with a genuine mainframe environment. If the provided SimBank tests do not work, then it is unlikely that you will be able to run your own tests on a mainframe application. In summary, SimBank helps you to understand Galasa's basic principles of operation before you learn how to connect Galasa to your own mainframe application-under-test. - - -## Launching SimBank offline SimBank applications and a set of sample SimBank tests are located in the `maven` directory of the `isolated.zip` downloadable file. diff --git a/src/markdown-pages/docs/cli-command-reference/simbank-cli.md b/src/markdown-pages/docs/running-simbank-tests/simbank-cli.md similarity index 88% rename from src/markdown-pages/docs/cli-command-reference/simbank-cli.md rename to src/markdown-pages/docs/running-simbank-tests/simbank-cli.md index 94c04c6f..90f3d0c0 100644 --- a/src/markdown-pages/docs/cli-command-reference/simbank-cli.md +++ b/src/markdown-pages/docs/running-simbank-tests/simbank-cli.md @@ -1,12 +1,8 @@ --- -path: "/docs/cli-command-reference/simbank-cli" -title: "Exploring Galasa SimBank online" +path: "/docs/running-simbank-tests/simbank-cli" +title: "Launching Galasa SimBank online" --- -Distributed with Galasa, SimBank is a component that simulates a mainframe application. It sits above another component called SimPlatform. As delivered, SimBank implements a sample banking application against which you can configure and run a set of provided tests in preparation for running your own tests against an *actual* mainframe application. You can also practice writing some new tests to run against the SimBank banking application. -By exercising the Galasa framework against SimBank, you can pre-empt a lot (but not all) of the work and learning necessary to eventually hook your own tests up with a genuine mainframe environment. If the provided SimBank tests do not work, then it is unlikely that you will be able to run your own tests on a mainframe application. In summary, SimBank helps you to understand Galasa's basic principles of operation before you learn how to connect Galasa to your own mainframe application-under-test. - -## Launching SimBank SimBank applications and a set of sample SimBank tests are located in the Galasa simplatform repository in GitHub. To start exploring the Galasa Simbank application and to run the sample SimBank tests by using the Galasa CLI, you need to complete the following steps: diff --git a/src/markdown-pages/docs/running-simbank-tests/web-app-integration-test.md b/src/markdown-pages/docs/running-simbank-tests/web-app-integration-test.md index 857f9a68..0a11c600 100644 --- a/src/markdown-pages/docs/running-simbank-tests/web-app-integration-test.md +++ b/src/markdown-pages/docs/running-simbank-tests/web-app-integration-test.md @@ -3,7 +3,7 @@ path: "/docs/running-simbank-tests/web-app-integration-test" title: "WebAppIntegrationTest" --- -The `WebAppIntegrationTest` is somewhat different to the previously described Galasa SimBank tests. It shows how you can use Galasa to test a hybrid cloud application that uses a mix of platforms and technologies. A mix of technologies makes end-to-end integration testing complicated. Use the `WebAppIntegrationTest` to help understand how Galasa simplifies integration testing in such an environment. +The `WebAppIntegrationTest` is somewhat different to the previously described Galasa SimBank tests. It shows how you can use Galasa to test a hybrid cloud application that uses a mix of platforms and technologies. A mix of technologies makes end-to-end integration testing complicated. Use the `WebAppIntegrationTest` to help understand how Galasa simplifies integration testing in such an environment. The SimBank Web App Integration test is available in the Galasa simplatform repository in GitHub. ## About the WebAppIntegrationTest diff --git a/src/markdown-pages/docs/running-simbank-tests/writing-a-simbank-test.md b/src/markdown-pages/docs/running-simbank-tests/writing-a-simbank-test.md index a3fa786d..0b6809e9 100644 --- a/src/markdown-pages/docs/running-simbank-tests/writing-a-simbank-test.md +++ b/src/markdown-pages/docs/running-simbank-tests/writing-a-simbank-test.md @@ -11,7 +11,7 @@ Don't forget that whenever you create a test, or modify an existing one, you nee ## Create a new Galasa test class -1. Launch SimBank using the instructions in the [CLI online](../cli-command-reference/simbank-cli) or [CLI offline](../cli-command-reference/simbank-cli) documentation. +1. Launch SimBank using the instructions in the [CLI online](../running-simbank-tests/simbank-cli) or [CLI offline](../running-simbank-tests/simbank-cli-offline) documentation. 1. Create a new test class. If you are using the CLI, manually create the test class file, for example in VS Code. Complete the next dialog as follows and then click *Finish*. Note that in the example a new package is created that is called `dev.galasa.simbanks.tests`. ![New Java Class](./create-new-class.png) 1. Annotate the new class with the `@Test` annotation. diff --git a/src/markdown-pages/docs/upgrading.md b/src/markdown-pages/docs/upgrading.md index b54779a1..925e9605 100644 --- a/src/markdown-pages/docs/upgrading.md +++ b/src/markdown-pages/docs/upgrading.md @@ -3,9 +3,18 @@ path: "/docs/upgrading" title: "Upgrading" --- -## Upgrading (online) -You can get the upgrade your version of Galasa by completing the following steps: +[Upgrading the Galasa version (online)](#Upgradeonline)
+[Upgrading the Galasa zipped distribution version (offline)](#Upgradeoffline)
+[Upgrading tests to compile using Gradle version 8](#UpgradeGradle)
+[Moving from Eclipse to the Galasa CLI](#EclipsetoCLI)
+[Upgrading tests created against an earlier version of Galasa](#Upgradingtests)
+[Troubleshooting](#Troubleshooting)
+ + +## Upgrading the Galasa version (online) + +You can upgrade your version of Galasa by completing the following steps: 1. Download the appropriate version of the Galasa CLI for your machine architecture from the Galasa CLI repository in GitHub. 2. Re-name the your existing `galasactl` binary so that you can re-name the Galasa binary that you just downloaded to `galasactl` to replace it. @@ -14,13 +23,44 @@ You can get the upgrade your version of Galasa by completing the following steps If you have already added the Galasa CLI path to your shell's initialization file, as described in the [Installing the Galasa CLI online](../docs/cli-command-reference/installing-cli-tool) topic, you should now be able to run the upgraded version of the Galasa CLI tool from any directory in your file system. -## Upgrading the Galasa zipped distribution using the command line (offline) +## Upgrading the Galasa zipped distribution version (offline) Download and extract the Galasa zip file to a directory of your choice and complete the steps documented in the [Installing the Galasa CLI offline](../docs/cli-command-reference/installing-offline) topic. +## Upgrading tests to compile using Gradle version 8 + +Galasa releases 0.35.0 and earlier support the use of Gradle versions 6.8.x, 6.9.x, and 7.x.x to create Galasa projects and build Galasa test code. From release 0.36.0 and later, Galasa additionally supports the use of Gradle version 8.x.x. + +To use Gradle version 8.0 or later to create Galasa projects and build and compile Galasa test code, complete the following steps: + +1. Edit the `build.gradle` file in the OBR directory of your parent project, setting the plug-in values at the top of the file to version `0.36.0`, as shown in the following example: +``` +plugins { +... +id 'dev.galasa.obr' version '0.36.0' +id 'dev.galasa.testcatalog' version '0.36.0' +... +} +``` +2. Add the following task definition to the `build.gradle` file in the OBR directory of the parent project to ensure that Gradle uses the correct build order. + +```groovy +tasks.withType(PublishToMavenLocal) { task -> + task.dependsOn genobr + task.dependsOn mergetestcat +} +``` +3. In each test project `build.gradle` file, set the `dev.galasa.tests` plug-in to version `0.36.0` to ensure that the build uses the correct plug-in. +``` +plugins { +... +id 'dev.galasa.tests' version '0.36.0' +... +} +``` -## Upgrading from using Eclipse to using the command line (online) +## Moving from Eclipse to the Galasa CLI Version 0.31.0 is the last version of the Eclipse plug-in for Galasa that is produced and maintained by the Galasa Team. You can work with later versions of Galasa by using the Galasa command line interface (CLI). The galasactl tool can do everything that the Eclipse tooling can do, and can be run from the command-line of any IDE, for example, the Eclipse terminal view. @@ -38,8 +78,7 @@ To upgrade to a Galasa version that uses the CLI when your previous Galasa versi If you encounter any difficulties, reach out for help in our Galasa Slack workspace in the `#galasa-users` channel. - -## Upgrading existing tests +## Upgrading tests created against an earlier version of Galasa If you have a pre-built version of tests that were created against an earlier version of Galasa in your local repository, you need to rebuild those test projects and any associated Managers after ugprading, so that the pom.xml files of those tests and Managers specify the new version of Galasa. @@ -73,7 +112,8 @@ A simple way to do this is to complete the following steps: a. Go to *File > Preferences > Settings* and expand the *Extensions* section.

b. Select *Galasa* and check that the *Version* field is using the default value of ```main```, to automatically select the latest version. -## Troubleshooting + +## Troubleshooting If you have problems after completing the steps for upgrading, try running a clean install. diff --git a/src/markdown-pages/docs/writing-own-tests/binding-tests.md b/src/markdown-pages/docs/writing-own-tests/binding-tests.md index 2cd70f6c..3d7ff0c3 100644 --- a/src/markdown-pages/docs/writing-own-tests/binding-tests.md +++ b/src/markdown-pages/docs/writing-own-tests/binding-tests.md @@ -31,7 +31,7 @@ The test declares that a z/OS image is required for the test to run and that thi When the z/OS Manager reads the code, it creates a z/OS image by using the *imageTag* attribute to ascertain which set of properties from the `cps.properties` or `overrides.properties` file that it needs to load to create that image. -In this example, the following properties are associated with the *SIMBANK* z/OS image in the `overrides.properties` file, as described in the [Running the SimBank tests using the CLI](../cli-command-reference/running-simbank-tests-cli) documentation: +In this example, the following properties are associated with the *SIMBANK* z/OS image in the `overrides.properties` file, as described in the [Running the SimBank tests using the CLI](../running-simbank-tests/running-simbank-tests-cli) documentation: ``` zos.image.SIMBANK.ipv4.hostname=127.0.0.1 zos.image.SIMBANK.telnet.port=2023 diff --git a/src/markdown-pages/highlights.md b/src/markdown-pages/highlights.md index 27d4882c..8f451442 100644 --- a/src/markdown-pages/highlights.md +++ b/src/markdown-pages/highlights.md @@ -17,15 +17,33 @@ We have the following available Slack channels: Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and open issues in the [project management repository](https://github.com/galasa-dev/projectmanagement). -## 0.35.0 - Release Highlights + +## 0.36.0 - Release Highlights + +- You can now create Galasa projects and build and compile Galasa test code using Gradle version 8. For more information, see the `Upgrading tests to compile using Gradle version 8` section in the [Upgrading](docs/upgrading) documentation to understand the changes you need to make. + +- Log into the Galasa Ecosystem and revoke a personal access token by using the `galasactl auth tokens delete` command. + +- Set terminal size within Gherkin tests (previously only available in Java tests) and use Scenario Outlines. + +- Various updates to the Galasa Web UI + +- Various defect fixes + +- Various documentation updates + + +
+0.35.0 - Release Highlights - A fix to the database connector of the DB2 Manager +
0.34.1 - Release Highlights -- Retrieve a list of all active personal access tokens in the Ecosystem by using the `galasactl auth tokens get` command. Use the information to revoke or delete an access token. +- Retrieve a list of all active personal access tokens in the Ecosystem by using the `galasactl auth tokens get` command. Use the information to revoke an access token. - The default size of the PVC storage allocated by the Helm chart is increased from 1GB to 30GB and automatic history compaction is now turned on by default to minimise the risk of etcd running out of space. @@ -309,7 +327,7 @@ zosmf.image.IMAGEID.servers=SERVERID,SERVERID ``` If you have zOS/MF servers on each z/OS image, the following properties are the minimum that are required: ``` -zos.image.MV2D.ipv4.hostname=winmvs2d.hursley.ibm.com +zos.image.MV2D.ipv4.hostname=mv2d.example.com zosmf.server.port=9999 ``` These settings assume a zOS/MF server on MV2D and the port overridden from `443` to `9999` for all zOS/MF servers. diff --git a/src/pages/index.js b/src/pages/index.js index 51fa499b..928902db 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -126,7 +126,7 @@ const IndexPage = () => ( Learn more