runyoufools 0.1.0 → 0.1.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/Gemfile.lock +1 -3
- data/lib/runyoufools/version.rb +1 -1
- data/runyoufools.gemspec +3 -19
- metadata +4 -33
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d0da91af962cffac0e233d1d8e80beb6cedf7c02
|
|
4
|
+
data.tar.gz: 6d2dd053816ba62efed18c1ae7bea6a4fe418666
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 55d8c6093cd75691d171498fe1bc2d05506252492235f29ac2382de136e2efbc50e464d2f920c1e03a3f68a32907e5e531b218b562e2ccf2a5afd42e95133c57
|
|
7
|
+
data.tar.gz: c22a5edf182d45f1149419767dc2aa3ec28cc874c953d9128877f9ffca579151807eba60611333bc39a4a2799b2526d9fc1f88ce6e40ca02b1f865c6b946ada5
|
data/Gemfile.lock
CHANGED
|
@@ -1,9 +1,8 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
runyoufools (0.1.
|
|
4
|
+
runyoufools (0.1.1)
|
|
5
5
|
colorize
|
|
6
|
-
subprocess
|
|
7
6
|
|
|
8
7
|
GEM
|
|
9
8
|
remote: https://rubygems.org/
|
|
@@ -17,7 +16,6 @@ GEM
|
|
|
17
16
|
slop (~> 3.4)
|
|
18
17
|
rake (10.4.2)
|
|
19
18
|
slop (3.6.0)
|
|
20
|
-
subprocess (1.2.0)
|
|
21
19
|
|
|
22
20
|
PLATFORMS
|
|
23
21
|
ruby
|
data/lib/runyoufools/version.rb
CHANGED
data/runyoufools.gemspec
CHANGED
|
@@ -10,24 +10,9 @@ Gem::Specification.new do |spec|
|
|
|
10
10
|
spec.email = ["haarcuba@gmail.com"]
|
|
11
11
|
spec.summary = %q{a generic, language agnostic test-runner for system tests}
|
|
12
12
|
spec.description = <<EOF
|
|
13
|
-
The
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
Most testing framework are more suitable for unit tests. System tests require a broader perspective,
|
|
17
|
-
and a simpler format. I believe that system tests should be readable, self-explanatory scripts that just
|
|
18
|
-
run from top to bottom, e.g. this little bit of Python:
|
|
19
|
-
|
|
20
|
-
# test_basic_client_server_chat.py
|
|
21
|
-
# these are the real thing, not Moch objects of any kind
|
|
22
|
-
server = Server()
|
|
23
|
-
clinet = client()
|
|
24
|
-
client.sendMessage( "what's up, server?" )
|
|
25
|
-
assert server.response() == "I'm OK, how are you?"
|
|
26
|
-
|
|
27
|
-
Different tests should reside in different files, again unlike unit tests.
|
|
28
|
-
|
|
29
|
-
The purpose of runyoufools is to supply the user with a runner to run his/her tests,
|
|
30
|
-
no matter if these tests are Ruby, Python, C++, Perl - whatever - with appropriate hooks for test setup.
|
|
13
|
+
The purpose of runyoufools is to supply the user with a runner to run his/her
|
|
14
|
+
*system* tests, no matter if these tests are Ruby, Python, C++, Perl -
|
|
15
|
+
whatever. This is NOT a runner for unit tests - which have different solutions you can easily find.
|
|
31
16
|
EOF
|
|
32
17
|
spec.homepage = "https://github.com/haarcuba/runyoufools"
|
|
33
18
|
spec.license = "GPL-2"
|
|
@@ -41,6 +26,5 @@ EOF
|
|
|
41
26
|
spec.add_development_dependency "rake", "~> 10.0"
|
|
42
27
|
spec.add_development_dependency 'pry'
|
|
43
28
|
|
|
44
|
-
spec.add_runtime_dependency 'subprocess'
|
|
45
29
|
spec.add_runtime_dependency 'colorize'
|
|
46
30
|
end
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: runyoufools
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Yoav Kleinberger
|
|
@@ -52,20 +52,6 @@ dependencies:
|
|
|
52
52
|
- - ">="
|
|
53
53
|
- !ruby/object:Gem::Version
|
|
54
54
|
version: '0'
|
|
55
|
-
- !ruby/object:Gem::Dependency
|
|
56
|
-
name: subprocess
|
|
57
|
-
requirement: !ruby/object:Gem::Requirement
|
|
58
|
-
requirements:
|
|
59
|
-
- - ">="
|
|
60
|
-
- !ruby/object:Gem::Version
|
|
61
|
-
version: '0'
|
|
62
|
-
type: :runtime
|
|
63
|
-
prerelease: false
|
|
64
|
-
version_requirements: !ruby/object:Gem::Requirement
|
|
65
|
-
requirements:
|
|
66
|
-
- - ">="
|
|
67
|
-
- !ruby/object:Gem::Version
|
|
68
|
-
version: '0'
|
|
69
55
|
- !ruby/object:Gem::Dependency
|
|
70
56
|
name: colorize
|
|
71
57
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -81,24 +67,9 @@ dependencies:
|
|
|
81
67
|
- !ruby/object:Gem::Version
|
|
82
68
|
version: '0'
|
|
83
69
|
description: |
|
|
84
|
-
The
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
Most testing framework are more suitable for unit tests. System tests require a broader perspective,
|
|
88
|
-
and a simpler format. I believe that system tests should be readable, self-explanatory scripts that just
|
|
89
|
-
run from top to bottom, e.g. this little bit of Python:
|
|
90
|
-
|
|
91
|
-
# test_basic_client_server_chat.py
|
|
92
|
-
# these are the real thing, not Moch objects of any kind
|
|
93
|
-
server = Server()
|
|
94
|
-
clinet = client()
|
|
95
|
-
client.sendMessage( "what's up, server?" )
|
|
96
|
-
assert server.response() == "I'm OK, how are you?"
|
|
97
|
-
|
|
98
|
-
Different tests should reside in different files, again unlike unit tests.
|
|
99
|
-
|
|
100
|
-
The purpose of runyoufools is to supply the user with a runner to run his/her tests,
|
|
101
|
-
no matter if these tests are Ruby, Python, C++, Perl - whatever - with appropriate hooks for test setup.
|
|
70
|
+
The purpose of runyoufools is to supply the user with a runner to run his/her
|
|
71
|
+
*system* tests, no matter if these tests are Ruby, Python, C++, Perl -
|
|
72
|
+
whatever. This is NOT a runner for unit tests - which have different solutions you can easily find.
|
|
102
73
|
email:
|
|
103
74
|
- haarcuba@gmail.com
|
|
104
75
|
executables:
|