http-api-mock

README

HTTP API Mock

HTTP API Mock is a fork of MMock

HTTP API Mock is a testing and fast prototyping tool for developers:

Easy and fast HTTP mock server.

• Download HTTP API Mock
• Create a mock definition.
• Configure your application endpoints to use HTTP API Mock
• Receive the expected responses
• Inspect the requests in the web UI
• Release it to a real server

Built with Go - HTTP API Mock runs without installation on multiple platforms.

Features

• Easy mock definition via JSON or YAML
• Variables in response (fake or request data, including regex support)
• Persist request body and load response from file or MongoDB
• Ability to send message to AMQP server
• Glob matching ( /a/b/* )
• Route patterns may include named parameters (/hello/:name). Using url-router
• Match request by method, URL params, headers, cookies and bodies.
• Mock definitions hot replace (edit your mocks without restart)
• Web interface to view requests data (method,path,headers,cookies,body,etc..)
• Proxy mode
• Fine grain log info in web interface
• Real-time updates using WebSockets
• Priority matching
• Crazy mode for failure testing
• Public interface auto discover
• Lightweight and portable
• No installation required

Example

Mock definition file example:

{
	"request": {
		"method": "GET",
		"path": "/hello/*"
	},
	"response": {
		"statusCode": 200,
		"headers": {
			"Content-Type":["application/json"]
		},
		"body": "{\"hello\": \"{{request.query.name}}, my name is {{fake.FirstName}}\"}"
	}
}

Or

---
request:
  method: GET
  path: "/hello/*"
response:
  statusCode: 200
  headers:
    Content-Type:
    - application/json
  body: '{"hello": "{{request.query.name}}, my name is {{fake.FirstName}}"}'

You can see more complex examples here.

Getting started

To run HTTP API Mock locally from the command line.

go get github.com/kolesa-team/http-api-mock
http-api-mock -h

To configure HTTP API Mock, use command line flags described in help.

    Usage of ./http-api-mock:
      -console-port int
          Console server Port (default 8082)
      -config-path string
          Mocks definition folder (default "execution_path/config")
      -config-persist-path
          Path to the folder where requests can be persisted or connection string to mongo database starting with mongodb:// and having database at the end /DatabaseName (default "execution_path/data")
      -console
          Console enabled  (true/false) (default true)
      -console-ip string
          Console Server IP (default "public_ip")
      -server-ip string
          Mock server IP (default "public_ip")
      -server-port int
          Mock Server Port (default 8083)

Mock

Mock definition:

{
	"description": "Some text that describes the intended usage of the current configuration",
	"request": {
		"method": "GET|POST|PUT|PATCH|...",
		"path": "/your/path/:variable",
		"queryStringParameters": {
			"name": ["value"],
			"name": ["value", "value"]
		},
		"headers": {
			"name": ["value"]
		},
		"cookies": {
			"name": "value"
		},
		"body": "Expected Body"
	},
	"response": {
		"statusCode": "int (2xx,4xx,5xx,xxx)",
		"headers": {
			"name": ["value"]
		},
		"cookies": {
			"name": "value"
		},
		"body": "Response body",

	},
	"persist" : {
		"entity-id": "{{ request.path.variable }}",
		"entity" : "/users/user-{{ request.entity.id }}.json",
		"collection" : "users",
        "actions"{
			"delete":"true",
			"append":"text",
			"write":"text"
		}
	},
	"notify":{
		"amqp": {
            "url": "amqp://guest:guest@localhost:5672/myVHost",
            "body": "{{ persist.entity.content }}",
			"delay": 2,
            "exchange": "myExchange",
            "type": "MockType",
            "correlationId": "9782b88f-0c6e-4879-8c23-4699785e6a95",
			"routingKey": "routing",
			"contentType": "application/json",
			"contentEncoding": "",
			"priority": 0,
			"replyTo": "",
			"expiration": "",
			"messageId": "",
			"timestamp": "2016-01-01T00:00:00Z",
			"userId": "",
			"appId": ""
        },
		"http":[
			{
				"method": "GET|POST|PUT|PATCH|...",
				"path": "/relative/path/to/call/{{request.url./your/path/(?P<value>\\d+)}}",
				"headers": {
					"name": ["value"]
				},
				"cookies": {
					"name": "value"
				},
				"body": "body in request"
			},
			{
				"method": "GET|POST|PUT|PATCH|...",
				"path": "http://absolute.path/to/call/{{request.url./your/path/(?P<value>\\d+)}}",
				"headers": {
					"name": ["value"]
				},
				"cookies": {
					"name": "value"
				},
				"body": "body in request"
			},
		]
	}
	"control": {
		"proxyBaseURL": "string (original URL endpoint)
		"delay": "int (response delay in seconds)",
		"crazy": "bool (return random 5xx)",
		"priority": "int (matching priority)"
	}
}

Request

This mock definition section represents the expected input data. I the request data match with mock request section, the server will response the mock response data.

• method: Request http method. Mandatory
• path: Resource identifier. It allows * pattern. Mandatory
• queryStringParameters: Array of query strings. It allows more than one value for the same key.
• headers: Array of headers. It allows more than one value for the same key.
• cookies: Array of cookies.
• body: Body string. It allows * pattern.

To do a match with queryStringParameters, headers, cookies. All defined keys in mock will be present with the exact value.

Response (Optional on proxy call)

• statusCode: Request http method.
• headers: Array of headers. It allows more than one value for the same key and vars.
• cookies: Array of cookies. It allows vars.
• body: Body string. It allows vars.

Persist (Optional)

• entity-id: Can be used for generating the entity ID which can be later reused in the definition. You can check the example usage in users-post-generate-id.json and users-storage-post.json
• entity: The relative path from config-persist-path to the file where the response body to be loaded from or the collection name and id if you are using MongoDB. It allows vars.
• collection: Used for returning or deleting more than one record. Represents the relative path from config-persist-path to the folder or the name of the mongo collection from where the records should be selected. Regex or glob can be used for filtering entities as well. Examples for the usage of collections can be found here.
• actions: Actions to take over the entity (Append,Write,Delete)

Notify (Optional)

• amqp: Configuration for sending message to AMQP server. If such configuration is present a message will be sent to the configured server.

  AMQP (Optional)
  • url: Url to the amqp server e.g. amqp://guest:guest@localhost:5672/vhost Mandatory.
  • exchange: The name of the exchange to post to Mandatory.
  • delay: message send delay in seconds.
  • routingKey: The routing key for posting the message.
  • body: Payload of the message. It allows vars.
  • bodyAppend: Text or JSON to be appended to the body. It allows vars.
  • contentType: MIME content type.
  • contentEncoding: MIME content encoding.
  • priority: Priority from 0 to 9.
  • correlationId: Correlation identifier.
  • replyTo: Address to to reply to (ex: RPC).
  • expiration: Message expiration spec.
  • messageId: Message identifier.
  • timestamp: Message timestamp.
  • type: Message type name.
  • userId: Creating user id - ex: "guest".
  • appId: Creating application id.

• http: An array of requests to be made from the mock. This can be useful if you want to create more than one entity when calling an endpoint - that endpoint may call additional endpoints to init other entities related to this one. An example usage can be found in post-user-orders-call-users.json

Control (Optional)

• proxyBaseURL: If this parameter is present, it sends the request data to the BaseURL and resend the response to de client. Useful if you don't want mock a the whole service. NOTE: It's not necessary fill the response field in this case.
• delay: Delay the response in seconds. Simulate bad connection or bad server performance.
• crazy: Return random server errors (5xx) in some request. Simulate server problems.
• priority: Set the priority to avoid match in less restrictive mocks.

Variable tags

You can use variable data (random data or request data) in response. The variables will be defined as tags like this {{nameVar}}

Request data:

• request.query."key"
• request.cookie."key"
• request.path."key"
• request.url
• request.body
• request.url."regex to match value"
• request.body."body path" - can be used for accessing JSON property if body is in JSON format or queryString format property if body is url encoded. Example can be found here users-body-parts.json
• request.body."regex to match value"
• persist.entity.content
• persist.entity.id
• persist.entity.name
• persist.entity.name."regex to match value"
• persist.entity.content
• request.entity.content."path" - can be used for accessing JSON property if content is in JSON format or queryString format property if content is url encoded
• persist.collection.content
• persist.collection.count
• storage.Sequence(name, increaseWith) - generates next sequence with a given name, useful when auto generating id, if no increaseWith is passed or increaseWith = 0 the sequence won't be increased but the latest value will be returned
• storage.SetValue(key, value) - stores a value corresponding to a given key and returns the value. This is useful if you have some entities requested by both id and name, so that you can store the mapping between than and later retrieve it. You can check the samples in storage folder
• storage.GetValue(key) - returns the value corresponding to the given key
• dynamic.Calc(expression) - returns the result of a mathematical or logical expression
• default.Get(value, default) - returns the first value if it's not empty or the default second

Regex: The regex should contain a group named value which will be matched and its value will be returned. E.g. if we want to match the id from this url /your/path/4 the regex should look like /your/path/(?P<value>\\d+). Note that in golang the named regex group match need to contain a P symbol after the question mark. The regex should be prefixed either with request.url., request.body. or response.body. considering your input. When setting the Persist.Collection field the regex can match multiple records from it's input, which is useful for cases like users-delete-passingids.json

Fake data:

• fake.Brand

• fake.Character

• fake.Characters

• fake.CharactersN(n)

• fake.City

• fake.Color

• fake.Company

• fake.Continent

• fake.Country

• fake.CreditCardVisa

• fake.CreditCardMasterCard

• fake.CreditCardAmericanExpress

• fake.Currency

• fake.CurrencyCode

• fake.Day

• fake.Digits

• fake.DigitsN(n)

• fake.EmailAddress

• fake.FirstName

• fake.FullName

• fake.LastName

• fake.Gender

• fake.IPv4

• fake.Language

• fake.Model

• fake.Month

• fake.Year

• fake.Paragraph

• fake.Paragraphs

• fake.ParagraphsN(n)

• fake.Phone

• fake.Product

• fake.Sentence

• fake.Sentences

• fake.SentencesN(n)

• fake.SimplePassword

• fake.State

• fake.StateAbbrev

• fake.Street

• fake.StreetAddress

• fake.UserName

• fake.WeekDay

• fake.Word

• fake.Words

• fake.WordsN(n)

• fake.Zip

• fake.Int(n) - random positive integer less than or equal to n

• fake.Float(n) - random positive floating point number less than n

• fake.UUID - generates a unique id

Persistence

Currently the tool supports two persistence modes:

File system

If you want to use that mode you need to pass the path to the folder where you want to store your data to the following argument - config-persist-path. The default value is set to the data folder under your current execution path. In this mode the entity name in the Persist defines the relative path to the file where the request data will be stored and retrieved from.

MongoDB

To use MongoDB persistence you need to set the url connection string to the config-persist-path. The format of that url should be in the following format: mongodb://[user:pass@]host1[:port1][,host2[:port2],...]/database For example if you are using your local mongo the connection string might be mongodb://localhost/http-api-mock. In this mode the entity name in the Persist define in which collection and with what ID the records to be stored and retrieved from. To achieve this the names should be in the following format: collectionName/itemId

You can check the sample configurations for persistence in the following files:

• users-get.json
• users-post.json
• users-delete.json

That configurations are going to work either with File system or MongoDB modes.

Updating template files

Do the following steps to apply any modifications in tmpl directory:

• Install go-bindata: go get -u github.com/go-bindata/go-bindata/...
• Run go-bindata -o console/bindata.go tmpl/...
• Replace package name main with console in console/bindata.go

Contributing

Clone this repository to $GOPATH/src/github.com/kolesa-team/http-api-mock and type go get ..

Requires Go 1.4+ to build.

If you make any changes, run go fmt ./... before submitting a pull request.

Contributors

• James A. Robinson

Licence

Original work Copyright (c) 2016 Jordi Martin Modified work Copyright 2016 - 2018 Vasil Trifonov

Released under MIT license, see LICENSE for details.