Skip to content

QaaS Mocker

QaaS.Mocker is the mock-server runtime in the QaaS ecosystem. It runs HTTP, gRPC, and socket mocks from YAML or from code, routes incoming traffic to named Stubs, and lets each stub shape its response through reusable or project-local Processors.
Runtime .NET 10
Package QaaS.Mocker (NuGet)
Source QaaS.Mocker
Docker Multi-stage Dockerfile included

Key Capabilities

  • Protocol coverage - host HTTP, gRPC, TCP, and UDP mocks from one process.
  • Composable responses - map endpoints to named Stubs, then let Processors turn request data and optional DataSources into responses.
  • Data-backed stubs - preload files or generated data in DataSources and reuse them across multiple endpoints and actions.
  • Runtime control - use the optional Controller to switch stubs or drive runtime state externally during QaaS.Runner flows.
  • Plugin model - load QaaS.Common.Processors and QaaS.Common.Generators from the project itself, local assemblies, or NuGet packages.
  • YAML and code parity - keep the mock definition in mocker.qaas.yaml, build it fluently in C#, or combine both through Configuration as Code.

See Architecture for the runtime layout.