If you find any problems whilst you’re using Galasa, get in touch and get the help you need:

• Search our project management repository on GitHub; perhaps someone has already had a similar issue and solved it.

• If you have an error message or java stack trace exception, feel free to raise an issue in the project management repository and the Galasa community will get back to you as soon as possible.

• Post a question in our Galasa Slack workspace. Register to join first if you're not yet a member. We have the following available Slack channels:

  • #galasa-dev - for developers of Galasa code or Galasa extensions
  • #galasa-users - for users comments, and for making announcements
  • #galasa-tsc - for technical steering committee discussions on longer term over-arching issues relating to Galasa

If your issue requires a code change, the community will do their best to respond and fix the problem as soon as they can. Depending on the severity of the issue, the fix might be scheduled for a future release of Galasa. Alternatively, the fix might be back ported to the current release. Naturally this is always a community decision and your input is just as important.

If you want to have a go at fixing the defect yourself, let us know and we will help you to try and fix the issue.

We are open to suggestions about more formal support, come and talk to us - we would love to hear from you.