baleen 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,15 @@
 ---
-SHA1:
-  metadata.gz: d42b96c06c8175ef15d7ec8240771e4ffa5fd596
-  data.tar.gz: f3e181c9f73e1611e2852a432da6e15239749525
-SHA512:
-  metadata.gz: 24edf1fe8a21baa0e6f7b76716084d163c49b74daff316ab2be3d784722b00a23e12d071e762dea52a8ef1156d61050edff06f3a309b67be8c20d60e984c37d3
-  data.tar.gz: 4dd3b940c44dd665c1150b1fa45798dbf88c9d40bd2088210b1b54e7f166a0a402fa004b8248783ceca97472216698f750e229f69dc66b5b097de1a4bc7ab928
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    OGY2MjEyY2M5YTgyY2FiMzBiZTE1ODI4NjkxNTE3M2NiMjVlMDU2Mg==
+  data.tar.gz: !binary |-
+    ZTFhNWQ0M2NjYzk5MDgxMDIxNzNmYjEyNzZhMjU1OWQyOWQyNjZiZQ==
+!binary "U0hBNTEy":
+  metadata.gz: !binary |-
+    ZjM1MzFjMzJkZjU0ZThmNDNlMmQxMWM3OTc3ZTRkM2I5YzRlZDNmMTgzN2Ux
+    MGYwZDdkMDAzNmYxZWFhODYwNjc4MGVmNjhiMDc2YjBiN2U0NGQyY2M1NDY4
+    YjM3ODdmY2VhZWMyYzE3ZDJhYWFhMWM3NTliMDUxMTA0NDlhMjA=
+  data.tar.gz: !binary |-
+    M2M1ZGM4YzcxZjViYzMwOWI1NjE2ZDBiZTc5MzlkMzIyYTIxOWU1OTIwZTlk
+    MjYwZDEzNDhiNDk4MDA4OTczNmQ5MzBiMTU1ZmYxNWNlYTYzMGYxODEzMjVj
+    YTRkYWVmNjE0ZjM1OWMzN2JmMjdkZTAxNjg2ODUyYTcwYWU1OTc=

data/Dockerfile

@@ -1,3 +1,2 @@
 From kimh/baleen-server
-Expose 5533:5533
-Entrypoint ["/bin/bash", "-c", "source /etc/profile && baleen-server start --docker_host 172.17.42.1 && tail -f /dev/null"]
+Entrypoint ["/bin/bash", "-c", "source /etc/profile && baleen-server start --docker_host 172.17.42.1"]

data/README.md

@@ -1,23 +1,38 @@
 # Baleen
-Baleen is a test runner powered by Docker and Celluloid::IO.
-Baleen allows you to run ruby standard tests such as Cucumber or Rspec in totally isolated environment and parallel.
+Baleen is a test runner powered by Docker.
 
-By using Baleen, you can tests in a dedicated linux container, so each test will not affect the state of other tests.
-Also, Baleen will speed up your tests since multiple containers run their tests in parallel.
+Baleen allows you to run ruby standard tests such as Cucumber or Rspec in totally **isolated** environment and **parallel**.
+
+## Supproted Framework
+As of v0.2, only cucumber tests are supported.
 
 ## Requirement
-* Linux machine with Docker installed
+* Docker v0.7 or later
 * ruby-2.0.0 or later
 
 ## Installation
 
     gem install baleen
 
+This will install both client and server.
+
+## Basic workflow
+
+####1. Creating Docker image
+First of all, you need to create a Docker image where you can run your app's tests. Since Baleen run actual tests by running the image, you need to have latest test codes on the image. Baleen's CI feature will help this by automatically updating your image whenever you push to specific branch of github.
+
+####2. Running baleen-server
+baleen-server will wait for client to run tests
+
+####3. Trigger test from baleen cli
+Requests baleen-server to run specific tests. You can do by either using on-the-fly or project. (explained later)
+
 ## Usage
-Baleen is server-client model. You need to run baleen-server which talks Docker API and baleen (client) to put your request to the server.
+Baleen is server-client model. By installing baleen gem, you will get two executables: baleen-server (server) and baleen (client).
+
+You use baleen-server which receives request from client and interacts Docker via remote API.
 
-#### Running Baleen server
-You can run baleen server with baleen-server command.
+#### baleen-server
 
     $ baleen-server start
 
