minitest 2.10.0 → 2.10.1
Sign up to get free protection for your applications and to get access to all the features.
- data.tar.gz.sig +0 -0
- data/.autotest +2 -1
- data/History.txt +6 -0
- data/README.txt +1 -1
- data/lib/minitest/unit.rb +1 -1
- data/test/metametameta.rb +2 -3
- metadata +47 -24
- metadata.gz.sig +0 -0
data.tar.gz.sig
CHANGED
Binary file
|
data/.autotest
CHANGED
@@ -1,12 +1,13 @@
|
|
1
1
|
# -*- ruby -*-
|
2
2
|
|
3
3
|
require 'autotest/restart'
|
4
|
-
require 'autotest/rcov'
|
4
|
+
require 'autotest/rcov' if ENV['RCOV']
|
5
5
|
|
6
6
|
Autotest.add_hook :initialize do |at|
|
7
7
|
at.testlib = 'minitest/unit'
|
8
8
|
|
9
9
|
at.extra_class_map["MiniTest::Spec"] = "test/test_minitest_spec.rb"
|
10
|
+
at.extra_class_map["TestMeta"] = "test/test_minitest_spec.rb"
|
10
11
|
at.extra_class_map["TestMiniTestUnitTestCase"] = "test/test_minitest_unit.rb"
|
11
12
|
at.extra_class_map["TestMiniTestUnit"] = "test/test_minitest_unit.rb"
|
12
13
|
at.add_exception 'coverage.info'
|
data/History.txt
CHANGED
data/README.txt
CHANGED
@@ -44,7 +44,7 @@ implementors that need a minimal set of methods to bootstrap a working
|
|
44
44
|
test suite. For example, there is no magic involved for test-case
|
45
45
|
discovery.
|
46
46
|
|
47
|
-
"Again, I can
|
47
|
+
"Again, I can't praise enough the idea of a testing/specing
|
48
48
|
framework that I can actually read in full in one sitting!"
|
49
49
|
|
50
50
|
-- Piotr Szotkowski
|
data/lib/minitest/unit.rb
CHANGED
data/test/metametameta.rb
CHANGED
@@ -19,9 +19,8 @@ class MetaMetaMetaTestCase < MiniTest::Unit::TestCase
|
|
19
19
|
output = @output.string.dup
|
20
20
|
output.sub!(/Finished tests in .*/, "Finished tests in 0.00")
|
21
21
|
output.sub!(/Loaded suite .*/, 'Loaded suite blah')
|
22
|
-
output.gsub!(
|
23
|
-
output.gsub!(
|
24
|
-
output.gsub!(/\[[^\]]+\]/, '[FILE:LINE]')
|
22
|
+
output.gsub!(/\[[^\]:]+:\d+\]/, '[FILE:LINE]')
|
23
|
+
output.gsub!(/^(\s+)[^:]+:\d+:in/, '\1FILE:LINE:in')
|
25
24
|
assert_equal(expected, output)
|
26
25
|
end
|
27
26
|
|
metadata
CHANGED
@@ -1,13 +1,13 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: minitest
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
hash:
|
4
|
+
hash: 37
|
5
5
|
prerelease:
|
6
6
|
segments:
|
7
7
|
- 2
|
8
8
|
- 10
|
9
|
-
-
|
10
|
-
version: 2.10.
|
9
|
+
- 1
|
10
|
+
version: 2.10.1
|
11
11
|
platform: ruby
|
12
12
|
authors:
|
13
13
|
- Ryan Davis
|
@@ -36,7 +36,7 @@ cert_chain:
|
|
36
36
|
FBHgymkyj/AOSqKRIpXPhjC6
|
37
37
|
-----END CERTIFICATE-----
|
38
38
|
|
39
|
-
date:
|
39
|
+
date: 2012-01-18 00:00:00 Z
|
40
40
|
dependencies:
|
41
41
|
- !ruby/object:Gem::Dependency
|
42
42
|
name: rdoc
|
@@ -68,26 +68,49 @@ dependencies:
|
|
68
68
|
version: "2.12"
|
69
69
|
type: :development
|
70
70
|
version_requirements: *id002
|
71
|
-
description:
|
72
|
-
|
73
|
-
|
74
|
-
|
75
|
-
|
76
|
-
|
77
|
-
|
78
|
-
|
79
|
-
|
80
|
-
|
81
|
-
|
82
|
-
|
83
|
-
|
84
|
-
|
85
|
-
|
86
|
-
|
87
|
-
|
88
|
-
|
89
|
-
|
90
|
-
|
71
|
+
description: |-
|
72
|
+
minitest provides a complete suite of testing facilities supporting
|
73
|
+
TDD, BDD, mocking, and benchmarking.
|
74
|
+
|
75
|
+
"I had a class with Jim Weirich on testing last week and we were
|
76
|
+
allowed to choose our testing frameworks. Kirk Haines and I were
|
77
|
+
paired up and we cracked open the code for a few test
|
78
|
+
frameworks...
|
79
|
+
|
80
|
+
I MUST say that mintiest is *very* readable / understandable
|
81
|
+
compared to the 'other two' options we looked at. Nicely done and
|
82
|
+
thank you for helping us keep our mental sanity."
|
83
|
+
|
84
|
+
-- Wayne E. Seguin
|
85
|
+
|
86
|
+
minitest/unit is a small and incredibly fast unit testing framework.
|
87
|
+
It provides a rich set of assertions to make your tests clean and
|
88
|
+
readable.
|
89
|
+
|
90
|
+
minitest/spec is a functionally complete spec engine. It hooks onto
|
91
|
+
minitest/unit and seamlessly bridges test assertions over to spec
|
92
|
+
expectations.
|
93
|
+
|
94
|
+
minitest/benchmark is an awesome way to assert the performance of your
|
95
|
+
algorithms in a repeatable manner. Now you can assert that your newb
|
96
|
+
co-worker doesn't replace your linear algorithm with an exponential
|
97
|
+
one!
|
98
|
+
|
99
|
+
minitest/mock by Steven Baker, is a beautifully tiny mock object
|
100
|
+
framework.
|
101
|
+
|
102
|
+
minitest/pride shows pride in testing and adds coloring to your test
|
103
|
+
output. I guess it is an example of how to write IO pipes too. :P
|
104
|
+
|
105
|
+
minitest/unit is meant to have a clean implementation for language
|
106
|
+
implementors that need a minimal set of methods to bootstrap a working
|
107
|
+
test suite. For example, there is no magic involved for test-case
|
108
|
+
discovery.
|
109
|
+
|
110
|
+
"Again, I can't praise enough the idea of a testing/specing
|
111
|
+
framework that I can actually read in full in one sitting!"
|
112
|
+
|
113
|
+
-- Piotr Szotkowski
|
91
114
|
email:
|
92
115
|
- ryand-ruby@zenspider.com
|
93
116
|
executables: []
|
metadata.gz.sig
CHANGED
Binary file
|