catchorg / catchorg/Catch2

CHECK fails test

Open
#1,446 5 comments 0 reactions 0 assignees View on GitHub
Query
Dominant language
C++
Stars
21.5k
Forks
3.5k
Avg merge
3d 16h
Merged PRs (30d)
2

Description

Perhaps I am missing something here. I thought that if no ``REQUIRE`` failed, any ``CHECK`` that occurred one way or another was basically transparent. Conversely, if a ``REQUIRE`` failed involving a ``CHECK``, then those ``CHECK`` instances would indeed report as such. What I am looking for is sort of like ``CHECK``, if it exists, but weaker than that. In other words, great, it reports, but does not otherwise influence the outcome of the test. Perhaps I am misunderstanding the nature of ``CHECK``. Thanks!

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by reading Catch2's existing CHECK and REQUIRE assertion behavior and related documentation or tests, then clarify the proposed weaker reporting-only assertion; done means its failure is reported without affecting the test outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.