Galasa allows clients to deliver software with confidence by simplifying and encouraging automated integration testing to help Mainframe modernisation within Hybrid Cloud environments and increase the reliability of repeatable software releases. Galasa is an integration test framework that has a strong focus on z/OS and providing a framework and test runner to not only test z/OS applications but enterprise wide applications that require the test to have a deep understanding of the mainframe. Galasa begun as an internal CICS-only test framework that enabled agile processes for the CICS development team. As CICS capabilities grew so did those in Galasa to enable the testing of those new capabilities. Customers were interested in adopting similar technology to CICS to equally accelerate their dev ops ambitions, which is why Galasa decided to become open-sourced.
Statement on alignment with Open Mainframe Project Mission and Vision statements
Galasa's automation of integration testing is aligned with the OMP’s objective of enhancing the quality, reliability, and availability of Mainframe systems, as it enables developers to efficiently identify and correct errors, minimising the possibility of downtime and excessive manual testing. Moreover, Galasa's adoption of modern development methodologies such as agile development, continuous integration and deployment, and CLI technology advances the OMP's vision of modernising Mainframe development and expanding its accessibility to a broader spectrum of developers, even enabling the possibility of cloud-based interaction with Mainframe systems.
Are there similar/related projects out there?
Although there are a multitude of test frameworks, none give the focus to z/OS and provide strong capabilities across 3270, JCL, File IO and middleware capability as Galasa. Secondly, the mechanism in which Galasa combines and integrates technology together is open, allowing any technology to be brought in the the same test context.
Name of Committer | ID | Duration on Project | Extent of contributions | Vendor
Will Yates | hobbit1983 | 4years | 149 | IBM
James Davies | Jimbo4794 | 4years | 144 | IBM
Michael Cobbet | tech cobweb | 1 year | 47 | IBM
Jade Carino | jadecarino | 3 years | 109 | IBM
Aaron Jhaj | AaronJhaj | 1 year | 7 | IBM
Eamonn Mansour | eamansour | 1 year | 33 | IBM
Savvas Kyriacou | KirbyKatcher | 1 year | 16 | IBM
Caroline McNamara | caromac | 4years | 640 | IBM
Petr Plavjanik | TBC | TBC | TBC | Broadcom
Broadcom Contributors - TBC
We have already had some PRs merged from Broadcom. One of our largest client adopters have already designs on code they wish to contribute back to the community. However both are restricted from going further due to the current lack of a open governance model, something that OMP adoption will help to guide us with.
Infrastructure requests
Galasa is currently built using Tekton on infrastructure provided by IBM but behind the firewall, ideally we would like to move this externally
Development builds for Galasa are hosted externally on IBM Cloud using custom containers within a K8s cluster
Web Site hosting / Domain Management is performed by IBM Cloud
Galasa is released through maven central and is released at the end of a 2 week sprint if the team feel there is adequate new value for the project to have a release
Social media accounts
TBD
Community size and any existing sponsorship
IBM Internal
Slack - Galasa currently has 86 users on #galasa-users and 69 users on #galasa
External
Slack - 174 current members (excluding bots)
At least 21 individual companies represented within the community
Project description
Galasa allows clients to deliver software with confidence by simplifying and encouraging automated integration testing to help Mainframe modernisation within Hybrid Cloud environments and increase the reliability of repeatable software releases. Galasa is an integration test framework that has a strong focus on z/OS and providing a framework and test runner to not only test z/OS applications but enterprise wide applications that require the test to have a deep understanding of the mainframe. Galasa begun as an internal CICS-only test framework that enabled agile processes for the CICS development team. As CICS capabilities grew so did those in Galasa to enable the testing of those new capabilities. Customers were interested in adopting similar technology to CICS to equally accelerate their dev ops ambitions, which is why Galasa decided to become open-sourced.
Statement on alignment with Open Mainframe Project Mission and Vision statements
Galasa's automation of integration testing is aligned with the OMP’s objective of enhancing the quality, reliability, and availability of Mainframe systems, as it enables developers to efficiently identify and correct errors, minimising the possibility of downtime and excessive manual testing. Moreover, Galasa's adoption of modern development methodologies such as agile development, continuous integration and deployment, and CLI technology advances the OMP's vision of modernising Mainframe development and expanding its accessibility to a broader spectrum of developers, even enabling the possibility of cloud-based interaction with Mainframe systems.
Are there similar/related projects out there?
Although there are a multitude of test frameworks, none give the focus to z/OS and provide strong capabilities across 3270, JCL, File IO and middleware capability as Galasa. Secondly, the mechanism in which Galasa combines and integrates technology together is open, allowing any technology to be brought in the the same test context.
Sponsor from TAC
Joe Bostian
Proposed Project Stage
Active
License and contribution guidelines
EPL v2
Current or desired source control repository
Github (GitHub.com/galasa-dev)
External dependencies (including licenses)
commons-collections-3.2.2.jar | Apache 2.0 commons-logging-1.2.jar | Apache 2.0 commons-collections4-4.4.jar | Apache 2.0 validation-api-2.0.1.Final.jar | Apache 2.0 commons-codec-1.15.jar | Apache 2.0 httpclient-4.5.13.jar | Apache 2.0 commons-lang-2.6.jar | Apache 2.0 httpmime-4.5.13.jar | Apache 2.0 httpcore-4.4.14.jar | Apache 2.0 derbyclient-10.14.2.0.jar | Apache 2.0 assertj-core-3.11.1.jar | Apache 2.0 commons-lang3-3.12.0.jar | Apache 2.0 simpleclient-0.6.0.jar | Apache 2.0 simpleclient_common-0.6.0.jar | Apache 2.0 commons-io-2.9.0.jar | Apache 2.0 simpleclient_httpserver-0.6.0.jar | Apache 2.0 commons-compress-1.21.jar | Apache 2.0 httpclient-cache-4.5.13.jar | Apache 2.0 velocity-engine-core-2.3.jar | Apache 2.0 selenium-api-3.141.59.jar | Apache 2.0 selenium-remote-driver-3.141.59.jar | Apache 2.0 selenium-edge-driver-3.141.59.jar | Apache 2.0 selenium-chrome-driver-3.141.59.jar | Apache 2.0 selenium-ie-driver-3.141.59.jar | Apache 2.0 selenium-firefox-driver-3.141.59.jar | Apache 2.0 selenium-opera-driver-3.141.59.jar | Apache 2.0 simpleclient_hotspot-0.6.0.jar | Apache 2.0 fluent-hc-4.5.13.jar | Apache 2.0 org.osgi.service.component.annotations-1.3.0.jar | Apache 2.0 log4j-core-2.17.1.jar | Apache 2.0 log4j-slf4j-impl-2.17.1.jar | Apache 2.0 log4j-api-2.17.1.jar | Apache 2.0 httpclient-osgi-4.5.13.jar | Apache 2.0 gson-2.9.0.jar | Apache 2.0 httpcore-osgi-4.4.14.jar | Apache 2.0 org.apache.felix.fileinstall-3.6.4.jar | Apache 2.0 org.apache.felix.gogo.shell-1.1.2.jar | Apache 2.0 org.apache.felix.gogo.runtime-1.1.2.jar | Apache 2.0 org.apache.felix.configadmin-1.9.16.jar | Apache 2.0 org.apache.felix.gogo.command-1.1.0.jar | Apache 2.0 bcel-6.7.0.jar | Apache 2.0 org.apache.felix.http.jetty-5.0.0.jar | Apache 2.0 org.apache.felix.http.servlet-api-2.1.0.jar | Apache 2.0 snakeyaml-2.0.jar | Apache 2.0 biz.aQute.resolve-5.3.0.jar | Apache 2.0, Eclipse 2.0 biz.aQute.bnd.gradle-5.3.0.jar | Apache 2.0, Eclipse 2.0 biz.aQute.bnd.embedded-repo-5.3.0.jar | Apache 2.0, Eclipse 2.0 biz.aQute.repository-5.3.0.jar | Apache 2.0, Eclipse 2.0 biz.aQute.bndlib-5.3.0.jar | Apache 2.0, Eclipse 2.0 biz.aQute.bnd.builder.gradle.plugin-5.3.0.jar | Apache 2.0, Eclipse 2.0 bcpkix-jdk15on-1.69.jar | Bouncy Castle License bcprov-jdk15on-1.69.jar | Bouncy Castle License bcutil-jdk15on-1.69.jar | Bouncy Castle License jakarta.activation-2.0.0.jar | BSD 3 jakarta.xml.bind-api-3.0.0.jar | BSD 3 jaxb-osgi-3.0.0.jar | BSD 3 dev.galasa.ras.couchdb-0.21.0.jar | Eclipse 2.0 dev.galasa.cicsts.manager.ivt-0.22.0.jar | Eclipse 2.0 dev.galasa.db2.manager.ivt-0.21.0.jar | Eclipse 2.0 dev.galasa.cps.etcd-0.21.0.jar | Eclipse 2.0 dev.galasa-0.21.0.jar | Eclipse 2.0 dev.galasa.zos3270.common-0.25.0.jar | Eclipse 2.0 xbasej-xBaseJ20221201 | LGPL 3.0 slf4j-api-1.7.30.jar | MIT slf4j-api-1.7.25.jar | MIT jquery-3.5.1.min.js | MIT
Initial committers
Name of Committer | ID | Duration on Project | Extent of contributions | Vendor Will Yates | hobbit1983 | 4years | 149 | IBM James Davies | Jimbo4794 | 4years | 144 | IBM Michael Cobbet | tech cobweb | 1 year | 47 | IBM Jade Carino | jadecarino | 3 years | 109 | IBM Aaron Jhaj | AaronJhaj | 1 year | 7 | IBM Eamonn Mansour | eamansour | 1 year | 33 | IBM Savvas Kyriacou | KirbyKatcher | 1 year | 16 | IBM Caroline McNamara | caromac | 4years | 640 | IBM Petr Plavjanik | TBC | TBC | TBC | Broadcom
Broadcom Contributors - TBC
We have already had some PRs merged from Broadcom. One of our largest client adopters have already designs on code they wish to contribute back to the community. However both are restricted from going further due to the current lack of a open governance model, something that OMP adoption will help to guide us with.
Infrastructure requests
Galasa is currently built using Tekton on infrastructure provided by IBM but behind the firewall, ideally we would like to move this externally
Development builds for Galasa are hosted externally on IBM Cloud using custom containers within a K8s cluster
Web Site hosting / Domain Management is performed by IBM Cloud
Communication channels
galasa.slack.com - slack workspace
Communication channels
GitHub.com/galasa-dev/projectmanagement
Website
https://galasa.dev
Release methodology and mechanics
Galasa is released through maven central and is released at the end of a 2 week sprint if the team feel there is adequate new value for the project to have a release
Social media accounts
TBD
Community size and any existing sponsorship
IBM Internal
Slack - Galasa currently has 86 users on #galasa-users and 69 users on #galasa
External
Slack - 174 current members (excluding bots)
At least 21 individual companies represented within the community
10,000 messages sent over the past 30 days