markcunninghamuk / markcunninghamuk/FluidTest
Specifications should run all of their validators, regardless of assertion errors
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 20
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The current behaviour is that Specifications will only run until they reach an error. This means all subsequent validators in a specification will not get run, and so the test will not report on further issues.
Specifications should run all of their validations and continue on error so that all assertion errors are reported.
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.
Research direction
Start by locating the Specification validation flow and reproduce the behavior with multiple validators, including an assertion failure in an earlier validator. Done means every validator runs despite assertion errors and the test reports all resulting assertion errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100