Demonstration Space
In order to help new users understand how GreenPepper can help them in their development cycle we have build in a demonstration space. This space will provide examples of executable specifications and the code that goes with it. It should help users to lower down the learning curve and answer a lot of questions on the "how to build an executable specification". This space can be added or removed at anytime from the administration of the plugin (Confluence - Administration - Plugins - GreenPepper Toolbox - Configure - Demo Space)
Enhanced Confluence picker in JIRA
The old Confluence picker in JIRA was very basic and almost unusable for confluence spaces with a lot of pages.
You can now search executable pages in Confluence based on the selected space and a search key!
Managing Classpath from the Maven2 pom.xml
In order to simplify your project definition in GreenPepper (System under tests classpaths, dependencies classpaths etc...) you can now use your pom.xml to be the holder of this definition. The Maven runner will use your pom.xml to build your executable specifications environment.
You will find all the documentation on the maven runner here: Documentation
Remote Execution Runner
The actual Runner retrieves (downloads) the specifications from the server and execute them locally on the workstation, assuming that all the dependencies are specified from the Java command line.
The Remote Execution Runner will only retrieve the execution results, leaving the dependency resolving and execution task to the remote host.
See the command line help for usage (GreenPepper Open - Java is required) :
