Support diff view for failed assertEqual condition in Intelij IDEA

[avokin2]

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.

[mpkorstanje]

I'm happy to see that this has your attention! Could you please pick up IDEA-276468 so I can get rid of the workarounds for IDEA:

cucumber-jvm/cucumber-core/src/main/java/io/cucumber/core/options/PluginOption.java

Lines 62 to 72 in ee6b693

	private static final Set<String> INCOMPATIBLE_INTELLIJ_IDEA_PLUGIN_CLASSES;
	static {
	Set<String> incompatible = new HashSet<>();
	incompatible.add("org.jetbrains.plugins.cucumber.java.run.CucumberJvmSMFormatter");
	incompatible.add("org.jetbrains.plugins.cucumber.java.run.CucumberJvm2SMFormatter");
	incompatible.add("org.jetbrains.plugins.cucumber.java.run.CucumberJvm3SMFormatter");
	incompatible.add("org.jetbrains.plugins.cucumber.java.run.CucumberJvm4SMFormatter");
	incompatible.add("org.jetbrains.plugins.cucumber.java.run.CucumberJvm5SMFormatter");
	INCOMPATIBLE_INTELLIJ_IDEA_PLUGIN_CLASSES = unmodifiableSet(incompatible);
	}