Overview

• De-reference transitive references in oas 2.0 specification

Overview

• Bump Prism to 2.0.0
• Perfomance boost for Prism Instances
• Automatic status code assertions for Scenario HTTP steps
• Removed Bugsnag
• Fix Scenario Refs for prism instances that reffed other Scenarios

Overview

• Bug fixes

Issues

• fixes #137
• fixes #136

Overview

• Parse collection settings correctly
• Support response schema not defined: response schema spec
• Add redirects to collection settings, and support it
• Make sure to always set $$.request, not just for proxy mode
• Set multiple header values correctly on scenario step results
• Unescape step http url correctly
• Support query property for http steps.
• build the runMap correctly for /v1/run endpoint.

Issues

• fixes #135
• fixes #104

Overview

• fixed windows crash on startup
• fixed windows Linux subsystem
• improve OAS expansion for responses, parameters and path items

Issues

• fixes #132

Overview

• add prism mock command to start a mock server

  prism mock --spec oas.json --port 4010 --debug
  
   --spec is required and is the location on disk or the internets
   --port is optional, defaults to 4010
   --debug is optional, defaults to false
  

• add prism validate command to start a validation server

   prism validate --spec oas.json --upstream http://example.com  --port 4010 --debug
  
    --spec is required, and is the location on disk or the internets
    --upstream is optional, defaults to oas specification
    --port is optional, defaults to 4010
    --debug is optional, defaults to false
  

• improve yaml support in for prism instances, scenarios and oas specification

• cookie API in javascript runtime

• scenario refs don't have to point to a collection file, can point to a scenario file.

• look up the correct header for authentication

• bug fixes and other usability improvements

Issues

• closes #106

Overview

YAML Scenarios and OAS support.

Issues

fixes #60

fixes #112
fixes #114

fix modifying the response in an after prism instance, when requests are forwarded upstream.

• download private scenario, oas refs
• fix int64 validation
• validate responses that don't have a content type
• other bug fixes/improvements

• up to a 2x performance boost
• scenario runs timeout after two mins
• configureable request timeout
• $$.stop
• bug fixes and improvements

• prism login is now an interactive command
• don't show password when using prism login
• When looping over step results, don't look up a result that doesn't exist.
• Properly build api host from swagger spec, especially when the api host is an ip address with a port.

• fix issue with swagger refs
• add support for --token, going to be exposed in the stoplight desktop/web app.
• fix spelling for error logs
• other bug fixes/improvements

• Update javascript runtime
• Fix windows
• Report errors at the collection result level
• fix issue with accessing oas specs
• other bug fixes and improvements.

• Breaking: Add login/logout command. If your scenarios are private, you must login first to run them.
• Feature: Add serve command. Run prism instance servers locally.
• Feature: Better error reporting when scenarios/specs fail to download.
• Fix: AWS Authentication when request has a body.

Fix panic for custom json schema formats

• fixes #88
• fixes #89
• Ignore formats that aren't supported for JSON Schema: https://spacetelescope.github.io/understanding-json-schema/reference/string.html#format

• Add array length assertion operation
• Error/Warning reporting
  • malformed body error
  • malformed request url
  • missing scenario ref
  • can’t capture target because it doesn’t exist
  • script errors
  • missing variables
• Validate format binary for JSON Schema/Contract Testing
• Empty base path in swagger spec ( ‘/‘ ) doesn’t cause contract testing and mocking to fail.
• Script step types console.log/warn/debub/error fixed when running from the terminal.
• Fix $$.response.headers.set(‘name’, ‘value’);
• Better error handling for Prism Instances
• Equal assertion in the ui is fixed for null.
• Add $.stop(), to js runtime, to stop current scenario.
• Add stop(), to js runtime, to stop current step.
• Add SL.sleep(milliseconds) to js runtime.

• Don’t panic when an array of refs can’t be expanded because the ref doesn’t exist.

• when running a scenario collection do not run utilities.
• validate empty body properly
• validate.contract should run if a response object is defined in swaggers spec, but json schema isn’t defined. link