You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This functionality should either be moved to a helper module in Cucumber::Formatter or to Cucumber-Ruby-Core. For the new formatter api to be easy to use, it should be possible to get from Cucumber::Core::Test::Result to the exception backtrace used the formatter output without using code in Cucumber::Formatter::LegacyApi. Doing so right now will instead produce the following exception backtrace:
The exception backtrace in the output from formatters is structured as (example from junit_formatter.feature):
To produce this backtrace code in
Cucumber::Formatter::LegacyApi
is used (this code in lib/cucumber/formatter/legacy_api/adapter.rb).This functionality should either be moved to a helper module in
Cucumber::Formatter
or to Cucumber-Ruby-Core. For the new formatter api to be easy to use, it should be possible to get fromCucumber::Core::Test::Result
to the exception backtrace used the formatter output without using code inCucumber::Formatter::LegacyApi
. Doing so right now will instead produce the following exception backtrace:The text was updated successfully, but these errors were encountered: