-
-
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
Different location objects in json report. #945
Comments
I'm having a very similar issue in my "Before" hook:
Is this expected behavior? It seems to break the jenkins cucumber reporting plugin because it expects ruby 2.2 EDIT: As far as I can see, this actually happens in every one of our steps (and |
The expected behaviour is documented in this spec. Why the json_spec-1.1.4 and capybara-2.6.2 hooks respond differently to |
@brasmusson I've been looking into it, and it looks like the problem occurs when MultiJson.dump is called on the match location. I'm assuming this has to do with the JSON implementation being used... I'll let you know if I come up with anything else. |
This commit on my fork fixes this issue for me. Although it's not quite the low-level fix I was hoping to find, all the tests still pass and I'm not sure there are any other repercussions to stringifying the object immediately. I'll likely make a PR after I've run some more verification. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When i use after step from another gem,
location element of after step in json report is different then in other steps
I would expect it to be:
full json:
cucumber-ruby 1.4.3
selenium-cucumber 2.1.4
cucumber 2.3.2
The text was updated successfully, but these errors were encountered: