These are the steps needed to configure the GreenPepper Visual Studio addin.
Before you begin, make sure
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.
 | 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.
