Repository navigation
Add mutation testing infrastructure and quality metrics - #1209
Merged
Kingsman-99 merged 5 commits intoOct 21, 2026
Merged
Conversation
|
@code-vortexIII Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add mutation testing infrastructure and quality metrics
What was solved
#1192 — Add mutation testing for test quality
Add mutation testing infrastructure to verify test effectiveness: select a mutation testing tool (e.g., Stryker for TypeScript), configure it against the existing Jest test suite, add mutation scoring thresholds, reporting, and result analysis/quality metrics. This is primarily tooling/config work plus a CI workflow and npm scripts, without altering production source or existing tests.
Addressed:
#1193 — Implement contract testing for API compatibility
Add a contract-testing layer to the SDK so API compatibility is enforced: define consumer contracts against the public API surface, verify the provider (SDK) against those contracts, verify consumers, publish contracts, and maintain a compatibility matrix. Implement as a focused test/framework module plus a contract definition file and a CI workflow, staying within the existing test conventions under src/tests and .github/workflows.
Addressed:
#1194 — Add SDK documentation testing
Add a documentation testing capability for the SDK: extract code examples from docs/examples, run them, validate results, report failures, and track versions. This is a new tooling/test harness rather than a change to SDK runtime code, so the contribution should add a focused doc-testing script (and possibly a small test) that extracts snippets, executes them, validates output, and reports failures with version tracking.
Addressed:
#1195 — Implement SDK regression test suite
Add an SDK regression test suite covering test case design, automation, baseline management, comparison logic, reporting, and trend analysis. Implement as a focused test module plus supporting baseline/comparison utilities, following existing test patterns under src/tests and scripts conventions.
Addressed:
Changes
src/__tests__/sdkFeatures.test.ts(modify)examples/README.md(modify)package.json(modify).gitignore(modify)src/__tests__/ammCalculator.test.ts(modify).github/workflows/integration-test.yml(modify)scripts/generate-docs.ts(modify)scripts/bundle-size-baseline.json(modify)Approach
Issues
Closes #1192
Closes #1193
Closes #1194
Closes #1195