So you heard there is a new tool in the house? But what is tiger for?

Take a look at our short pitch video explaining the basic idea of Tiger

• Internal test teams that want to perform iop or e2e tests for reference or product implementation.

• Internal test teams that want to perform acceptance tests for reference or product implementation.

Within the test teams we focus on testers, with not necessarily too much programming skills. It must be easy to set up and implement tests against service nodes, potentially reusing test steps from other test suites. For non BDD test suites it must be easily possible to utilize most of the features of Tiger by directly calling public interface methods.

• External product teams, which need to do automated IOP/E2E testing for their health applications.

Every information at one place: check out our Tiger-User-Manual!

• HTML: Tiger-User-Manual

• PDF: Tiger-User-Manual

For more details please check out more Plantuml diagrammes at specification folder

For a standalone example see here in our examples section

The package "de.gematik.test.tiger.mockserver" of the module tiger-proxy is based upon mockserver (https://github.com/mock-server/mockserver), licensed under Apache License 2.0 (January 2004).

Files under the tiger-proxy/src/main/resources/css and webfonts folders were taken from the projects with listed licenses:

• bulma css MIT
• bulma swatch css MIT
• Font Awesome by Dave Gandy - Website License (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)