Sha256: 0a0188b28598bf7ee760ec57e15a501be91f018d75a41824957a1125539e87c2
Contents?: true
Size: 1.46 KB
Versions: 2
Compression:
Stored size: 1.46 KB
Contents
[![CircleCI](https://circleci.com/gh/alexfalkowski/nonnative.svg?style=svg)](https://circleci.com/gh/alexfalkowski/nonnative) # Nonnative Do you love building microservices using different languages? Do you love testing applications using [cucumber](https://cucumber.io/) with [ruby](https://www.ruby-lang.org/en/)? Well so do I. The issue is that most languages the cucumber implementation is not always complete or you have to write a lot of code to get it working. So why not test the way you want and build the microservice how you want. These kind of tests will make sure your application is tested properly by going end-to-end. The way it works is it spawns the process you configure and waits for it to start. Then you communicate with your microservice however you like (TCP, HTTP, gRPC, etc) ## Installation Add this line to your application's Gemfile: ```ruby gem 'nonnative' ``` And then execute: $ bundle Or install it yourself as: $ gem install nonnative ## Usage Configure nonnative with the following: - Process that you want to start. - A timeout value. - Port to verify. - The file you want STDOUT to be logged to. - The strategy (Startup will start the process once and before will hook into cucumbers Before and After). ```ruby require 'nonnative' Nonnative.configure do |config| config.process = 'features/support/bin/start' config.timeout = 0.5 config.port = 12_321 config.file = 'logs/output' config.strategy = :startup or :before end ```
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
nonnative-0.8.0 | README.md |
nonnative-0.7.0 | README.md |