Skip to content

docs: expect_fail instead of explicit_fail - #89

Merged
choppsv1 merged 1 commit into
LabNConsulting:mainfrom
liambrady:working/docs_typo_expectfail
Jan 2, 2026
Merged

choppsv1 merged 1 commit into
LabNConsulting:mainfrom
liambrady:working/docs_typo_expectfail

Conversation

@liambrady

Copy link
Copy Markdown
Contributor

The wrong argument is explained in the mutest example docs. explicit_fail does not exists and should instead be expect_fail.

The wrong argument is explained in the mutest example docs.
`explicit_fail` does not exists, and should instead be `expect_fail`.

Signed-off-by: Liam Brady <lbrady@labn.net>
@liambrady
liambrady requested a review from choppsv1 December 1, 2025 20:19
@liambrady liambrady added the documentation Improvements or additions to documentation label Dec 1, 2025
@codecov

codecov Bot commented Dec 1, 2025 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.19%. Comparing base (5ef25cf) to head (4ba48f3).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   59.19%   59.19%           
=======================================
  Files          19       19           
  Lines        5833     5833           
=======================================
  Hits         3453     3453           
  Misses       2380     2380           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@choppsv1
choppsv1 merged commit 1cded5a into LabNConsulting:main Jan 2, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants