llnl / llnl/smith

Tests are expected to fail should be very explicit

Open
#526 0 comments 0 reactions 0 assignees View on GitHub
CS quick testing
Dominant language
C++
Stars
245
Forks
36
Avg merge
8d 23h
Merged PRs (30d)
4

Description

I was trying to track down a problem and spent entirely too long looking into a test that was expected to fail. Obviously by looking at the source of the test its clear but it would be helpful if failing tests are in their own test that explicity says in the name it should error, something like `test_for_input_failure`.

Contributor guide

Open the contributing guide

Research direction

No file or test path is named. Start by locating tests that intentionally expect failure and review how the test suite currently identifies them. Done means expected-failure tests are clearly named or separated so their purpose is obvious when a test fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.