@@ -26,94 +41,267 @@ baleen-server will take below options
 * --docker_host: specify url or ip of server where Docker server is running. Default: 127.0.0.1
 * --docker_port: specify port that Docker server is listening to. Default: 4243
 * --port: specify port that Baleen server is listening to. Default: 5533
-* --debug: you can specify this option to enable debug mode to print out debug message to console. No argument is required. Default: disabled
+* --dir: working directory for docker-server. Default: ./baleen 
+* --project_file: specify file path for project. Default: ~/baleen.yml
+* --ci: specify whether running CI server to receive github post receive hook. Default: false
+* --ci-port: specify port to listen github post-receive hook. Default: 4567
+* --log-level: specify log level. It is should be either "debug", "warn", or "error"
+* --daemon: running baleen-server on background. Default: false
 
-#### Running Baleen client
-You can run baleen client with simply baleen command. baleen command will take one subcommand to specify which kind of test you want to run on baleen server. With v0.0,1. only cucucmber subcommand is available.
+#### baleen
 
-    $ baleen cucumber --image kimh/baleen-poc --files features --work_dir /git/baleen/poc --before_command "source /etc/profile" --concurrency 6
+    $ baleen subcommand --option1 --option2
 
-baleen command wil take below options
+baleen command will take two subcommands
+
+* project: specify project to run
+
+**project** subcommand will take one more subcommand to specify project name
+
+* cucumber: run cucumber tests
+
+**cucumber** subcommand wil take following options
 
-* --port: specify port number of baleen server. Default: 5533
 * --image: specify the name of image that you want to use to run your tests. Mandatory option
 * --files: specify directory or file of tests that you want to run. Default is /features with v0.0.1
 * --work_dir: specify working directory. Default: ./
 * --before_command: specify commands that you want to execute before running your tests. Default: nil
 * --concurrency: specify number of containers that you want to run at the same time. Default: 2
 
-## Try Baleen with POC app
-If you pull kimh/baleen-poc image to your Docker, you can see how baleen works. In this example, you are running Docker at 192.168.0.1, baleen-server @192.168.0.2 that points to the Docker server, and baleen client to point to the baleen server.
+Both subcommands can take following options
 
-First, pull the image at Docker server
+* --baleen_server: specify host where baleen-server is running. Default: 127.0.0.1
+* --port: specify port number of baleen server. Default: 5533
+* --debug: running client on debug mode. As of v0.2, debugging only printing celluloid debug messages to console.
 
-    $ docker pull kimh/baleen-poc
+### Using Baleen
+There are mainly two ways to use baleen
 
-By pulling kimh/baleen-poc, you will have a container that has the latest baleen project, installed under /git.
-You need to run Docker with API enabled (Docker server listens 127.0.0.1 by default) by modifying /etc/init/docker.conf.
+* on-the-fly: You pass options to baleen-server from baleen cli.
+* project: You write baleen.yml file for projects that will be loaded baleen-server at boot time.
 
