Detect "impossible" expectations before running the application.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
When a dispatchAction is used in combination with a message[Type]Expectation we can use the application configuration to check if the test could ever pass without executing any code.
This should eliminate a bunch of branches within the expectation reporting and help catch configuration errors or copy/pasted tests more quickly.
Contributor guide
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 tracing dispatchAction, message[Type]Expectation, and the expectation-reporting paths, then inspect how application configuration is exposed to them. Define the impossible-expectation cases from that configuration and confirm that they are detected before application code runs, with existing expectation behavior preserved for valid cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100