QaaS.Mocker.Stubs 2.2.0

QaaS.Mocker

Configurable mock runtime for QaaS protocol workloads.

Contents

• Overview
• Packages
• Functionalities
• Protocol Support
• Quick Start
• Run the Example
• Runner Integration Overlay
• Build and Test
• Documentation

Overview

This repository contains one solution: QaaS.Mocker.sln.

QaaS.Mocker is published as a single NuGet package and composes internal runtime modules for stubs, protocol servers, and optional Redis controller operations.

Packages

Package	Latest Version	Total Downloads
QaaS.Mocker

Functionalities

QaaS.Mocker

• Parses CLI options and loads YAML configuration with overwrite files/arguments and optional environment resolution.
• Builds and validates execution context, data sources, stubs, one or more server runtimes, and optional controller runtime.
• Supports execution modes: Run and Template.

QaaS.Mocker.Stubs

• Builds transaction stubs from configured processors and data source bindings.
• Executes request/response transformation through configurable serializer/deserializer pairs.
• Includes default status-code stubs for not-found and internal-error flows.

QaaS.Mocker.Servers

• Hosts protocol runtimes for HTTP/HTTPS, gRPC/gRPCs, and Socket.
• Routes actions/RPC methods to transaction stubs through state objects.
• Caches input/output payloads for controller consume operations.

QaaS.Mocker.Controller

• Initializes optional Redis-backed runtime controller when configured.
• Handles Ping and Command channels.
• Supports runtime commands such as action-to-stub switch, trigger, and consume.

QaaS.Mocker.Example

• Provides runnable multi-server and transport-specific mocker configurations, sample processors, protobuf schema, and sample data assets.

Protocol Support

Supported protocol/runtime families in QaaS.Mocker:

Quick Start

Install package:

dotnet add package QaaS.Mocker

Upgrade package:

dotnet add package QaaS.Mocker --version <target-version>
dotnet restore

Run the Example

The example uses relative paths for certificates, sample data, and socket payloads, so run it from QaaS.Mocker.Example. The example entry point also disables environment-variable overrides by default so IDE terminal variables do not rewrite the sample configuration.

1. Open a terminal in the example directory.

Set-Location .\QaaS.Mocker.Example

2. Create the development certificate expected by the sample HTTPS and gRPC configs.

dotnet dev-certs https -ep .\Certificates\devcert.pfx -p qaas-dev-cert

3. Start the combined example. It boots HTTPS, gRPC with TLS, and a TCP socket collect endpoint from the same process.

dotnet run -- run mocker.qaas.yaml

4. In a second terminal, call the HTTPS health endpoint.

curl.exe -k https://127.0.0.1:8443/health

5. Call the gRPC endpoint from Git Bash, WSL, or another POSIX-style shell if you have grpcurl installed.

grpcurl -insecure -import-path Protos -proto echo.proto -d '{"message":"hello"}' 127.0.0.1:50051 qaas.mocker.example.EchoService/Echo

6. Send a payload to the socket collect endpoint. The socket endpoint does not reply; success is a clean connect and write plus a collect log entry in the server terminal.

$client = [System.Net.Sockets.TcpClient]::new()
$client.Connect('127.0.0.1', 7001)
$stream = $client.GetStream()
$payload = [System.Text.Encoding]::UTF8.GetBytes('socket-check')
$stream.Write($payload, 0, $payload.Length)
$stream.Flush()
$stream.Dispose()
$client.Dispose()

7. Generate the effective combined configuration with the template command.

dotnet run -- template mocker.qaas.yaml

8. If you still want the dedicated gRPC-only sample, it remains available.

dotnet run -- run mocker.grpc.qaas.yaml

Runner Integration Overlay

The example now includes mocker.runner.qaas.yaml, an overwrite file that appends only the runner-integration pieces missing from mocker.qaas.yaml:

• Redis controller configuration for runner mocker commands
• Alternate stubs for ChangeActionStub checks on HTTP, gRPC, and socket
• A socket broadcast endpoint on port 6000 for TriggerAction

The overlay uses explicit numeric indexes for list sections so it can be appended with --overwrite-files without editing the base sample.

Use it together with the base file instead of editing the base sample:

1. Start local Redis:

docker run -d --name qaas-redis -p 6379:6379 redis:7-alpine

2. Ensure the sample certificate exists:

Set-Location .\QaaS.Mocker.Example
dotnet dev-certs https -ep .\Certificates\devcert.pfx -p qaas-dev-cert

3. Run the sample plus the overlay:

dotnet run -- run mocker.qaas.yaml --overwrite-files mocker.runner.qaas.yaml

The combined runtime exposes:

• HTTPS health endpoint on https://127.0.0.1:8443/health
• TLS gRPC endpoint on 127.0.0.1:50051
• TCP socket collect endpoint on 127.0.0.1:7001
• TCP socket broadcast endpoint on 127.0.0.1:6000
• Redis controller under server name RunnerMockerExample

The broadcast endpoint is disabled by default and becomes active only when the runner sends TriggerAction for SocketBroadcastAction.

Build and Test

dotnet restore QaaS.Mocker.sln
dotnet build QaaS.Mocker.sln -c Release --no-restore
dotnet test QaaS.Mocker.sln -c Release --no-build

Documentation

• Official docs: thesmoketeam.github.io/qaas-docs
• CI workflow: .github/workflows/ci.yml
• NuGet package: QaaS.Mocker on NuGet