New PIT Plugin for IntelliJ

[Brendan McCarthy]

Greetings PIT Users,

Was looking for richer functionality and more stability than I found in the current PIT plugins for IntelliJ, so I built my own. Features:

• Run against any combination of files -- automatically matches sources and tests
• See mutation icons directly in IDE or jump to a browser view
• Sort/filter results, see score breakdown
• View and re-execute previous runs
• Maven and Gradle support

Please have a look if interested, feedback welcome.

Brendan

[Ullrich Hafner]

Thanks for creating a new plugin for IntelliJ. 

When I run it, I get a 

org.junit.platform.commons.JUnitException: TestEngine with ID 'junit-jupiter' failed to discover tests

OutputDirectoryProvider not available; probably due to unaligned versions of the junit-platform-engine and junit-platform-launcher jars on the classpath/module path.

It seems your plugin bundles PIT and JUnit in some incompatible versions compared to the versions in my project.

• Maven and Gradle support

What kind of support do you have for Maven? 

I configured PIT in Maven correctly to avoid such class loading problems, but it seems that such a configuration is not correctly picked up by your plugin…

Is there a way to run the visualization without invoking PIT? I normally invoke static analysis and coverage directly in Maven and want to visualize the generated results in IntelliJ only. Otherwise you need to configure the tools twice one time for maven and one time for IntelliJ.

Ulli

--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pitusers/abededf8-bee5-4dd9-90c7-177e19bb1dd3n%40googlegroups.com.

[Brendan McCarthy]

Ulli,

I presume your using JUnit 5.12.2 and it only works up to 5.11.2. I will put out a fix for this sometime this week and let you when it's ready.

Thanks for posting,

Brendan

[Brendan McCarthy]

Fixes in for latest JUnit in latest release 0.2.1, please let me know if it works for you or otherwise. In the latest release I've also added:
  * The ability to view the classpath used for PIT which highlights any elements that the plugin added
  * The ability to completely configure that classpath on your own, overriding any classpath munging done by the plugin
See here for details (that page also linked to from the main page now here).

In answer to your other questions:

> What kind of support do you have for Maven?
> I configured PIT in Maven correctly to avoid such class loading problems, but it seems that such a configuration is not correctly picked up by your plugin…

Maven and Gradle both should work without such problems in the latest release. If there are still problems please let me know, and please include a copy of the classpath from the "Show Classpath..." popup (described in the link above).

> Is there a way to run the visualization without invoking PIT?

If you are asking about doing that from a menu, that action always invokes PIT. There is currently no way to make a menu selection without invoking PIT. You can always open the toolwindow and cancel the invocation however.

Previous runs are available in the history window, and they remain persisted even on restart. Thus you can select a previous run and its results will display in rest of the toolwindow and the editor.

> I normally invoke static analysis and coverage directly in Maven and want to visualize the generated results in IntelliJ only. Otherwise you need to configure the tools twice one time for maven and one time for IntelliJ.

It should load your pit results automatically even if invoked from Maven, it should just appear as a history entry in the toolwindow. If not please let me know.