Full Visual Studio plugin guide

Visual Studio is a large worldwide used environnement. It provides a range of tools that offer many benefits for individual developers and software development teams.

1. Install

Visual Studio Versions supported:
The plugin was tested on Visual Studio 2005 & 2008

Step 1

Follow installer steps

Step 2

Start or ReStart your Microsoft Visual Studio environment to complete installation.

Check installation

You should now see a GreenPepper menu on the toolbar.

If the GreenPepper menu does not appear, go in menu Tools -> Option -> Environment -> Add-in/Macros Security and add the folowing line in paths : %APPDATA%\Microsoft\MSEnvShared\Addins

2. Configure

These are the steps needed to configure the GreenPepper Visual Studio addin.
Before you begin, make sure

Confluence is well configured

I. Solution Configuration

First, you will need to configure where the plugin can find your GreenPepperServer.
This is done in the GreenPepper Options menu dialog.

Enter the URL for the server :

For Confluence, it is the base url of Confluence (e.g. http: //domain:8080/confluence)
For XWiki, it is the main XWiki url followed by /greenpepper/xmlrpc (e.g. http: //domain:8080/xwiki/greenpepper/xmlrpc)

And the GreenPepper handler. (For now only greenpepper1 is available)
You will be able to test the connection by simply clicking on the Test Connection button.

II. Project Configuration

Supported GreenPepper Command Line Runner Versions: GreenPepper Core .NET 1.3.x Framework 2.0

Check the Properties for the Project.
You should now have a GreenPepper property page with two sub-page

Advanced settings
Local repositories

In the GreenPepper page you will identify your Visual Studio project to a System under test (under development).
Doing so, you will see all the associated specification repositories. You will be able to enter your own crudentials for each of these repositories. Optional
You will also need to configure your runner location. Mandatory

Since version 2.5.1

If you don't configure the runner, the plugin will use his internal runner.
The limitations is that you'll be tight coupled to the GreenPepper runner version installed with your plugin.

The Advanced settings page allow you to add optionnal parameters to be sent to the Command Line Runner.

The Local repository page associates your project to local specification directories accessible by your computer.

You are now ready to execute specification documents on your development code.

3. Use

Running specifications

To run specifications, you have to open the Repository View.

There is two differents ways to execute specifications :

I. Execute and Debug specification(s)

By right-clicking on desired specification or group of specifications to be executed
(For debugging, you can right click on a specification)

By clicking in the Repository View menu on "Execute Selected Document" button

II. Results

Running will show you the results :

You can also view the results by double-clicking on the executed specification ( in Repository View ).

Repository view

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

Show the repository view window

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

	Actions
	Will tell Eclipse to work on the Working copy of the Document
	Will tell Eclipse to work on the Implemented copy of the Document
	Will Ask the Repository to MERGE the Working copy with the Implemented copy of the Document
	Executes The selected Document
	Reloads The selected Document from the repository
	Refreshes the Tree

By default Visual Studio plugin will work on the Implemented copy of the document.

Fixture generation

You can generate a skeleton fixture for a specification

In the repository view window

Choose an executable specification, right click on it and select "Generate skeleton fixture"

The Generator View

The generator shows you all fixtures contained in the selected specification.

1. Select the fixture to generate
2. Select the folder where you want to create your fixture
3. Click on "Generate"

The Generated Fixture

Visual Studio plugin fixture generation works for VB.Net and C#.Net.

Keyboard shortcuts

Shortcut	Action
CTRL+G, C	GreenPepperAddIn.Connect.CreateFixture
CTRL+G, D	GreenPepperAddIn.Connect.DebugDocument
CTRL+G, E	GreenPepperAddIn.Connect.ExecuteAllDocument
CTRL+G, X	GreenPepperAddIn.Connect.ExecuteDocument
CTRL+G, P	GreenPepperAddIn.Connect.GreenPepperOptions
CTRL+G, V	GreenPepperAddIn.Connect.GreenPepperRepositoryView
CTRL+G, O	GreenPepperAddIn.Connect.ReloadDocument
CTRL+G, L	GreenPepperAddIn.Connect.ReloadRepositories
CTRL+G, I	GreenPepperAddIn.Connect.SwitchToImplementedVersion
CTRL+G, W	GreenPepperAddIn.Connect.SwitchToWorkingCopy
CTRL+G, F	GreenPepperAddIn.Connect.TagAsImplemented