-    $ vi /etc/init/docker.conf
+#### On-the-fly
+With on-the-fly way, you will use baleen cli and passes options. Benefit of this approach is you can change options flexibly. This is suitable when you need to figure out what options you need to pass to run your tests successfully.
+
+Here is an example to use baleen cli to let baleen-server to run test on the fly. With this, you are running cucumber tests by using kimh/baleen-poc Docker image and running 6 containers, each container running one feature, at the same time.
+
+    $ baleen cucumber --image kimh/baleen-poc --files features --work_dir /git/baleen/poc --before_command "source /etc/profile" --concurrency 6
+
+#### Project
+By using project, you can save test configurations in a yaml file which is loaded by baleen-server at boot time. After that, you can kick the project from baleen cli simply by specifying project name like this.
+
+    $ baleen project my-project
+
+Project file consists of project name section that has 3 sub sections (runner, framework, and ci) and each sub section has more sections. You can specify multiple projects in a single file. Here is an example of project file.
+
+    # Project name section
+    baleen-poc:
+      # Runner section
+      runner:
+        image: "kimh/baleen-poc"
+        work_dir: /baleen-poc
+        concurrency: 3
+        before_command: |
+          source /etc/profile
+          export RAILS_ENV=test
+          bundle exec rake db:migrate
+
+      # Framework section
+      framework:
+        type: cucumber
+        features: ./features/t1.feature
+
+      # CI section
+      ci:
+        build: true
+        url: https://github.com/kimh/baleen-poc
+        repo: baleen-poc
+        branch: master
+
+##### Project name section
+You must have one project name section to specify the name of project.
+
+Under project section, you should have 3 sub sections. Each section has mandatory and optional sections. If you don't specify optional sections, it follows the same default value as the equivalent baleen cli option if exists.
+##### Runner section
+You must have one runner section. Runner section has following sub sections.
+
+_Mandatory_
+
+ * image: Name of Docker image. This is equivalent to --image option of baleen cli.
+
+_Optional_
+
+ * work_dir: Working directory. This is equivalent to --work_dir option of baleen cli.
+ * concurrency: Number of concurrency. This is equivalent to --concurrency option of baleen cli.
+ * before_command: Specify commands that you want to be executed before running tests. Note that you can use block syntax of yaml to specify multiple commands. This is equivalent to --before_command option of baleen cli.
+
+##### Framework section
+You must have one framework section to specify settings for test frameworks to run.
+
+_Mandatory_
+
+ * type: Specify the name of test framework. As of v0.2, only cucumber is allowed to specify. This is equivalent to cucumber subcommand of baleen cli.
+
+
+_Optional_
+
+Below sections are optional. If you don't specify, it follows the same default value as the equivalent baleen cli option.
+
+ * featutes: Specify feature files to be run. This section is only valid only when you specify cucumber at type. This is equivalent to --files option of baleen cli.
 
-    description     "Docker daemon"
+##### CI section
+You must have one ci section to specify CI (continuous integration) setting. Note that this section will be ignored if your don't give --ci option to baleen-server.
 
