-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
StdErr output is after StdOut in step definition the output should contain
#705
Comments
Thanks @archerzz, that is indeed a regression. |
Hi @archerzz I've just tried to reproduce this and it looks like this particular behavior is the same in 0.14.4, 0.14.14 and 1.0.0. In all versions, the combined output contains all of stdout and then all of stderr. Therefore, I think the problem may be more subtle. I know you can't share your project, but can you create a minimal test case that succeeds with 0.14.14 and fails with 1.0.0? |
Hi @mvz, sorry for the late response. My original report is not correct. I doubled checked my daily test logs, and I think this problem should exist in |
the output should contain
the output should contain
No problem. I've changed the title of this issue accordingly. |
Summary
I found that in version
1.0.0
, the contents ofStdOut
andStdErr
do not keep their original sequence in step definitions likethe output should contain
. More specific,StdErr
is afterStdOut
.Version
0.14.x
is fine. So I think this should be a regression.Expected Behavior
The output of
StdErr
andStdOut
should keep their original sequence in step definitions likethe output should contain
.Current Behavior
If the app prints some contents to
StdErr
first, and then toStdOut
, like below:We write the scenario according to the actual output.
However in step definitions like
the output should contain
, it will treat the output like:Thus the comparison will fail.
Possible Solution
Roll back to old versions.
Steps to Reproduce (for bugs)
StdErr
beforeStdOut
1.0.0
0.14.4
Context & Motivation
This will break CLI apps which mix
StdOut
andStdErr
outputs (like put some warning messages between normal output)Your Environment
The text was updated successfully, but these errors were encountered: