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

Make the result objects usable in the new formatter api #88

Merged
merged 2 commits into from May 4, 2015

Conversation

brasmusson
Copy link
Contributor

To make the result objects usable in the new formatter api:

  • Set the message on undefined results.
  • Append the backtrace with the backtrace line of the step on results that either have an exception (with backtrace) or have a backtrace themselves.
  • Support applying filters on the backtrace.

Required by cucumber/common#843.

Set the message on undefined results and append the backtrace with
the backtrace line of the step on results that either have an
exception (with backtrace) or have a backtrace themselves. Support
applying filters on the backtrace.
Somehow a scenario in a wire feature file in Cucumber failed with a
timeout error when copying the object and its backtrace.
@brasmusson
Copy link
Contributor Author

This deep copying of the backtrace resulted in a timeout error in one of the wire scenario of Cucumber, so a resorted to modify the backtrace in place (instead of treating the result object as immutable).

mattwynne added a commit that referenced this pull request May 4, 2015
Make the result objects usable in the new formatter api
@mattwynne mattwynne merged commit c72a6db into master May 4, 2015
@brasmusson brasmusson deleted the result-new-api-usable branch May 4, 2015 15:37
@lock
Copy link

lock bot commented Oct 24, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants