QaaS.Runner.Sessions 4.8.2

QaaS.Runner

Execution orchestration package for running QaaS test workflows from YAML configuration.

Contents

• Overview
• Packages
• Projects
• Quick Start
• ReportPortal
• Documentation

Overview

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

QaaS.Runner is published to NuGet and includes the runner runtime plus packaged project outputs from this solution that are required at runtime (sessions/assertions/storage orchestration flow).

Packages

Package	Latest Version	Total Downloads
QaaS.Runner

Projects

QaaS.Runner

• CLI/bootstrap entrypoint for run, act, assert, template, and execute verbs.
• Builds execution contexts and routes each execution type through the right logic chain.
• Orchestrates setup/teardown, optional Allure result serving, ReportPortal access validation, and final ReportPortal publishing.

QaaS.Runner.Assertions

• Builds assertion runtime objects from configured hooks and filters.
• Executes assertions against session/data-source outputs.
• Writes Allure results, links, and attachments.
• Can also publish the same runner-produced assertion results into ReportPortal.

QaaS.Runner.Sessions

• Session runtime with staged action execution.
• Supports publishers, consumers, transactions, probes, and collectors.
• Produces session data and failure/flakiness metadata.

QaaS.Runner.Storage

• Storage abstraction for storing and retrieving serialized session data.
• Built-in implementations: filesystem and S3-compatible backends.
• Shared builder-based configuration for act/assert flows.

QaaS.Runner.Infrastructure

• Small shared cross-project helpers (filesystem and date/time utilities).

Quick Start

Install package:

dotnet add package QaaS.Runner

Upgrade package:

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

ReportPortal

QaaS can send its assertion results to an existing ReportPortal instance. Configure Reporters.ReportPortal with Enabled, Endpoint, ApiKey, and an optional Project (defaults to MetaData.Team). YAML values override package defaults.

• QaaS does not create ReportPortal projects or credentials; the target project and API key must already exist.
• Only run and assert use ReportPortal. template still renders its configuration, while template and act perform no validation or publishing.
• Immediately before the first ReportPortal-enabled run or assert, the runner validates every enabled launch group with a read-only project lookup. If validation fails, it returns exit code 1 and skips that command and everything after it; earlier commands remain completed.
• Assertion results are queued locally and published during cleanup. Compatible ReportPortal configurations share a launch.
• Final publishing errors are logged without changing the execution-derived exit code. Allure output is unaffected.

Documentation

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