Skip to content

test: example smoke test suite#67

Merged
rian-be merged 1 commit into
mainfrom
docfx-ui
Jul 2, 2026
Merged

test: example smoke test suite#67
rian-be merged 1 commit into
mainfrom
docfx-ui

Conversation

@rian-be

@rian-be rian-be commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR adds a dedicated repository smoke test layer for the executable examples under Examples/Core and Examples/Governance, so the shipped samples are built and exercised as part of a focused validation pass.

Highlights

Example smoke test project

  • Add a dedicated Tests/ModularityKit.Mutator.Examples.SmokeTests project instead of folding sample checks into the existing unit test suites.
  • Add readable smoke coverage for the main example groups under Examples/Core and Examples/Governance.
  • Keep the suite organized into Examples/Core, Examples/Governance, and Support so the coverage maps cleanly back to the sample projects.

Runner behavior and failure reporting

  • Execute example entry points through a shared smoke runner that builds the target project and runs the compiled assembly in isolation.
  • Capture stdout and stderr and surface them in test failures so broken samples are easy to identify.
  • Keep validation lightweight and focused on example viability rather than duplicating detailed scenario assertions from the main test suites.

Environment handling and sample-specific coverage

  • Keep the Redis-specific environment override scoped to the RedisQueries smoke case instead of the generic runner.
  • Accept the documented Redis fallback path when Redis is unavailable locally, while still validating the normal governed query entry point shape.
  • Add XML docs and a local README for the smoke layer so the project is easier to extend when new examples are added.

Why

Issue #53 is about keeping the executable examples trustworthy as documentation. The repository already ships a broad set of examples that represent intended public usage, but those samples can drift from the current API and runtime behavior if they are only exercised manually or incidentally during larger solution builds.

This PR adds a focused smoke layer that validates the sample entry points directly while keeping the coverage separate from the normal unit and governance test suites.

Checks

  • dotnet build Tests/ModularityKit.Mutator.Examples.SmokeTests/ModularityKit.Mutator.Examples.SmokeTests.csproj -c Debug
  • dotnet test Tests/ModularityKit.Mutator.Examples.SmokeTests/ModularityKit.Mutator.Examples.SmokeTests.csproj -c Debug --no-build

Closes

@github-actions github-actions Bot added the tests Test coverage and test changes label Jul 2, 2026
@rian-be rian-be changed the title [codex] Add example smoke test suite test: example smoke test suite Jul 2, 2026
@rian-be rian-be marked this pull request as ready for review July 2, 2026 20:07
@rian-be rian-be merged commit 9b5d604 into main Jul 2, 2026
29 of 30 checks passed
@rian-be rian-be deleted the docfx-ui branch July 2, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests Test coverage and test changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Task]: Add repository smoke tests for example scenarios

1 participant