Skip to content

Latest commit

 

History

History
27 lines (15 loc) · 1.28 KB

DOCS.md

File metadata and controls

27 lines (15 loc) · 1.28 KB

Maze Runner 🏃

A test runner for validating requests.

How it works

The test harness launches a mock API which awaits requests from sample applications. Using the runner, each scenario is executed and the requests are validated to have to correct fields and values. Uses Gherkin and Cucumber under the hood to draft semantic tests.

Getting Started

Mock server

In all modes of operation, Maze Runner automatically starts an HTTP server that mocks Bugsnag's server endpoints. This mock server provides a URL for each endpoint that Bugsnag does, allowing it to receive errors, session, builds, source map uploads and traces.

See Mock Server for more details of the options available for controlling the behaviour of the mock server.

Modes of operation

Internally, Maze Runner has the following modes of operation

  • Appium/Devices - For running tests with Appium on local Android/iOS device or using a device farm such as BitBar or BrowserStack.
  • Selenium/Browsers - For running tests with Selenium locally using a browser farm such as BitBar or BrowserStack.

Test outputs

See Test Outputs for details of logging and other outputs generated by Maze Runner.