Improve assertion reports using "produced" message sets.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
This assertion logic was written before handlers were required to declare the message types they produce. Now that such information is available, the explanation messages such as:
no relevant handlers (aggregate or integration) were engagedno relevant handlers (process) were engaged
Could be improved by referring to the specific handler that would produce the expected message.
Additionally the suggestions like:
verify the logic within the '<process>' process message handler
Could show a more specific message if the handler is the one that would produce the expected message.
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 locating the assertion logic that emits the listed explanation and suggestion messages, then read how handlers declare the message types they produce. Trace how expected messages are matched to aggregate, integration, and process handlers. Done means reports identify the specific relevant handler and provide a more specific suggestion when that handler produces the expected message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100