Eclipse plugin for PIT. Update site: http://eclipse.pitest.org/release
If you wish to build the plugin from source, you will need the following.
- Maven 3.0
- Nexus OSS setup for P2 Repository support https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+P2+Repository+Plugin or http://mrexception.blogspot.co.uk/2012/04/p2-support-for-nexus-oss.html OR
- Nexus Pro
You will need to setup p2 proxys for the following update sites:
- http://download.eclipse.org/releases/indigo
- http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site/
- http://jbehave.org/reference/eclipse/updates/
- Eclipse installation 3.6 or greater
- SWTBot plugin (to drive UI testing) - update site http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site/
- JBehave plugin (to run the UI stories) - update site http://jbehave.org/reference/eclipse/updates/
Import the project as a maven project. You may need to disable the maven nature from the org.pitest.pitclipse.core & org.pitest.pitclipse.ui modules (right-click Maven -> Disable Nature). If you check the build properties of org.pitest.pitclipse.core & org.pitest.pitclipse.ui, ensure it has the Plug-in Manifest Builder enabled.
The UI tests use SWTBot to drive the UI interactions. To run the UI tests, open SimpleJavaProjectTest and Run As -> SWTBot Test. This launches JBehave and runs stories matching the file name pattern u*.story.
Due to limitations with Tycho, the PIT build has to be run it two steps:
- mvn clean install deploy -Pbundle
- mvn clean install -Pplugin
The contents of pitclipse-plugin/org.pitest.pitclipse.site/target/repository/ can then be used as an update site.
NB - there is also a ui-test profile which should run the UI tests. However, for reasons not yet ascertained, the eclipse instance started by tycho does not seem to be able to add JUnit to the classpath of the test projects.
If you wish to develop the Pitclipse plugin and run the acceptance tests, you will need to build a development plugin locally. There is a bit of a chicken and egg situation in that you need to build and install the plugin before you can develop against. You can then setup a local update site and install everything from there. Again, needs to be done in two steps:
- mvn clean install deploy -Pbundle,ui-test -U
- mvn clean install -Pplugin,ui-test -U
The contents of pitclipse-plugin/org.pitest.pitclipse.test-site/target/repository/ should be used as the update site.