Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve assertion reports using "produced" message sets. #66

Open
jmalloc opened this issue Jan 8, 2020 · 0 comments
Open

Improve assertion reports using "produced" message sets. #66

jmalloc opened this issue Jan 8, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@jmalloc
Copy link
Member

jmalloc commented Jan 8, 2020

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 engaged
  • no 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant