Skip to content

Releases: quii/mockingjay-server

Vastly improved CDC failure messages

31 Jan 10:15
Compare
Choose a tag to compare

This release improves the output on failed CDCs by

  1. Using a consistent logger so the formatting is good
  2. Rather than a simple "JSON is incompatible" message, it now finds every problem there is and gives you a list of what's wrong

Example:

Chriss-Air:mockingjay-server quii$ mockingjay-server -config=examples/incompatible.yaml -realURL=http://localhost:9090
mocking-jay: 2016/01/31 10:13:47 ✗ Test endpoint (GET /hello) is incompatible with http://localhost:9090
mocking-jay: 2016/01/31 10:13:47 JSON err on field 'proclomation' : Missing field
mocking-jay: 2016/01/31 10:13:47 JSON err on field 'message' : Field is not a float in other JSON
mocking-jay: 2016/01/31 10:13:47 ✗ Test endpoint 2 (DELETE /world) is incompatible with http://localhost:9090
mocking-jay: 2016/01/31 10:13:47 Got 200 expected 400
mocking-jay: 2016/01/31 10:13:47 ✗ Failing endpoint (POST /card) is incompatible with http://localhost:9090
mocking-jay: 2016/01/31 10:13:47 Exact body match did not pass

This should hopefully make debugging API problems a lot easier.

Another upgrade on equaliser, again!

23 Jan 09:58
Compare
Choose a tag to compare
1.4.4

Update to jsonequaliser

And another json equaliser upgrade!

22 Jan 14:56
Compare
Choose a tag to compare

Handling when there are empty arrays on 'A' JSON.

Another upgrade on equaliser

21 Jan 17:17
Compare
Choose a tag to compare
1.4.2

latest jsonequaliser

Upgrading to new jsonequaliser

21 Jan 16:58
Compare
Choose a tag to compare

Fixes bug with fields defined as having null values

Optional regex URI matching

21 Jan 13:53
Compare
Choose a tag to compare

This release introduces an optional field to the configuration, regexuri

---
 - name: Regex example
   request:
     uri: /hello/chris
     regexuri: \/hello\/[a-z]+
     method: GET
   response:
     code: 200
     body: '{"message": "hello, there"}'
     headers:
       content-type: text/json

When running in server mode, if you define a regex URI then the server will match on this if the incoming URL doesn't match any "concrete" uri.

This allows the fake server to be a bit more flexible.

Please note that the uri field is still required. The reason for this is that it is needed for the consumer driven contract functionality (how would it know what URL to hit if all it has is a regex).

The uri you define must match against the regexuri if supplied

Improved output when duplicate requests found

04 Jan 13:13
Compare
Choose a tag to compare
1.3.1

Improving output of duplicated requests

Fixes a few bugs

02 Jan 09:59
Compare
Choose a tag to compare
1.3

Adding expvar to close #21

1.2

17 Nov 13:27
Compare
Choose a tag to compare
1.2

Version for docker image

First proper release

01 Sep 12:36
Compare
Choose a tag to compare

This has been used on a number of projects with Springer (http://joinit.springer.com/) over the past few months and I believe we ironed out most of the bugs and issues.