Recover from dogma.UnexpectedMessage panics during tests.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
As per https://github.com/dogmatiq/testkit/issues/8#issuecomment-509860634, this leads to some pretty indecipherable output, as it's not obvious which message or handler was involved.
Such a panic should be used to produce meaningful test suggestions, just as is done for failed assertions.
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 examining how the testkit handles failed assertions and where dogma.UnexpectedMessage panics escape during tests. Compare the panic path with the existing assertion path, then verify that the resulting suggestions identify the relevant message or handler without producing indecipherable output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100