I see that cucumber-core team has implemented output formatter for IntelliJ IDEA. Thank you. Now JetBrains doesn't need to ship output formatter for every Cucumber-Java version.
🤔 What's the problem you're trying to solve?
Unfortunatelly built-in formatter (TeamCityPlugin) doesn't provide "expected" and "actual" attributes in cause of failed condition. That's why diff toolwindow is unavailable for cucumber tests.
✨ What's your proposed solution?
It's necessary to add the "expected" and the "actual" attributes to the ##teamcity[testFailed message.
⛏ Have you considered any alternatives or workarounds?
We could ship a new version of output formatter for Cucumber-Java v.7. But I believe it's much better when the TeamCityPlugin built in cucumber-core.
I see that cucumber-core team has implemented output formatter for IntelliJ IDEA. Thank you. Now JetBrains doesn't need to ship output formatter for every Cucumber-Java version.
🤔 What's the problem you're trying to solve?
Unfortunatelly built-in formatter (TeamCityPlugin) doesn't provide "expected" and "actual" attributes in cause of failed condition. That's why diff toolwindow is unavailable for cucumber tests.
✨ What's your proposed solution?
It's necessary to add the "expected" and the "actual" attributes to the
##teamcity[testFailed
message.⛏ Have you considered any alternatives or workarounds?
We could ship a new version of output formatter for Cucumber-Java v.7. But I believe it's much better when the TeamCityPlugin built in cucumber-core.
📚 Any additional context?
Issue in IDEA tracker: IDEA-125830
This text was originally generated from a template, then edited by hand. You can modify the template here.