1. Install

The update site for GreenPepper's Eclipse development tools plugin is located at: http://www.greenpeppersoftware.com/greenpepper-eclipse.

Step 1

In Eclipse, choose Help/Software Updates/Find and Install.

Step 2

Select Add... button to add a new remote site.

Step 3

To update the plugin enter following link: http://www.novatec-gmbh.de/updatesite/aqe

Step 4

In the tree of available updates select GreenPepper Development Tools and click Next >.

Step 5

Click Next > button in the Install Details window.

Step 6

You have to accept the terms of the license agreement to be able to proceed with the installation. You are now ready for the installation, click Finish.

Step 8

Once the download manager has started downloading, you see the Security Warning popup. The authenticity of software can not be established. You have to click Ok to continue with the installation.

Step 9

After the installation you must restart the Eclipse workbench, for the plugin to be available within the application.

Checking the installation

You should now see the GreenPepper menu on the toolbar.

Select Installation Details menu from Help to check the correct installation of the plugin.

Updating

You can see the current installed version of the plugin and a link for checking for updates.

Alternative: Select the first option in step 2.

2. Configure

Following steps are needed to configure the GreenPepper Eclipse plugin.
Before you begin, you must verify:

• You have downloaded the binaries for GreenPepper Core Java version on your workstation.
• Confluence is well configured.

I. Workspace configuration

First, you have to configure where the plugin can find the GreenPepper Server.  This is done in Window >> Preferences.

Enter the URL for the server :

• For Confluence, it is the base url of Confluence (e.g. http: //domain:8080/confluence)

Enter the XML-RPC 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.

  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.

3. Use

Running specifications

A GreenPepper project, inside Eclipse, is a JavaProject.
When you greenpepperised a Java project, you gain access to Run
To validate that your project developement code respect the example in the specifications, you create a new Run Configuration.

I. Run Configuration

The Debug configuration works the same way.  Then create a new GreenPepper Specification

II. Inputs

1. Project
   Your eclipse project to launch the specification on.
2. Repository UID
   The remote Repository UID (None if local)
3. Document Repository base URL
   The Repository URL (Or directory path if local)
4. Document Repository Class
   • com.greenpepper.repository.FileSystemRepository for files
   • com.greenpepper.runner.repository.AtlassianRepository for Jira/Confluence
   • com.greenpepper.runner.repository.VFSRepository for zip ...
5. Username
   If Authentication is need for the Repository access
6. Password
   If Authentication is need for the Repository access
7. Specification
   The Specification name (Document name)
8. Current Version
   If versioning is handled, aim for the latest version of the document.
   
   

III. Execute Document

Open the Repository View and click right to execute a certain document to run the tests.

IV. Results

  Running the specification will give you a result like this one

  Notice that the html result file was added to your project files.

V. Text Result

  If the window displayed shows html in a text format, check your Open With setting for the html file

  You need the Browser support plugin to be able to see the html page inside an Eclipse Editor.

Repository view

You can view all the specifications for your project using the repository view.

Show the repository view window

There is two ways to access the repository view.
1) From the GreenPepper menu

2) From the eclipse standard view selection.
    First choose Show View-Other
    Then choose GreenPepper RepositoryView

The Repository View

  The Repository view is a JUnit like view.
  You will be able to launch executions, view documents and results and work on both Implemented and Working copies of the documents.
  Careful ! the Green bar might be addictive after a while ...

project GreenPepperised   Repositories A JIRA Repository A Confluence Repository A Remote File Repository A Local directory   Documents Plain Executable Working differs from the Implemented copy Working copy Broken Reference

Actions Will tell Eclipse to work on the Working copy of the Document(s) Will tell Eclipse to work on the Implemented copy of the Document(s) Will Ask the Repository to MERGE the Working copy with the Implemented copy of the Document(s) Executes all the selected Documents Executes The selected Document Reloads The selected Document from the repository Opens a Fixture class Creation Wizard to generate the Fixture and its needed components (v. BETA only) Refreshes the Tree

Keyboard shortcuts

4. FAQ

I cannot see the GreenPepper property page for my project.

Make sure your project has been GreenPepperized using the option menu. Only projects with a GreenPepper nature have the GreenPepper property pages.
See Configure GreenPepper Eclipse plugin for more information.

I cannot see my project in the projects combo when creating a Run Configuration.

Make sure your project has been GreenPepperized using the option menu. Only projects with a GreenPepper nature can have a GreenPepper run configuration. See Configure GreenPepper Eclipse plugin for more information.

Some of the pages I retrieved from Confluence have underlined macro errors.

To prevent deadlocks, we ask Confluence not to render the GreenPepper macros for third party applications witch result in an underlined error on the rendered page.