[keycloak-dev] mechanisms to deploy/install for testing

[Stian Thorgersen]

I don't think our testsuite will be very useful to your QE team as it's
very Java heavy.

I'd recommend creating a realm import file to make it easy to bulk
configure RH-SSO/Keycloak at startup. See [1] for example. Then it's just a
matter of getting a Keycloak server up and running and adding
"-Dkeycloak.import=<path to realm json file>" to startup command. Use RPMs,
Docker or an Ansible playbook to unzip the zips, whatever is easier for
you. I'd use Docker if it was up to me.

[1]
https://github.com/keycloak/keycloak/blob/master/testsuite/integration-arquillian/tests/base/src/test/resources/testrealm.json

On 3 October 2017 at 17:29, John Dennis <jdennis at redhat.com> wrote:

> We utilize RH-SSO/Keycloak as the authentication component in many of
> our products. When our QE team does testing the automated testing needs
> to install and configure RH-SSO/Keycloak. At the moment the QE team is
> bypassing automation and is installing and configuring RH-SSO/Keycloak
> manually because they lack an automated process.
>
> I was asked to inquire how the keycloak team does their automated
> testing with the hope your tools can be utilized so we don't have to
> build something from scratch.
>
> To put things in context this is for the platform group which does not
> traditionally deal with middleware and the Java ecosystem. Software
> installation is exclusively done with RPM's. Preferred methods are:
>
> 1) Ansible playbooks
> 2) Puppet manifests
> 3) Shell scripts
>
> Can you describe how your testing is performed and/or point us to
> documentation and/or repositories with the tools.
>
> Thanks,
> --
> John
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>