TIger
Agiles Testen in der Telematik-Infrastruktur
Agiles Testen in der Telematik-Infrastruktur
The local tiger proxy is instantiated automatically on startup of your test suite given you have included the
Tiger BDD hooks.
The Java proxy system properties
If you have those system properties already set, Tiger will not overwrite them!
Please note that all nodes will be available to your test suite via their configured hostname. You don't need to configure them here.
Advanced settings are hidden per default and can be revealed by clicking on the toolbox icon
Wählen Sie zunächst einen Servertyp oder eine Testvorlage aus. Sie können Ihrem Projekt später weitere Typen und Vorlagen hinzufügen.
Please select one of the basic server types from the left list or choose a more sophisticated server node from the list of templates at the bottom of the left list. by clicking on it a more detailed description to each type/template will be shown. To add it press the button on the bottom right.
With the base type "Docker" you can specify a docker image from a remote docker registry. Tiger will download the image and start a local container on your machine.
Example use case: run some tests agains a server in a docker container.
Exposed ports will be available with the expression ${PORT:localport} in the Exports list. ${NAME} will be replaced with the hostname.
With the base type "external Jar" you can specify a local jar file to be executed on your machine (with customizable options and program arguments). In most cases the jar will start a server. The local test suite proxy will then route traffic from the given hostname for this node to the external Jar (reverse proxy mode). The healthcheck attribute will determine the servers access URL (= the destination address for the test suite proxy). This way your test suite needs to know nothing about the external address and can switch between different servers without any changes in its configuration.
Example use case: locally run some tests agains the server you are developing (your server = "the external jar")
${NAME} will be replaced with the hostname in the Exports list.
With the base type "Tiger proxy" you can add an additional forward or reverse proxy to your test environment. These proxies will not be available to the test suite or nodes out of the box but must be configured on the nodes.
Example use case: configure additional forward proxies for nodes in your environment or to facade nodes via a reverse proxy.
With the base type "external URL" you can specify an external internet address where a service is hosted. The local test suite proxy will then route traffic from the given hostname for this node to the external URL (reverse proxy mode). This way your test suite needs to know nothing about the external address and can switch between different servers without any changes in its configuration.
Example use case: run some tests agains a server that someone else is hosting (server address = "the external URL")
${NAME} will be replaced with the hostname in the Exports list.
With the base type "Docker Compose" you can specify one or more docker compose scripts and the test environment manager will set up all services locally.
Example use case: run some tests agains a group of servers in a docker composition.
Exposed ports will be available with the expression ${PORT:localport} in the Exports list. ${NAME} will be replaced with the hostname.
This template provides the reference implementation of the IDP server as local docker container. The docker image is loaded from a gematik internal docker registry server.
The system property IDP_SERVER is set to the URL of the Discovery Document end point and is available for all subsequently initiated test environment nodes.
This template provides a route to the RISE IDP in the Gematik RU
The system property IDP_SERVER is set to the URL of the Discovery Document end point and is available for all subsequently initiated test environment nodes.
This template provides a route to the RISE IDP in the Gematik TU
The system property IDP_SERVER is set to the URL of the Discovery Document end point and is available for all subsequently initiated test environment nodes.