https://github.com/nishants/wirestub

A wrapper over wiremock , to make it work like a stub.
https://github.com/nishants/wirestub

automation jeyson stubbing test-automation testing wiremock

Last synced: 14 days ago
JSON representation

A wrapper over wiremock , to make it work like a stub.

• Host: GitHub
• URL: https://github.com/nishants/wirestub
• Owner: nishants
• License: mit
• Created: 2016-08-07T04:49:03.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2016-10-21T03:49:46.000Z (over 8 years ago)
• Last Synced: 2024-11-11T10:12:16.441Z (2 months ago)
• Topics: automation, jeyson, stubbing, test-automation, testing, wiremock
• Language: Java
• Homepage:
• Size: 27.3 MB
• Stars: 4
• Watchers: 2
• Forks: 0
• Open Issues: 5
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# Wirestub : wiremock in stub style

- Designed to operate in standalone and stubbing mode only.

- Adds powerful scripting and templating system for wiremock.

- Allows behavioral stubbing without writing java code.

- Adds following feature to wiremock : 

    - templating engine for json and xml.

    - before script to execute instruction before serving response.

    - accessing request body, headers, cookies, query params in templates.

    - xpath support for xml request body.

    - configuration by environment.

    - setting session values in before scripts. 

    - accessing session values in templates.

- This wrapper doesn't change any existing behavior of wiremock, so a wiremock standalone jar can be safely replaced by miraze standalone jar.

- Because it behaves just like wiremock, so it can be used along with other wrappers (like service_mock) and extensions.

- It can be controlled with the wiremock's http api.

- It support all the runtime parameters of wiremock, along with adding some of its own.

# Philosophy : Stubbing over Mocking 

- This extension tries to push developers away from mocking external services instead of stubbing them.

- A stub has a pre-determined behavior and tests are written based on stub's behavior.

- Mocking on the other hand creates expected behavior just before executing a test.

- Hence stubbing facilitates easier reproduction of issues and keeps test data in human readable form (json/xml files).

- Also the test data itself can be validated or migrated into databases if needed.

- Miraze is designed to reflect back user response based on incoming request.

- Though it also allows session variables, but sessions must be avoided to keep stubs stateless.

# Jeyson Template Engine

- request, config, session, directives, custom directives

- link to template syntax.

# Template Features

 - conditional

 - expressions

 - @ignore-if : "expression"

 - @if, @else, @then        : "expression"

 - @include   : "expression"

 - @log       : "expression"

 - @repeat

# Shared templates

- segregate shared template (ease of maintaining test data)

- include template conditionally 

- passing params to template scope.

# Sessions

- get session

- set session

- use session by response body

- reset session by api calls

# @before

- execute script before request

- set or get session variables, request body, header, path, query in script scope.

- exectes lines of javascript expressions in place.

# @headers 

    - use jeyson in headers

    - conditional headers

    

# @body

    - use jeyson expressions in body

     

# @template

Route By Request 

- by url path variable

- by request query param

- by request header

- by request body

- by using expressions

- by session variable

# Run as standalone

# Run as extension

# stub_service (fork of service_mock) ruby gem 

invoke : 

- start server : with runtime parameters

- stub http calls + all service mock features

- reset session

- get session

- set session