https://github.com/senseyeio/mbgo

A mountebank client written in Go.
https://github.com/senseyeio/mbgo

mountebank mountebank-client service-virtualization testing

Last synced: over 1 year ago
JSON representation

A mountebank client written in Go.

• Host: GitHub
• URL: https://github.com/senseyeio/mbgo
• Owner: senseyeio
• License: mit
• Created: 2018-04-20T14:28:51.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2023-02-21T13:58:15.000Z (over 3 years ago)
• Last Synced: 2024-06-19T02:07:50.588Z (almost 2 years ago)
• Topics: mountebank, mountebank-client, service-virtualization, testing
• Language: Go
• Homepage:
• Size: 5.63 MB
• Stars: 11
• Watchers: 10
• Forks: 9
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# mbgo

[![GoDoc](https://godoc.org/github.com/senseyeio/mbgo?status.svg)](https://godoc.org/github.com/senseyeio/mbgo) [![Build Status](https://travis-ci.org/senseyeio/mbgo.svg?branch=master)](https://travis-ci.org/senseyeio/mbgo) [![Go Report Card](https://goreportcard.com/badge/github.com/senseyeio/mbgo)](https://goreportcard.com/report/github.com/senseyeio/mbgo)

A mountebank API client for the Go programming language.

## Installation

```sh

go get -u github.com/senseyeio/mbgo@latest

```

## Testing

This package includes both unit and integration tests. Use the `unit` and `integration` targets in the Makefile to run them, respectively:

```sh

make unit

make integration

```

The integration tests expect Docker to be available on the host, using it to run a local mountebank container at 

`localhost:2525`, with the additional ports 8080-8081 exposed for test imposters. Currently tested against a mountebank 

v2.1.2 instance using the [andyrbell/mountebank](https://hub.docker.com/r/andyrbell/mountebank) image on DockerHub.

## Contributing

* Fork the repository.

* Code your changes.

* If applicable, add tests and/or documentation.

* Please ensure all unit and integration tests are passing, and that all code passes `make lint`.

* Raise a new pull request with a short description of your changes.

* Use the following convention for branch naming: `/`. For instance, `smotes/add-smtp-imposters`.