undercover 0.1.4 → 0.1.5

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: d59941488c038fb70ce49c2b5e05e85695f076a8dc97c9a0948b4f158ae5be63
4
- data.tar.gz: '019136f219f0d4a77d973d882feb747bd0ac6a95d0609572c98ca38103ddc8a3'
3
+ metadata.gz: e3a80729dcf97f5d3188675219a6feba262334737dc4275a16999ae235f43bc0
4
+ data.tar.gz: b79148c4de82f9af0cb49c097082802aba1131d6645be0075255ae710ff032ab
5
5
  SHA512:
6
- metadata.gz: 5430c18e8cef09a54d07419aa32adcdc29ad887db6c719168b3f4bb347473c3612c670a7be6864cdb11c07b4b21a39c45f1456f2438979eff3db5c8ab6dbdef1
7
- data.tar.gz: 523970464fff725778c3f37d2425cd9fbb02f8b1ce0211856b856d3fa14a43a86a97be678bdb92898bef3ab8fd5101cb2ce7e0b2ee7d7598c9076df1b346a16d
6
+ metadata.gz: 68d899cc9910b6322d0e877addddae17cf87adfaaa449e5b25a27b5a2d9f6af090de27b179c4070d892413d67f1f0adedb046a23c0807946fa3373412a53efee
7
+ data.tar.gz: 53a77c9773daff27c1a44387ee1e87f3aca6f245ba1c312b85b1d97916f151ea8aa636723b844ea987eba1c8d4aa38164b41c29647f93ddb05d29cf7d13bc3bf
data/README.md CHANGED
@@ -4,6 +4,17 @@
4
4
 
5
5
  **Inspects files in a git diff and warns on methods, classes and blocks which need test coverage.** Use it locally or as part of an automated build to shorten your code coverage feedback loop!
6
6
 
7
+ ## Why?
8
+
9
+ I wanted to create a tool to help others and myself ensure that tests are written for all the recent code changes. This should be useful for any ruby project, but especially those large or legacy codebases that lack testing (and we can't or don't want to invest in full test coverage).
10
+
11
+ The goal was to provide automated warnings, that are:
12
+ - relevant, so scoped to the actual code changes
13
+ - timely, so we don't end up writing tests long after the implementation
14
+ - actionable, so we can fix them before the code is committed or reaches production
15
+
16
+ ## How?
17
+
7
18
  Technically, `undercover` combines data from git, coverage reports and code structure graphs.
8
19
 
9
20
  A sample output of `undercover` ran before a commit may look like this:
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Undercover
4
- VERSION = '0.1.4'
4
+ VERSION = '0.1.5'
5
5
  end
@@ -23,7 +23,7 @@ Gem::Specification.new do |spec|
23
23
  spec.require_paths = ['lib']
24
24
 
25
25
  spec.add_dependency 'imagen', '~> 0.1.2'
26
- spec.add_dependency 'rainbow', '~> 3.0.0'
26
+ spec.add_dependency 'rainbow', '~> 2.1'
27
27
  spec.add_dependency 'rugged', '~> 0.27.0'
28
28
 
29
29
  spec.add_development_dependency 'bundler', '~> 1.16'
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: undercover
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.4
4
+ version: 0.1.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jan Grodowski
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-05-20 00:00:00.000000000 Z
11
+ date: 2018-06-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: imagen
@@ -30,14 +30,14 @@ dependencies:
30
30
  requirements:
31
31
  - - "~>"
32
32
  - !ruby/object:Gem::Version
33
- version: 3.0.0
33
+ version: '2.1'
34
34
  type: :runtime
35
35
  prerelease: false
36
36
  version_requirements: !ruby/object:Gem::Requirement
37
37
  requirements:
38
38
  - - "~>"
39
39
  - !ruby/object:Gem::Version
40
- version: 3.0.0
40
+ version: '2.1'
41
41
  - !ruby/object:Gem::Dependency
42
42
  name: rugged
43
43
  requirement: !ruby/object:Gem::Requirement