Skip to content

Getting Started

Richard Tomlinson edited this page May 31, 2016 · 8 revisions

Installation

Installing the Sample package

Download OrgWmAOPSample from the Downloads page. Add it to your IS instance and verify it appears in Designer.

The package contains:

  • Services on which the tests execute - Your normal business like functionality
  • A top level src folder which follows the Java Maven naming convention and in which the test functionality is stored
  • A SoapUI project held in /src/test/resources/soapui which contains a suite of tests using the RESTful interface
  • wm-jbehave tests in /src/test/resources/stories

Applying the dependency manually

Applying the test dependency manually is not ideal and forces the same action every time the package is loaded for use in Designer as well as complicating automated testing.

  • Download the wm-jbehave jar file from the downloads link
  • In Designer, within the Java perspective, right click on the project and select Disable Maven Nature
  • Again right click and select Properties
  • Choose the Java Build Path, select the Libraries tab then click Add External JARs...
  • Select the downloaded wm-jbehave jar file

This should now resolve the problem and no red 'X' should exist against any file. Ideally, use Maven to define and import your projects.

Local maven

Setting up locally resolved Maven files is possible.

Running the stories

SoapUI

Download and install SoapUI v5.2.1, the free open source version or trial SoapUI NG Pro as part of ReadyAPI

Once installed, load the project from src/test/resources/soapui/Samples-soapui-project.xml

When expanding the project within SoapUI, you will see:

  • Endpoint for the tests are localhost:5555 with the usual credentials
  • A grouping for each type of test or feature is shown.
  • The test steps show different calls

You can run each individually by right clicking on the test case and selecting to Show the test case editor, or pressing return. Then press the green 'play' button to execute. If all is well a green bar should show success.

Looking at the package structure