rack-test-poc 2.0.1 → 2.0.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -1
- data/VERSION +1 -1
- data/lib/rack/test/poc.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: ed34174c0a0ecacc8a0ab3afcd1d142a9bd32291
|
4
|
+
data.tar.gz: 0d36e3b67ca0ce77ffba9f74dccf7847d6af234c
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 9f89b386c4827ff526a5b36ab592aeaa57819c33cd86dc3f1fbe1ec4e163155147e366e8fc82f43ffad750e1195de40aaa4db2fb1946b9b99357431702077336
|
7
|
+
data.tar.gz: 68f6d61dd6dd02b4869c6b3c837bf86c9f852be959843efa908adc91d4b3813801db5c801d1b9c387d862bd7f5cfcdeb05e09f0aa956afa36d4e1507d26c95ee
|
data/README.md
CHANGED
@@ -28,7 +28,7 @@ All you need to do is to require 'rack/test/poc' in your test_helper
|
|
28
28
|
when you working with rack-test module,
|
29
29
|
and you good to go!
|
30
30
|
|
31
|
-
If you can, you should always describe with :is_for object methods, the response content,
|
31
|
+
If you can, you should always describe with :is_for, :it_is_for object methods, the response content,
|
32
32
|
so it can be easy to analyze out from the poc file, or even can be used in documentation generating!
|
33
33
|
With that you can make Google Api docs level documentations!
|
34
34
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
2.0.
|
1
|
+
2.0.2
|
data/lib/rack/test/poc.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: rack-test-poc
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 2.0.
|
4
|
+
version: 2.0.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Adam Luzsi
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2014-11-
|
11
|
+
date: 2014-11-15 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: bundler
|