These are the steps needed to configure the GreenPepper Eclipse plugin.
Before you begin, you must verify the following:
I. Workspace configuration
First, you have to configure where the plugin can find your GreenPepper Server.
This is done in the workspace preferences dialog box.
Enter the URL for the server (e.g.
http: //domain:8080/greenpepper-server or
if using GreenPepper server 2.x the base url of your Confluence. ).
Enter the GreenPepper handler. (For now only
greenpepper1 is available.)
You can test the connection by clicking on the
Test Connection button.
II. Project configuration
Enable GreenPepper on a project by selecting GreenPepper/Project GreenPepperised.
You should see a check mark beside the menu option afterwards.
 |
Only Java projects can be GreenPepperised. |
Once your project has been
GreenPepperised, check its properties (right-click
Project/Properties).
You should now have a GreenPepper property page with two sub-pages.
- Advanced settings
- Local repositories
In the GreenPepper page, you will identify your Eclipse project to a System Under Test (under development).
By doing so, you will see all the associated specification repositories. You will be able to enter your own credentials
for each of these repositories. Optional
You will also need to configure your runner location. Mandatory
The local repository page associates your project to local specification directories accessible with your computer.
The advanced settings let you override the SystemUnderDevelopment class that resolves the fixture and domain classes.
Make sure your class is in a library that resides in your runner directory. The arguments are seperated by "
;" and will be passed to
the constructor. Please see the
command line options.
You will be able to add additional options to the command line and append additional JVM parameters.
You are now ready to execute specification documents on your development code.
