QaaS Documentation

QaaS (QA As A Service) is a .NET 10 ecosystem for integration and end-to-end testing of backend applications. Define tests in YAML, extend behavior with C# hooks, and validate results with minimal boilerplate.

Quick Navigation

• Runner

  ---

  The QaaS.Runner test orchestrator. Manages Sessions, DataSources, Policies, Storages, and Assertions via YAML or code.

  Runner Docs

• Mocker

  ---

  Spin up QaaS.Mocker HTTP, gRPC, or socket mock servers with configurable Stubs, Servers, and runtime Controller support via Redis.

  Mocker Docs

• Hooks

  ---

  Reusable QaaS.Common.Assertions, QaaS.Common.Generators, QaaS.Common.Probes, and QaaS.Common.Processors. Plug them into any test.

  Hooks Reference

• Framework

  ---

  The shared QaaS.Framework foundation that QaaS.Runner, QaaS.Mocker, and custom hooks build on: SDK types, configuration loading, protocol abstractions, serialization, Policies, and DI providers.

  Framework Docs

Zero-to-Hero Path

Phase	#	Guide	Description
Setup	1	Installation	Install .NET 10, configure NuGet feeds, scaffold a project
	2	IDE Setup	Enable YAML auto-complete and validation in VS Code or Rider
Build	3	Write a Test (YAML)	Write a minimal YAML test, define DataSources, Sessions, and Assertions
	4	Write a Test (Code)	Same test using C# builders instead
	5	Write Custom Hooks	Create your own QaaS.Common.Generators, QaaS.Common.Assertions, QaaS.Common.Probes, and QaaS.Common.Processors
Run & Debug	6	Run a Test	Execute tests and view results in the Allure Report
	7	Debug Failures	Split act/assert, inspect session data, diagnose issues
Master	8	Maintainable Tests	Improve structure by using anchors, placeholders, and variable files
	9	Architecture	Understand the Runner pipeline and design complex scenarios

Contact Us

Join our community where you can ask questions, report bugs, request features, and interact with the community.

Click Here to join the QaaS Community.