Rambo is a gem that generates API contract tests from API docs in RAML. Rambo is being developed to test APIs complying with standard REST practices. Mileage may vary with other architectures, but I'm happy to consider pull requests.
Rambo is still in development. It is unstable and has a limited feature set. Use at your own risk and please file issue reports if they come up!
You can install Rambo using:
gem install rambo_rubyYou can also add it to your project's Gemfile:
group :development, :test do
gem 'rambo_ruby', '~> 0.7'
endThere are three options for generating tests from Rambo: The command line tool, the rake task, and the Ruby API. In all cases, Rambo will look for a .rambo.yml file in the root directory of your project for configuration options. Options may also be passed in through the command line as arguments or the Ruby API as a hash. There is currently no option to pass arguments to the Rake task, but Rambo comes pre-loaded with sensible defaults, and the .rambo.yml file is always an option.
Rambo will create spec/contract directory and a spec/rambo_helper.rb file if they don't exist, and will create a spec/contract/foobar_spec.rb file. The latter will overwrite any existing spec file by the same name. This is intentional behavior and will not change in future versions.
The Rack::Test API uses different syntax for Rails and non-Rails Rack apps. By default, Rambo assumes it is dealing with a Rails app, but this is easily modified by passing options or using a .rambo.yml file.
To run the RSpec examples Rambo generates, you will need to have requires in your spec_helper.rb or rambo_helper.rb file:
require "rack/test"require "json"require "json-schema"
To use the command line tool, simply cd into the root directory of your project and run
$ rambo foobar.raml
Replace foobar.raml with the path of the actual RAML file from which you want to generate tests.
By default, Rambo assumes you are testing a Rails app and generates tests using syntax that will work for Rails apps. If you are testing a non-Rails app, you can use the --framework flag to indicate a sinatra:classic, sinatra:modular, grape, or rory app. If you are using a different framework, please open an issue to let us know which, or submit a PR adding support for the framework you are using.
If your app uses an API token header, you can also pass in the token to be used as an option using the -T or --token flag:
$ rambo foobar.raml -T sometoken
Rambo will automatically use this value for any header whose name matches "token" or "key" (not case-sensitive).
After adding rambo_ruby to your Gemfile or gemspec, you will need to add the following to your Rakefile:
require "rambo"
Rambo::Rake::Task.newThis will create a Rake task called rambo. Now, you can generate tests by running:
rake rambo
You can generate Rambo tests from a Ruby script using:
require "rambo"
Rambo.generate_contract_tests!(File.expand_path("doc/foobar.raml"), {})You can pass any options in as a hash. Currently, the available options are :framework and :token. Valid values for the :framework option are :grape, :"sinatra:classic", :"sinatra:modular", :rory, and :rails, with :rails being the default. The :token option takes an API token as a string.
By default, Rambo will always check for a .rambo.yml file in the root directory of your projects and load options from there. If there is no .rambo.yml file, default values will be used (see below).
A sample .rambo.yml file could look like this:
raml: docs/contracts/foobar.raml
framework: sinatra:modular
token: foobarbazThe three possible keys are:
raml- specifies the RAML file to use to generate the tests. The default, relative to the root of your project directory, isdoc/raml/foobar.raml, wherefoobar.ramlis the first RAML file found in thedoc/ramldirectory.framework- specifies the framework you are using. The default value israils; other available frameworks aresinatra:classic,sinatra:modular,grape, androry.token- the API key or token to be included in the security headers. This value will be used for any header whose name matches either "token" or "key" (not case-sensitive).
If a .rambo.yml file is present and additional options are passed in through the command line or Ruby API, the option values that are passed in will override those in the .rambo.yml file.
In order to provide the best user experience to a majority of users, Rambo comes with some sensible defaults that are easily overridden in an optional .rambo.yml file, or by using command line flags or a Ruby option hash (see above).
In the present version, Rambo only generates tests from a single RAML file. If you're using the command line tool, the name of this file is passed in as an argument. If you're not using the command line tool and don't specify by another means (Ruby hash, .rambo.yml file) which RAML file to use, Rambo will look in your_project/doc/raml and use the first RAML file it finds.
As noted above, Rambo currently supports only Rails, Sinatra, Grape, and Rory apps. Since Rails is the most popular Ruby framework, it assumes your app is a Rails app unless specified otherwise. Since Rack::Test syntax differs when testing Rails and non-Rails apps, you will need to tell Rambo if your app is not a Rails app using the --framework flag on the command line, the :framework option for the Ruby API, or specifying framework: <framework> in your .rambo.yml file. Note that for Sinatra apps, you must choose either sinatra:classic or sinatra:modular.
Rambo is able to generate tests for apps written in Rails, Grape, or Sinatra. However, it has one important limitation when working with non-Rails frameworks. Specifically, Rambo does not support multiple subclasses of Sinatra::Base, Sinatra::Application, or Grape::API. In order to identify the class of your app (which is required to configure Rack::Test), the Rambo-generated test configuration will use the first subclass of one of these classes that it finds. There is currently no option to override this behavior. (If you are building a classic Sinatra app instead of the modular type, Sinatra::Application will be used.)
I started Rambo in March of 2016 as part of my work at Renew Financial. For this reason, our primary focus has been on adding the features and functionality that are most important for testing RF's back-end services. Since my contract with Renew Financial has ended, I now have more latitude to do with the project what I want, but also less time to do it.
Rambo, therefore, considers RAML 1.0 and Rails 4 the default, and support for other frameworks and for RAML 0.8 is currently lower priority. We would be delighted to merge pull requests adding such support, as long as they don't adversely affect the features we need most.
Rambo is a new project and any contributions are much appreciated. All pull requests should include comprehensive test coverage and, where appropriate, documentation. If you're not sure where to get started, contact me through Github and I'll be glad to chat.
Additional information for contributors is available in the wiki. Beginning or first-time contributors are welcome and encouraged!
- RAML homepage
- Roy Fielding's dissertation describing Representational State Transfer (REST) architecture
- RESTful Web Services, by Leonard Richardson & Sam Ruby
- Toby Clemson on testing microservices