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

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

III. Results

Running the specification will give you a result like this one

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

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