jumpup 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9034054d3abacb3e4bc0ca75822baf3b9843c3c3
-  data.tar.gz: edb667649a01ca4e6158c46481566de7cf2e52ed
+  metadata.gz: 5105b8cc0da609d273f7949b1c9166faf4ac13f3
+  data.tar.gz: 688b114ef4fbf248707d10819991e8c32bb29914
 SHA512:
-  metadata.gz: 02338a6f52369fdbfd5c685a79bf3fd28d90a7796c15c8222a999872d6cf46caeda5720b1290a368e60fbd14861713ca34ef9bd6e3186b965bee4929a7f4f204
-  data.tar.gz: 5848c36943b14f530f322a17e0889cf8d02c70b0368beb8e294def2c523466027bfe4261b85d9fcce0f0dda3c73d4ec257f4c9a636168e8f75b68269b28a62db
+  metadata.gz: e9f6a6988584c24c816e412b11069a87c8aacbe3c898a8dc70c2d3849fb2a3064cbf11cfe8d74fa3f2d3241f56b2a1d79305c28682873e50d1634ab7951de668
+  data.tar.gz: bcb16b9ed90d99ac95085dbf170251717851ec28021b02f25d484c8340cf1a030c91540b2e637ad3c7c4e9a0eec56d9dad2904c84592b2eb98934dc9140492b0

data/README.mkdn

@@ -84,9 +84,9 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
   So you don't have tests, nor specs but you still want to use the jumpup. You might get away with this customized lib/tasks/integration.rake:
 
         INTEGRATION_TASKS = %w(
-          integration:start
+          jumpup:start
           db:migrate
-          integration:finish
+          jumpup:finish
         )
 
   The fact that you can get away with this doesn't mean you should. Don't you think it's already time to grow up and become more professional about software development? I know you believe you have a great excuse to avoid writing those tests or specs. Still it's just an excuse. Write tests or write specs and make a better world!
@@ -96,10 +96,10 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
    You haven't jumped on the [BDD][BDD] bandwagon yet. Instead, you write tests, which is good, but they don't cover all of your code yet, which is bad. We believe you will improve it and make sure your tests cover 100% of your code. In the meantime you might need to skip coverage checkings. Oh, you also don't use [Selenium][sor]. Shame on you! Try this:
 
         INTEGRATION_TASKS = %w(
-          integration:start
+          jumpup:start
           db:migrate
           test
-          integration:finish
+          jumpup:finish
         )
 
   As a matter of fact, since this case might be very common, **we decided to create a lib/tasks/integration.rake for you once the plugin has been installed. It has this very configuration and you can use it as a starting point to customize your integration process**.
@@ -109,11 +109,11 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
   So you used to [TDD][TDD] all around but then someone told you that this is for gramma. The new wave has a name on it: [BDD][BDD]. So, of course, you now have specs covering 100% of your code and doesn't have any more tests. Great! Just do it:
 
         INTEGRATION_TASKS = %w(
-          integration:start
+          jumpup:start
           db:migrate
           spec
-          integration:coverage_verify
-          integration:finish
+          jumpup:coverage_verify
+          jumpup:finish
         )
 
 ## Versioning

data/jumpup.gemspec

@@ -19,5 +19,5 @@ Gem::Specification.new do |spec|
   spec.require_paths = ["lib"]
 
   spec.add_development_dependency "bundler", "~> 1.3"
-  spec.add_development_dependency "rake"
+  spec.add_development_dependency "rake",    "~> 0"
 end

data/lib/jumpup/version.rb

@@ -1,3 +1,3 @@
 module Jumpup
-  VERSION = "0.0.2"
+  VERSION = "0.0.3"
 end

data/test/coverage_test.rb

@@ -6,10 +6,7 @@ class CoverageTest < Test::Unit::TestCase
     last_run = JSON.parse(File.read(COVERAGE_FILE))
     covered_percent = last_run['result']['covered_percent']
 
-    if covered_percent < 100
-      puts "\nBad Boy! Coverage is #{covered_percent}% < 100%..."
-    else
-      puts "\nCongratulations! Your coverage is 100%!"
-    end
+    assert_equal 100, covered_percent, "\nBad Boy! Coverage is #{covered_percent}% < 100%..."
+    puts "\nCongratulations! Your coverage is 100%!"
   end
 end

metadata

@@ -1,41 +1,41 @@
 --- !ruby/object:Gem::Specification
 name: jumpup
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - HE:labs
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-01-08 00:00:00.000000000 Z
+date: 2014-01-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.3'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.3'
 - !ruby/object:Gem::Dependency
   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'
 description: A synchronous continuous integration gem.
@@ -45,7 +45,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
+- ".gitignore"
 - CHANGELOG.md
 - Gemfile
 - MIT-LICENSE
@@ -66,17 +66,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.6
+rubygems_version: 2.2.0
 signing_key: 
 specification_version: 4
 summary: Jumpup gem help people that want to do synchronous continuous integration