jumpup 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: eb0354246bd7cbf1ed0d5e456df6f69978327bf2
-  data.tar.gz: 42ee0da3af45702cdb57fca2d5a23636d47cdff7
+  metadata.gz: 0ed0c9528c69588fdb4ceeb4c0903e2a1d3031a3
+  data.tar.gz: f97154f489694aacfa37c24c85b4b8be5c493523
 SHA512:
-  metadata.gz: a3c2b76cb72e3076ca57fb037c1d824ac72b9a7615adfad4e1e0858b454cbe756f81a516b04c9a4b9ee9a32664964031b1775281943facf211a37477551e76da
-  data.tar.gz: 2548f339f950d911785a9ba5614bd0050947b023b046692300f6b0e8288667a1a8f7ba97a5384c9b78ca6205542fddd89be6f240dfd945d03dbe09a741843d0f
+  metadata.gz: 1fd5bc4b91d8d3f279d4f0618009b3475d60a8e5dcf7c3056f9db4965b43ceda7e3b8579ef5221032c17e91f4afe3634f288f49af3ad5d22c39c0023a140e8f4
+  data.tar.gz: f769f6316fc344fddc4e025016fc4e9fd24d38248688e5ce6057d87a267b78379c1184a4ca31c8f9311ead56d559d3e379349a12577e967bf61a244ea8eca80d

data/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.0.6 (unreleased)
+## 0.0.7 (unreleased)
 
 ### features
 
@@ -8,6 +8,15 @@
 
 ### bug fixes
 
+## 0.0.6 (July 11, 2014)
+
+### features
+
+### improvements
+- Transfer coverage verification to simplecov
+
+### bug fixes
+
 
 ## 0.0.5 (May 15, 2014)
 

data/README.mkdn

@@ -51,11 +51,6 @@ The integration process is composed of several steps that are explained ahead. I
 
   Remove temporary files.
 
-* task backup:local
-
-  Backup files locally. This is done before scm update to create a recovery point if you have problems during scm update. If a file merge creates undesirable effects on the software, you can recover from the backup file.
-  Backup file names have a timestamp. By default, the last 30 backups are kept. You may change this number as you'll see shortly. This task won't work on Windows because it uses [tar][]. So, if you're using Windows you'll have to write your own version of this task or just stop using Windows. We highly recommend the later.
-
 * task git:pull
 
   Update local files from your remote scm repository.
@@ -68,10 +63,6 @@ The integration process is composed of several steps that are explained ahead. I
 
   Set the rake task your test/spec suite needs to run. Use a command that generate the coverage files.
 
-* coverage_verify
-
-  Check if tests/specs cover 100% of the application code.
-
 * git:push
 
   Push your changes. If any of the previous tasks break, because one test failed, for instance, the script won't push. Actually this task runs only if every checking done before work well.
@@ -103,19 +94,16 @@ Using this almost paranoid sequence of steps it will be hard to check in bad cod
           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 gem has been installed. It has this very configuration and you can use it as a starting point to customize your integration process**.
-
 * Spec infected programmer
 
-  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:
+  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 change your test_helper.rb/spec_helper.rb with:
 
-        INTEGRATION_TASKS = %w(
-          jumpup:start
-          db:migrate
-          spec
-          jumpup:coverage_verify
-          jumpup:finish
-        )
+  ```ruby
+  require 'simplecov'
+  SimpleCov.start 'rails' do
+    minimum_coverage 100
+  end
+  ```
 
 ## Versioning
 
@@ -151,6 +139,7 @@ Comments are welcome.
 ## Maintainers
 
 - [Thiago Borges](https://github.com/thiagogabriel)
+- [Mauro George](https://github.com/maurogeorge)
 
 ## Authors
 

data/lib/jumpup/version.rb

@@ -1,3 +1,3 @@
 module Jumpup
-  VERSION = '0.0.5'
+  VERSION = '0.0.6'
 end

data/lib/tasks/integrate.rake

@@ -34,11 +34,6 @@ namespace :jumpup do
   end
   task :finish => ["git:push"]
 
-  desc 'Check code coverage'
-  task :coverage_verify do
-    sh "ruby #{File.expand_path(File.dirname(__FILE__) + '/../../test/coverage_test.rb')}"
-  end
-
   desc 'Run bundle install'
   task :bundle_install do
     Bundler.with_clean_env do
@@ -63,7 +58,6 @@ INTEGRATION_TASKS = %w(
   jumpup:bundle_install
   db:migrate
   spec
-  jumpup:coverage_verify
   jumpup:finish
 )
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jumpup
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - HE:labs
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-05-15 00:00:00.000000000 Z
+date: 2014-07-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -54,10 +54,8 @@ files:
 - Rakefile
 - jumpup.gemspec
 - lib/jumpup.rb
-- lib/jumpup/test_case.rb
 - lib/jumpup/version.rb
 - lib/tasks/integrate.rake
-- test/coverage_test.rb
 homepage: https://github.com/Helabs/jumpup
 licenses:
 - MIT
@@ -83,5 +81,4 @@ signing_key:
 specification_version: 4
 summary: Jumpup gem help people that want to do synchronous continuous integration
   on their ruby projects.
-test_files:
-- test/coverage_test.rb
+test_files: []

data/lib/jumpup/test_case.rb

@@ -1,7 +0,0 @@
-module Jumpup
-  if defined?(MiniTest::Test)
-    TestCase = ::Minitest::Test
-  else
-    TestCase = ::MiniTest::Unit::TestCase
-  end
-end

data/test/coverage_test.rb

@@ -1,12 +0,0 @@
-%w(minitest/autorun jumpup/test_case rubygems json).each { |lib| require lib }
-
-class CoverageTest < Jumpup::TestCase
-  COVERAGE_FILE = "coverage/.last_run.json"
-  def test_if_application_is_fully_covered
-    last_run = JSON.parse(File.read(COVERAGE_FILE))
-    covered_percent = last_run['result']['covered_percent']
-
-    assert_equal 100, covered_percent, "\nBad Boy! Coverage is #{covered_percent}% < 100%..."
-    puts "\nCongratulations! Your coverage is 100%!"
-  end
-end