How gematik/poc-vsdm2 works
Project type and purpose
• This is a Java‑based Maven project that demonstrates a VSDM 2.0 mock server embedded in a test suite.
• It uses the Tiger testing framework to spin up a “Zion” mock HTTP server, run a Cucumber feature (readVSD.feature), and verify responses.
File structure
Top‐level elements:
• pom.xml → Maven build and test orchestrator
• tiger.yaml → Tiger environment definition (which servers to start, config mount points)
• vsdmUsers.yaml, vsdmAnswer.xml, poppTokenTemplate.json, ports.yaml → configuration & data files
• src/test/resources/features/readVSD.feature → Cucumber test definitions
• src/test/resources/*.p12 → key stores for token signing/verification
• src/ → (empty or placeholder for code; all logic lives in test suite and Tiger)
README insights
• Tiger reads tiger.yaml, starts the Zion server, mounts additional YAMLs under a virtual data tree.
• Tests use “TGR” commands to set variables, inject headers, call the server, and assert XML responses.
• Zion server matches incoming requests against configured requestCriterions, performs assignments (using RbelPath formulas), and returns templated XML responses seeded from vsdmAnswer.xml + vsdmUsers.yaml.
Main components
a) Developer Machine / CI
– Maven build & test runner
– Java 17 environment
b) Tiger Test Framework
– Parses tiger.yaml
– Orchestrates lifecycle (start/stop environment)
c) Zion Mock Server
– HTTP interface
– Request matching engine
– Assignment engine (RbelPath)
– Response templating engine
d) Configuration & Data Stores
– tiger.yaml (environment + server definitions + mounts)
– vsdmUsers.yaml (user data)
– vsdmAnswer.xml (response template)
– poppTokenTemplate.json (JWT template)
– P12 key stores for signing/verifying tokens
e) Test Suite
– Cucumber feature file (readVSD.feature)
– Step‐definitions invoking TGR commands
f) Reporting
– Serenity reports under target/site/serenity
Relationships & data flows
1) Developer/CI “mvn clean install” → Maven plugin
2) Maven → Tiger Test Framework starts
3) Tiger reads tiger.yaml → launches Zion server (on configured port)
4) Tiger mounts vsdmUsers.yaml under in‐memory data context
5) Test suite executes Cucumber steps:
• TGR set variable
• TGR inject header (reads poppTokenTemplate.json, P12 key store)
• HTTP GET → Zion server endpoint
6) Zion server on request:
• Match against requestCriterions
• Perform assignments (extract JWT body field via RbelPath to insurantId)
• Load vsdmAnswer.xml, substitute placeholders from vsdmUsers.yaml
• Return XML response
7) Test suite asserts expected response fields
8) Tiger stops environment → Serenity report generated
Architectural patterns & principles
• Mock‐server pattern (Zion) for POC/stub interactions
• Configuration‐driven design (all behavior defined in YAML/JSON/XML files)
• Data‐driven testing (Cucumber + external templates)
• Layered separation: orchestration (Tiger) vs. HTTP mock engine vs. data templates vs. test logic