-    start on filesystem or runlevel [2345]
+_Mandatory_
+
+  * repo: Name of repository.
+  * url: URL of your github repository to pull.
+
+_Optional_
+
+  * build: Specify whether you want to receive github post receive hook to run your projects automatically. This is equivalent to --ci option of baleen-server command.
+  * branch: Branch to pull and use it for tests.
+
+## Try Baleen
+Please try Baleen and give me your feedback!!
+
+In this section, you will use baleen to run cucumber tests of [poc](https://github.com/kimh/baleen-poc "baleen-poc app"). baleen-poc is a fake app with some cucumber features to show how baleen runs cucumber tests.
+
+Here, I am assuming two different scenarios: Linux user and Mac user. If "Only for Mac user", Linux user can skip the section. Otherwise, both users have to do the section.
+
+#### Installing Docker
+First of all, you need to install Docker. Please follow [official page](https://www.docker.io/gettingstarted/#h_installation "instruction at official page").
+
+#### Enable remote API
+Docker only allows access through unix socket by default. Since baleen relies on Docker remote API, you need to enable the access through TCP.
+
+Open _/etc/init/docker.conf_ and modify **DOCKER_OPTS**.
+
+    $ vi /etc/init/docker.conf
+    description "Docker daemon"
+
+    start on filesystem and started lxc-net
     stop on runlevel [!2345]
 
     respawn
 
     script
-       /usr/bin/docker -d -H=tcp://0.0.0.0:4243/ # Add this line
-       #/usr/bin/docker -d                       # and comment out this line
+    	DOCKER=/usr/bin/$UPSTART_JOB
+    	DOCKER_OPTS="-H tcp://0.0.0.0:4243 -H unix:///var/run/docker.sock" # Add this line
+    	if [ -f /etc/default/$UPSTART_JOB ]; then
+    		. /etc/default/$UPSTART_JOB
+    	fi
+    	"$DOCKER" -d $DOCKER_OPTS
     end script
 
-And restart your machine to apply the new configuration.
+Restart docker
+
+    $ restart docker
+
+#### Configure port forwarding for Vagrant (Only for Mac user)
+_You can skip this step if you use Linux_
+
+Add following line to Vagrant.configure block to forward 5533 port
 
-Next, run baleen-server. Make sure you specify correct ip of the machine that is running Docker.
+    config.vm.network :forwarded_port, guest: 5533, host: 5533
 
-    $ baleen-server --docker-host 192.168.0.1
+And run Vagrant and Docker.
 
-Finally, run baleen. Make sure to specify correct ip of the machine that is running baleen-server. Below command will run all features under /git/baleen/poc with three containers.
+#### Pull images
+
+    $ docker pull kimh/baleen-server
+    $ docker pull kimh/baleen-poc
+
+#### Running baleen-server container
+
+    $ docker run -i -t -p 5533:5533 kimh/baleen-server
+
+#### Use baleen cli and run baleen-poc project
+
+    $ baleen project baleen-poc
+    Start container f77b2608137e
+    Start container 722f5d4a8662
+    Start container 85f8778d797d
+    Start container 4aa0aebbf725
+    Start container 693055e07f84
+    Finish container 722f5d4a8662
+    Finish container 85f8778d797d
+    Finish container 693055e07f84
+    Finish container 4aa0aebbf725
+    Finish container f77b2608137e
+    Start container a2c45645d42a
+    Start container cf34f905be5a
+    Start container 636d390ed150
+    Start container 1f506e49f156
+    Start container 887295220ca6
+    Finish container 1f506e49f156
+    Finish container 887295220ca6
+    Finish container 636d390ed150
+    Finish container cf34f905be5a
+    Finish container a2c45645d42a
+    Start container e6ada0b3405e
+    Finish container e6ada0b3405e
 
-    $ baleen cucumber --host 192.168.0.2 --image kimh/baleen-poc --work_dir /git/baleen/poc --before_command "export RAILS_ENV=test; source /etc/profile" --concurrency 3
     [Summary]
     Result: Pass
-    Time: 0min 38sec
-    12 containers
+    Time: 0min 41sec
 
     [Details]
-    Id: 5a836a088480f557bf79a00b0c6e34b36e8432f53ee8b5231b8983d902ae21d9
+    Id: f77b2608137e
     status code: 0
-    feature file: features/io_bound.feature
-    logs:
+    feature file: ./features/t6.feature
+
+    Id: 722f5d4a8662
+    status code: 0
+    feature file: ./features/t1.feature
+
+    STDOUT:
     ------------------------------------
-    Rack::File headers parameter replaces cache_control after Rack 1.5.
     Using the default profile...
-    Feature: Benchmark IO intensive feature
+    Feature: t1
 
-      Scenario: Benchmark for IO bound operation # features/io_bound.feature:2
-        Then io intensive operation              # features/step_definitions/fake_test_steps.rb:20
+      Scenario: Benchmark for IO bound operation # ./features/t1.feature:2
+        Then io intensive operation              # features/step_definitions/fake_test_steps.rb:24
 
-    1 scenario (1 passed)
-    1 step (1 passed)
-    0m1.556s
+      Scenario: Benchmark for CPU bound operation # ./features/t1.feature:5
+        Then cpu intensive operation              # features/step_definitions/fake_test_steps.rb:9
 
-    Id: 1e25993136553319379a07efd61fbc2b86094151fa25df4da0fc613f8c4fe87c
-    status code: 0
-    feature file: features/io_bound.feature
-    logs:
+      Scenario: Benchmark for IO bound operation # ./features/t1.feature:8
+        Then io intensive operation              # features/step_definitions/fake_test_steps.rb:24
+
+      Scenario: Benchmark for CPU bound operation # ./features/t1.feature:11
+        Then cpu intensive operation              # features/step_definitions/fake_test_steps.rb:9
+
+    4 scenarios (4 passed)
+    4 steps (4 passed)
+    0m4.723s
+
+    STDERR:
     ------------------------------------
     Rack::File headers parameter replaces cache_control after Rack 1.5.
-    Using the default profile...
-    Feature: Benchmark IO intensive feature
 
-      Scenario: Benchmark for IO bound operation # features/io_bound.feature:2
-        Then io intensive operation              # features/step_definitions/fake_test_steps.rb:20
+    ....snip.....
+
+### How Baleen works (briefly explained)
+So how baleen-poc tests are run?
 
-    1 scenario (1 passed)
-    1 step (1 passed)
-    0m1.518s
+####Step 1. Breaking up features/ directoires
+First, baleen-server needs to know how many test files exist under the directory specified by features section of baleen.yml.
+To do this, it runs a container by using the image specified at image section and run __find ./features__ bash command.
+
+####Step 2. Run containers
+baleen-server will run containers to run actual tests. It depends on your configuration, but the most simple command for containers are like this.
+
+    $ cd work_dir && bundle exec cucumber $feature_file
+
+where $feature_file is each cucumber file passed from step 1. baleen-server will run proper number of containers according to concurrency.
+
+####Step 3. Wait containers
+baleen-server then monitor and wait for each container to finish given test. This will be done asynchronously thanks to Celluloid.
+
+####Step 4. Report result
+when all containers finish running tests, it collects STDOUT of all containers to see the rest result and display to user.
 
-    ....snip.....
 
 ## Contributing
 
@@ -124,5 +312,3 @@ Finally, run baleen. Make sure to specify correct ip of the machine that is runn
 5. Create new Pull Request
 6. Work hard!!
 
-
-

data/baleen.yml.sample

@@ -1,46 +1,29 @@
-# baleen.yml: Configuration file to run baleen
-#
-# This file is used to specify the configuration for your baleen job.
-# The file has three top sections and config file must have each section
-#
-# base:
-#   Mandatory
-#     baleen-server: IP address or host of baleen server
-#
-#   Optional
-#     port: port that baleen server is listening. Default: 5533
-#
-# runner:
-#   Mandatory
-#     image: name of image to run Docker container where your tests will be run
-#
-#   Optional
-#     work_dir: working directory of container. Default: ./
-#     concurrency: number of containers to run at one time. Default: 2
-#     before_command: commands to run before running your tests.
-#
-# framework:
-#   Mandatory
-#     type: your test framework
-#
-#   Optional
-#     features: place of your feature files when your framework type is cucumber. Default: ./features
-#
+#### Sample baleen project file ####
 
-base:
-  baleen_server: 127.0.0.1
-  port: 5533
+## Use this file as your template to construct your project and save as ~/baleen.yml
+## The file is loaed by baleen-server at boot time (use --project_file option to specify file location)
+## See also https://github.com/kimh/baleen/blob/master/README.md
 
-runner:
-  image: kimh/baleen-poc
-  work_dir: /git/baleen/poc
-  concurrency: 3
-  before_command: bundle install
-  # If you want to specify multiple commands, you can use block style syntax of YAML
-  # before_command: |
-  #   source /etc/profile.d/rvm.sh
-  #   bundle install
+# Project name section
+baleen-poc:
+  # Runner section
+  runner:
+    image: "kimh/baleen-poc"
+    work_dir: /baleen-poc
+    concurrency: 3
+    before_command: |
+      source /etc/profile
+      export RAILS_ENV=test
+      bundle exec rake db:migrate
 
-framework:
-  type: cucumber
-  features: ./
+  # Framework section
+  framework:
+    type: cucumber
+    features: ./features/t1.feature
+
+  # CI section
+  ci:
+    build: true
+    url: https://github.com/kimh/baleen-poc
+    repo: baleen-poc
+    branch: master

data/bin/baleen

@@ -53,7 +53,7 @@ module BaleenCLI
     include Baleen::Default
     include BaleenCliHelper
 
-    option :baleen_server, :required => true
+    option :baleen_server
     option :port
     option :before_command
     option :concurrency
@@ -66,8 +66,8 @@ module BaleenCLI
     def start
      project = {
        base: {
-         baleen_server: options[:baleen_server],
-         port: options[:port]                    || default_port
+         baleen_server: options[:baleen_server]   || default_baleen_server,
+         port: options[:port]                     || default_port
        },
        runner: {
          before_command: options[:before_command] || default_before_command,

data/lib/baleen/version.rb

@@ -1,3 +1,3 @@
 module Baleen
-  VERSION = "0.2.2"
+  VERSION = "0.2.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: baleen
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - Kim, Hirokuni
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-02 00:00:00.000000000 Z
+date: 2013-12-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -28,154 +28,154 @@ dependencies:
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: awesome_print
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: interactive_editor
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: celluloid
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: celluloid-io
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: docker-api
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: colorize
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: thor
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sinatra
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 description: Ballen allows you to run standard ruby tests in parallel and isolated
@@ -243,12 +243,12 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: 2.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
@@ -263,3 +263,4 @@ test_files:
 - spec/lib/baleen/spec_task.rb
 - spec/lib/baleen/spec_validator.rb
 - spec/spec_helper.rb
+has_rdoc: