Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

I. Workspace configuration

...


  Once your project has been GreenPepperised, check its properties (right-click Project/Properties).

Image RemovedImage Added


  You should now have a GreenPepper property page with two sub-pages.

...

  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.

Image Added

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

...

  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 ...

Image Added

 

 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
Info
titleBy default Eclipse will work on the Implemented copy of the document.

 

...

Image Removed

 

...

Keyboard shortcuts

4. FAQ

I cannot see the GreenPepper property page for my project.

...