Test File Format
ConfIT test definitions live in .json or .yaml files — no C# required. Each file is a map of test name → test case. Tests run in the order they appear in the file.
Mock Interactions
Component tests run the service under test in-process, but real services still call external dependencies. Without a way to stand in for those dependencies, the test would fail the moment it hits a live HTTP call. Mock interactions let you declare what those outbound calls look like and what each one should return — all inside the test definition file, without writing a line of C#.
GraphQL Support
A graphql block lets a test send a GraphQL query or mutation without hand-building the request envelope. Declare the query and variables; ConfIT composes the { query, variables, operationName } JSON body, sets the HTTP method, and sets Content-Type — the same request pipeline (matchers, extract, {}, mocking) applies afterward exactly as it does for any other test.
Test Filtering
By default every test in a suite runs. Filtering lets you run a targeted subset without changing the test files — useful for smoke pipelines, debugging a single failing test, or separating fast and slow groups.