WireMock: document and mention in NEWS.txt

No functional changes.

[ci skip]

Author: php-coder

NEWS.txt

@@ -22,6 +22,7 @@
 - (functionality)  add support for specifying Zagorski catalog numbers
 - (functionality)  user may specify how many stamps from a series in his/her collection
 - (functionality)  paid users may specify a price that he/she paid for a series
+- (infrastructure) use WireMock in integration tests for mocking external services
 
 0.3
 - (functionality)  implemented possibility to user to add series to his collection

README.md

@@ -45,5 +45,5 @@ If you are programmer/sysadmin or you just feeling that you are able to run a lo
 * *Validation*: JSR-303 (Hibernate Validator)
 * *Logging*: Slf4j (Logback)
 * *Unit tests*: Groovy and Spock Framework (for Java code), jasmine (for JavaScript code)
-* *Integration tests*: Selenium2, RobotFramework, TestNG and fest-assert
+* *Integration tests*: Selenium2, RobotFramework, WireMock, TestNG and fest-assert
 * *Others*: Lombok, Togglz, WebJars

docs/wiremock.md

@@ -0,0 +1,43 @@
+# WireMock
+
+## What and why
+WireMock is a simulator for HTTP-based APIs. We use this tool in the integration tests for mocking
+external services. For example, for testing import of the stamps series from sites.
+
+## Running on TravisCI
+WireMock is automatically running/stopping during integration tests execution (`mvn verify`).
+
+## Running manually
+In order to run the server as a standlone process:
+* uncomment `<keepRunning>` option in the `pom.xml` file
+* execute the `mvn wiremock:run` command
+
+After that the mock server will be available on 8888 port.
+
+## Troubleshooting
+* [run the plugin separately](#running-manually) to be able to test it with a browser/curl
+* append `--verbose` flag to the options from `<params>` tag in the `pom.xml` file. This instructs
+  WireMock to produce more detailed output to the console
+
+## Configuration
+WireMock is fully configured by the `wiremock-maven-plugin` in the `pom.xml` file:
+
+* the server is listening on `8888` port
+* you can refer to the mock server from within RobotFramework test cases by using `${MOCK_SERVER}`
+  variable.
+* static files are reside inside the `src/test/wiremock/__files` directory
+* mocks and stubs are reside inside the `src/test/wiremock/mappings` directory
+
+By our convention the files in these directories should have the same hierarchy as their
+RobotFramework test cases. For instance, the mocks/files used solely by
+`category/creation/logic.robot` test case, should be placed into
+`src/test/wiremock/__files/category/creation/logic` and
+`src/test/wiremock/mappings/category/creation/logic` directories.
+
+In the case, mocks/files are being used by the different test cases, they should reside in a
+directory that is the base for all such test cases.
+
+## Links
+* http://wiremock.org/
+* https://github.com/tomakehurst/wiremock
+* https://github.com/automatictester/wiremock-maven-plugin