Test failure masks following failures
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by inspecting the example commit 3c38cc6b6290225bb0bf74588038f76ef9c1eae8 and tracing how the Unity test runner records a failure before executing later tests. Done means a failing test no longer causes subsequent tests to appear to pass, and the relevant test behavior is covered by a regression test.
Written by the indexing model from the issue text.
Description
One failing test can make following tests appear to pass. An example of this can be found here:
https://github.com/c1728p9/mbed-os/commit/3c38cc6b6290225bb0bf74588038f76ef9c1eae8
@PrzemekWirkus, @bridadan
- Dominant language
- C
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
libsdl-org/SDL#16372 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
corazawaf/coraza-nginx#140 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
jamesstringer90/appsandbox#160 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100