Skip to content

If a messages could not be matched than the test should output failed counter #18

Open
ehmkah opened this issue Oct 22, 2020 · 1 comment

Comments

@ehmkah
Copy link
Contributor

ehmkah commented Oct 22, 2020

If I see the following before the tests finishes
waiting: 0 / active: 10 / done: 230

Than the test result looks like

---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                           230 (100%)
> 800 ms < t < 1200 ms                                   0 (  0%)
> t > 1200 ms                                            0 (  0%)
> failed                                                 0 (  0%)

But it should look like (and reflect that some messages have not been processed)

---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                           230 (96%)
> 800 ms < t < 1200 ms                                   0 (  0%)
> t > 1200 ms                                            0 (  0%)
> failed                                                 10 ( 4%)
@ehmkah ehmkah changed the title If a message could not be matched than it should fail If a messages could not be matched than the test should output failed counter Oct 22, 2020
@ehmkah
Copy link
Contributor Author

ehmkah commented Oct 22, 2020

Problem occurs if timeout for messages has not been reached when test finishes.

One workaround is: set replyTimeout to lower value so it can timeout before test fininsh.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant