How tricentis/simulation works
This repository is a catalog of Tricentis Simulation configuration examples, not the simulation engine. The documented workflow is to use an example to define a virtual API or service so testing can continue when a dependency is unavailable. The tree also exposes scenario examples and feature demonstrations, plus a JSON schema for YAML editor support. Source excerpts were not provided, so relationships below rely only on README statements; the individual configurations’ runtime behavior is not verified here.
Main entry points: examples Simulation examples · schema.json YAML JSON schema
Components 16
Service scenarios
- Simulation examples
examples - Shopping cart
examples/shoppingCart/simpleState.yml - Car service
examples/carServiceDemo/carService.yml - Data-driven service
examples/dataDriven/DataDrivenMagic.yaml - Dynamic resource
examples/dynamicResource/dynamic_resource.yml - Payment history
examples/paymentsHistory/TRI-PaymentService.yml - Rate limiting
examples/rateLimiting/rateLimiting.yml
Configuration features
- Feature demonstrations
features - Expressions
features/expressions/try/try.yml - Tree configuration
features/tree/tree.yml - Template use
features/use/use.yml - Variables
features/variables/variables.yml - HTTP configuration
features/http.yml
Authoring support
- YAML JSON schema
schema.json
Other components
- Testers and developers
- Virtual API or service
Connections 3
- Testers and developers → Simulation examples: uses examples
README.md - Simulation examples → Virtual API or service: simulates dependency
README.md - Testers and developers → YAML JSON schema: configures editor
README.md