no_moss 0.6.0 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/no_moss/role_api.rb +1 -1
- data/lib/no_moss/version.rb +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA512:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d86cb329bd0ab0ca155457da7697e33644595f6bb321b85e81e6be432c5f0770e572a46e002befd388e00688045a285ea52dd3d4a1c9bc9002eaccd840ace254
|
|
4
|
+
data.tar.gz: 65e127d9e358be30af316f6ad6ea96c2a460e74651f50d50ceb1046194b1e6fe8607d3135ec061aeb38fe2af03eb2bd42202b31c3fe793fc64ee696b20a1b069
|
|
5
5
|
SHA1:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 21f79db3811fc0df0d9eff1eada5612cb166930d
|
|
7
|
+
data.tar.gz: 5eb97112d405b49b6223b55578dfa75bd7206029
|
data/lib/no_moss/role_api.rb
CHANGED
data/lib/no_moss/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: no_moss
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.6.
|
|
4
|
+
version: 0.6.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Steve Jorgensen
|
|
@@ -9,7 +9,7 @@ autorequire:
|
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
11
|
|
|
12
|
-
date: 2013-
|
|
12
|
+
date: 2013-12-14 00:00:00 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
type: :development
|
|
@@ -87,7 +87,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
87
87
|
requirements: []
|
|
88
88
|
|
|
89
89
|
rubyforge_project:
|
|
90
|
-
rubygems_version: 2.0.
|
|
90
|
+
rubygems_version: 2.0.14
|
|
91
91
|
signing_key:
|
|
92
92
|
specification_version: 4
|
|
93
93
|
summary: Provides a means of defining object role APIs that should be consistent between test subjects (objects under test) and test doubles (AKA mock objects). A role provides data that can be used to verify that a test subject implements the role API. A role also provides a wrapper around a test double that prevents unsupported interactions.
|