-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Display error banner when Reports server returns status code ≠ 2xx #1608
Display error banner when Reports server returns status code ≠ 2xx #1608
Conversation
Update scenario to ensure cucumber execution fails if the server returned an error
Seems to work fine now (except for the 'null' line that I have to fix)
|
The build is not really stable (I managed to get it green by relaunching - and after it failed again). Apparently that comes from some tests I have added and the way the stream errors are handled. I'm going to dig a bit more into that (although the solution I have in mind is not that beautiful to be honest :D ) |
@vincent-psarga are the non-deterministic tests new tests in this PR? I can help have a look at this. |
The flaky tests I think started from the original change where publish support was added per #1457 I tried a few things a while ago but hit a bit of a wall tbh. |
At least from what I see, it's the test that I've introduced which is flaky. I'm looking at a way to not spawn Cucumber in order to fix this (worked fine with Ruby getting rid of spawning, so I give a try) |
Get banner displayed as expected
That may fix the inconsistent tests
Two listener on "close" per socket, one destroying it, the other one resolving the promise when stopping the server. But the one destroying it may be responsible to also resolving the promise when stopping the server, so as I understand, it could lead to resolving the same promise twice for a single socket.
Just tried to remove the delays in the server So it seems the combination of the delays, and the ports, stabilized the tests. |
We'll bring it back in a new PR
@vincent-psarga @aslakhellesoy @vincentcapicotto Beside the race condition / inconsistent test, something still need to be done before merging that PR? |
@davidjgoss do you have any new feedback regarding that PR? I plan to open a new PR dedicated to the inconsistent test once that one is merged. |
@aurelien-reeves I'll review this morning, thanks for the nudge! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Other Cucumber implementations display the content send by the server upon failure. For example, with Cucumber ruby:
This is an attempt to get the same behavior in
cucumber-js
TODO:
null
line displayed above the banner