theAutomation 

Core abstractions for the Precept test automation framework: test attributes, the ambient test context, settings, outcome exceptions and the assertion engine.

dotnet new templates for Precept Web test projects with and without Reqnroll.

Precept's test runner: a Microsoft.Testing.Platform test framework that owns discovery, filtering, parallel scheduling, retries, lifecycle hooks and reporting for Precept tests. A test project starts here.

Optional Gherkin authoring for Precept: compiles Reqnroll feature files into Precept test classes and runs them on the Precept test runner.

Test data management for Precept: environment-specific data sets for users, clients, vehicles and anything else a suite needs, dynamic value generation, factories that create and clean up data in the system... More information

Database testing for Precept. Provider-agnostic: works with any ADO.NET provider (SQL Server, PostgreSQL, MySQL, SQLite) supplied by the test project.

HTTP API testing for Precept: a fluent request builder, response assertions, and automatic request/response logging into the test report.

Browser automation for Precept, built on Playwright: per-test isolation and automatic screenshot, trace and video capture on failure.

Docker-backed dependencies for Precept runs, via Testcontainers: start a service for the run, hand its address to the tests, and tear it down afterwards.

gRPC testing for Precept: pooled channels, typed clients, and assertions over status codes, deadlines and streaming responses.

MCP server for Precept test projects: diagnoses the configuration faults that do not report themselves, and explains environment resolution, parallelism, filters and test data to a coding agent.

ReportPortal reporting for Precept: a launch per run, a suite per class, a test item per scenario, with logs and artifacts attached.

Azure DevOps reporting for Precept: a test run per suite execution, with results filed against the Test Case work items the scenarios are tagged with.

Microsoft Teams reporting for Precept: one Adaptive Card per run, posted to an incoming webhook, listing what failed.

The screenplay pattern for Precept: actors, abilities, interactions and questions, with the browser bindings that carry them out through Playwright.

Excel, CSV, JSON and XML files for Precept tests: workbooks and CSV files written from a data table or a query result, rows appended to what the system under test already has, files read back as rows, JSON and... More information