dtr 0.0.3
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.
- data/CHANGES +10 -0
- data/LICENSE.TXT +203 -0
- data/LICENSE.txt +203 -0
- data/README +302 -0
- data/Rakefile +425 -0
- data/TODO +8 -0
- data/bin/dtr +124 -0
- data/doc/jamis.rb +591 -0
- data/install.rb +88 -0
- data/lib/dtr.rb +111 -0
- data/lib/dtr/base.rb +160 -0
- data/lib/dtr/raketasks.rb +68 -0
- data/lib/dtr/runner.rb +265 -0
- data/lib/dtr/service_provider.rb +160 -0
- data/lib/dtr/test_unit.rb +278 -0
- data/lib/dtr/test_unit_injection.rb +19 -0
- data/test/base_test.rb +31 -0
- data/test/logger_test.rb +54 -0
- data/test/scenario_tests.rb +166 -0
- data/test/test_helper.rb +17 -0
- data/test/test_unit_test.rb +25 -0
- metadata +89 -0
data/CHANGES
ADDED
data/LICENSE.TXT
ADDED
@@ -0,0 +1,203 @@
|
|
1
|
+
|
2
|
+
Apache License
|
3
|
+
Version 2.0, January 2004
|
4
|
+
http://www.apache.org/licenses/
|
5
|
+
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
7
|
+
|
8
|
+
1. Definitions.
|
9
|
+
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
12
|
+
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
14
|
+
the copyright owner that is granting the License.
|
15
|
+
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
17
|
+
other entities that control, are controlled by, or are under common
|
18
|
+
control with that entity. For the purposes of this definition,
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
20
|
+
direction or management of such entity, whether by contract or
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
23
|
+
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
25
|
+
exercising permissions granted by this License.
|
26
|
+
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
28
|
+
including but not limited to software source code, documentation
|
29
|
+
source, and configuration files.
|
30
|
+
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
32
|
+
transformation or translation of a Source form, including but
|
33
|
+
not limited to compiled object code, generated documentation,
|
34
|
+
and conversions to other media types.
|
35
|
+
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
37
|
+
Object form, made available under the License, as indicated by a
|
38
|
+
copyright notice that is included in or attached to the work
|
39
|
+
(an example is provided in the Appendix below).
|
40
|
+
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
47
|
+
the Work and Derivative Works thereof.
|
48
|
+
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
50
|
+
the original version of the Work and any modifications or additions
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
62
|
+
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
65
|
+
subsequently incorporated within the Work.
|
66
|
+
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
73
|
+
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
79
|
+
where such license applies only to those patent claims licensable
|
80
|
+
by such Contributor that are necessarily infringed by their
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
83
|
+
institute patent litigation against any entity (including a
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
86
|
+
or contributory patent infringement, then any patent licenses
|
87
|
+
granted to You under this License for that Work shall terminate
|
88
|
+
as of the date such litigation is filed.
|
89
|
+
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
92
|
+
modifications, and in Source or Object form, provided that You
|
93
|
+
meet the following conditions:
|
94
|
+
|
95
|
+
(a) You must give any other recipients of the Work or
|
96
|
+
Derivative Works a copy of this License; and
|
97
|
+
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
99
|
+
stating that You changed the files; and
|
100
|
+
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
103
|
+
attribution notices from the Source form of the Work,
|
104
|
+
excluding those notices that do not pertain to any part of
|
105
|
+
the Derivative Works; and
|
106
|
+
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
109
|
+
include a readable copy of the attribution notices contained
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
112
|
+
of the following places: within a NOTICE text file distributed
|
113
|
+
as part of the Derivative Works; within the Source form or
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
115
|
+
within a display generated by the Derivative Works, if and
|
116
|
+
wherever such third-party notices normally appear. The contents
|
117
|
+
of the NOTICE file are for informational purposes only and
|
118
|
+
do not modify the License. You may add Your own attribution
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
121
|
+
that such additional attribution notices cannot be construed
|
122
|
+
as modifying the License.
|
123
|
+
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
125
|
+
may provide additional or different license terms and conditions
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
129
|
+
the conditions stated in this License.
|
130
|
+
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
134
|
+
this License, without any additional terms or conditions.
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
136
|
+
the terms of any separate license agreement you may have executed
|
137
|
+
with Licensor regarding such Contributions.
|
138
|
+
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
141
|
+
except as required for reasonable and customary use in describing the
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
143
|
+
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
153
|
+
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
159
|
+
incidental, or consequential damages of any character arising as a
|
160
|
+
result of this License or out of the use or inability to use the
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
163
|
+
other commercial damages or losses), even if such Contributor
|
164
|
+
has been advised of the possibility of such damages.
|
165
|
+
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
169
|
+
or other liability obligations and/or rights consistent with this
|
170
|
+
License. However, in accepting such obligations, You may act only
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
175
|
+
of your accepting any such warranty or additional liability.
|
176
|
+
|
177
|
+
END OF TERMS AND CONDITIONS
|
178
|
+
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
180
|
+
|
181
|
+
To apply the Apache License to your work, attach the following
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
183
|
+
replaced with your own identifying information. (Don't include
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
185
|
+
comment syntax for the file format. We also recommend that a
|
186
|
+
file or class name and description of purpose be included on the
|
187
|
+
same "printed page" as the copyright notice for easier
|
188
|
+
identification within third-party archives.
|
189
|
+
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
191
|
+
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
193
|
+
you may not use this file except in compliance with the License.
|
194
|
+
You may obtain a copy of the License at
|
195
|
+
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
197
|
+
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
201
|
+
See the License for the specific language governing permissions and
|
202
|
+
limitations under the License.
|
203
|
+
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,203 @@
|
|
1
|
+
|
2
|
+
Apache License
|
3
|
+
Version 2.0, January 2004
|
4
|
+
http://www.apache.org/licenses/
|
5
|
+
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
7
|
+
|
8
|
+
1. Definitions.
|
9
|
+
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
12
|
+
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
14
|
+
the copyright owner that is granting the License.
|
15
|
+
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
17
|
+
other entities that control, are controlled by, or are under common
|
18
|
+
control with that entity. For the purposes of this definition,
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
20
|
+
direction or management of such entity, whether by contract or
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
23
|
+
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
25
|
+
exercising permissions granted by this License.
|
26
|
+
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
28
|
+
including but not limited to software source code, documentation
|
29
|
+
source, and configuration files.
|
30
|
+
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
32
|
+
transformation or translation of a Source form, including but
|
33
|
+
not limited to compiled object code, generated documentation,
|
34
|
+
and conversions to other media types.
|
35
|
+
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
37
|
+
Object form, made available under the License, as indicated by a
|
38
|
+
copyright notice that is included in or attached to the work
|
39
|
+
(an example is provided in the Appendix below).
|
40
|
+
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
47
|
+
the Work and Derivative Works thereof.
|
48
|
+
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
50
|
+
the original version of the Work and any modifications or additions
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
62
|
+
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
65
|
+
subsequently incorporated within the Work.
|
66
|
+
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
73
|
+
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
79
|
+
where such license applies only to those patent claims licensable
|
80
|
+
by such Contributor that are necessarily infringed by their
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
83
|
+
institute patent litigation against any entity (including a
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
86
|
+
or contributory patent infringement, then any patent licenses
|
87
|
+
granted to You under this License for that Work shall terminate
|
88
|
+
as of the date such litigation is filed.
|
89
|
+
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
92
|
+
modifications, and in Source or Object form, provided that You
|
93
|
+
meet the following conditions:
|
94
|
+
|
95
|
+
(a) You must give any other recipients of the Work or
|
96
|
+
Derivative Works a copy of this License; and
|
97
|
+
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
99
|
+
stating that You changed the files; and
|
100
|
+
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
103
|
+
attribution notices from the Source form of the Work,
|
104
|
+
excluding those notices that do not pertain to any part of
|
105
|
+
the Derivative Works; and
|
106
|
+
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
109
|
+
include a readable copy of the attribution notices contained
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
112
|
+
of the following places: within a NOTICE text file distributed
|
113
|
+
as part of the Derivative Works; within the Source form or
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
115
|
+
within a display generated by the Derivative Works, if and
|
116
|
+
wherever such third-party notices normally appear. The contents
|
117
|
+
of the NOTICE file are for informational purposes only and
|
118
|
+
do not modify the License. You may add Your own attribution
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
121
|
+
that such additional attribution notices cannot be construed
|
122
|
+
as modifying the License.
|
123
|
+
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
125
|
+
may provide additional or different license terms and conditions
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
129
|
+
the conditions stated in this License.
|
130
|
+
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
134
|
+
this License, without any additional terms or conditions.
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
136
|
+
the terms of any separate license agreement you may have executed
|
137
|
+
with Licensor regarding such Contributions.
|
138
|
+
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
141
|
+
except as required for reasonable and customary use in describing the
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
143
|
+
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
153
|
+
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
159
|
+
incidental, or consequential damages of any character arising as a
|
160
|
+
result of this License or out of the use or inability to use the
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
163
|
+
other commercial damages or losses), even if such Contributor
|
164
|
+
has been advised of the possibility of such damages.
|
165
|
+
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
169
|
+
or other liability obligations and/or rights consistent with this
|
170
|
+
License. However, in accepting such obligations, You may act only
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
175
|
+
of your accepting any such warranty or additional liability.
|
176
|
+
|
177
|
+
END OF TERMS AND CONDITIONS
|
178
|
+
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
180
|
+
|
181
|
+
To apply the Apache License to your work, attach the following
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
183
|
+
replaced with your own identifying information. (Don't include
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
185
|
+
comment syntax for the file format. We also recommend that a
|
186
|
+
file or class name and description of purpose be included on the
|
187
|
+
same "printed page" as the copyright notice for easier
|
188
|
+
identification within third-party archives.
|
189
|
+
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
191
|
+
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
193
|
+
you may not use this file except in compliance with the License.
|
194
|
+
You may obtain a copy of the License at
|
195
|
+
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
197
|
+
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
201
|
+
See the License for the specific language governing permissions and
|
202
|
+
limitations under the License.
|
203
|
+
|
data/README
ADDED
@@ -0,0 +1,302 @@
|
|
1
|
+
= DTR -- Distributed Test Runner
|
2
|
+
|
3
|
+
Supporting DTR version: 0.0.x
|
4
|
+
|
5
|
+
This package contains DTR, a distributed test runner program for decreasing
|
6
|
+
time of running ruby tests, only supporting Test::Unit ruby testing framework
|
7
|
+
right now.
|
8
|
+
|
9
|
+
DTR has the following features:
|
10
|
+
|
11
|
+
* Run tests in mutli processes or on distributed machines.
|
12
|
+
|
13
|
+
* Hot plug distributed runner agents.
|
14
|
+
|
15
|
+
* Runtime injection, all tests run in same environment.
|
16
|
+
|
17
|
+
DTR works in three parts: DTR Server, Runner Agent and DTR Master.
|
18
|
+
|
19
|
+
* DTR Server is a Rinda Server which allows DRb services and clients to automatically find each other without knowing where they live.
|
20
|
+
|
21
|
+
* Runner Agent is a DRb service hosting on distributed machines to run tests. For using 'fork' to create runner process, Runner Agent can't run on Windows directly.
|
22
|
+
|
23
|
+
* DTR Master is the process finding runner service to run tests and collect test results. It works by loading 'dtr/test_unit_injection.rb' with all test files.
|
24
|
+
|
25
|
+
DTR doesn't synchronize codebase, so you need to consider using synchronize tools
|
26
|
+
(e.g. rsync(http://samba.anu.edu.au/rsync/)) or distributed version control system
|
27
|
+
(e.g. mercurial(http://www.selenic.com/mercurial/wiki/)) to synchronize project
|
28
|
+
files between machines. The distributed version control system Mercurial is cool for
|
29
|
+
synchronizing codebase between machines, see the example "Setup a development build
|
30
|
+
grid".
|
31
|
+
|
32
|
+
== Download
|
33
|
+
|
34
|
+
The latest version of DTR can be found at
|
35
|
+
|
36
|
+
* http://rubyforge.org/projects/dtr/
|
37
|
+
|
38
|
+
== Installation
|
39
|
+
|
40
|
+
=== Normal Installation
|
41
|
+
|
42
|
+
You can install DTR with the following command.
|
43
|
+
|
44
|
+
% ruby install.rb
|
45
|
+
|
46
|
+
from its distribution directory.
|
47
|
+
|
48
|
+
=== GEM Installation
|
49
|
+
|
50
|
+
Download and install DTR with the following.
|
51
|
+
|
52
|
+
gem install --remote dtr
|
53
|
+
|
54
|
+
=== Running the DTR Test Suite
|
55
|
+
|
56
|
+
If you wish to run the unit and functional tests that come with DTR:
|
57
|
+
|
58
|
+
* CD into the top project directory of dtr.
|
59
|
+
* Type the following:
|
60
|
+
|
61
|
+
rake # You need a version of rake installed
|
62
|
+
|
63
|
+
== DTR References
|
64
|
+
|
65
|
+
* DTR Documentation Home: http://dtr.rubyforge.org
|
66
|
+
* DTR Project Page: http://rubyforge.org/projects/dtr
|
67
|
+
* DTR API Documents: http://dtr.rubyforge.org
|
68
|
+
|
69
|
+
== Simple Example
|
70
|
+
|
71
|
+
Once installed, you can run DTR server anywhere:
|
72
|
+
|
73
|
+
% dtr -s
|
74
|
+
|
75
|
+
If you are running Runner Agent on remote machine, please specify the DTR server machine ip:
|
76
|
+
|
77
|
+
% dtr -s --server_address dtr_server_ip
|
78
|
+
|
79
|
+
After server started, you can run DTR runner agent at your project directory as follows:
|
80
|
+
|
81
|
+
% dtr --server_address dtr_server_ip -r runner_name
|
82
|
+
|
83
|
+
Type "dtr --help" for an up-to-date option summary.
|
84
|
+
Invoking <tt>dtr</tt> without any options causes dtr to show help too.
|
85
|
+
|
86
|
+
Most of time your project test suite need setup environment before run tests, you
|
87
|
+
can set setup command by option '--setup', for example:
|
88
|
+
|
89
|
+
% dtr --server_address dtr_server_ip -r runner1 --setup "rake db:test:prepare"
|
90
|
+
|
91
|
+
At last, you need to add 'dtr/test_unit_injection.rb' into test_files of your test
|
92
|
+
task in your Rakefile, and for load it, you also need add dtr lib path:
|
93
|
+
|
94
|
+
require 'dtr'
|
95
|
+
|
96
|
+
DTR.broadcast_list = ['dtr server ip']
|
97
|
+
|
98
|
+
Rake::TestTask.new(:dtr_tests) do |t|
|
99
|
+
t.libs << DTR.lib_path
|
100
|
+
t.test_files = FileList['dtr/test_unit_injection.rb', 'test/*test.rb']
|
101
|
+
t.warning = false
|
102
|
+
t.verbose = false
|
103
|
+
end
|
104
|
+
|
105
|
+
In the case above we changed dtr broadcast list for listening remote dtr server.
|
106
|
+
And you also can use *DTR.port = 1234* to change the port listening. These two
|
107
|
+
options would be cached in the directory running the test or any other dtr processes
|
108
|
+
(e.g. dtr runner agent or dtr server).
|
109
|
+
|
110
|
+
== Run tests in multi-processes on one machine
|
111
|
+
|
112
|
+
For running Runner in multi-processes, you need install gem 'daemons'.
|
113
|
+
The following is the test task example in the rake file:
|
114
|
+
|
115
|
+
require 'dtr/raketasks'
|
116
|
+
|
117
|
+
DTR::MPTask.new :test do |t|
|
118
|
+
t.test_files = FileList['test/*test.rb']
|
119
|
+
t.processes = 2 #default is 2
|
120
|
+
end
|
121
|
+
|
122
|
+
== Setup a development build grid
|
123
|
+
|
124
|
+
This example is a build grid shared within developers to run unit tests
|
125
|
+
before commit code. We'll use Mercurial to synchronize code between Runner
|
126
|
+
Agent machines and developer machine.
|
127
|
+
|
128
|
+
=== Background
|
129
|
+
|
130
|
+
Suppose I am a developer working on a rails project pet_store checked out
|
131
|
+
at '~/pet_store'. I have a MacBook called M1 and another 2 Mac-minis called
|
132
|
+
M2 and M3. My plan is distributing tests running on M1 to M2 and M3 before
|
133
|
+
commit code. M3 also will be DTR Server. All machines are accessable in
|
134
|
+
local network and IPs are M1_IP, M2_IP and M3_IP. Mercurial and DTR are
|
135
|
+
installed on all machines. And for running dtr runner agent in daemons mode,
|
136
|
+
you need install gem daemons. The test environment will be running on Mysql.
|
137
|
+
All machines are installed Mysql accessed by the following database.yml
|
138
|
+
configuration:
|
139
|
+
|
140
|
+
development:
|
141
|
+
database: pet_store_development
|
142
|
+
adapter: mysql
|
143
|
+
username: root
|
144
|
+
password:
|
145
|
+
host: localhost
|
146
|
+
test:
|
147
|
+
database: pet_store_test
|
148
|
+
adapter: mysql
|
149
|
+
username: root
|
150
|
+
password:
|
151
|
+
host: localhost
|
152
|
+
|
153
|
+
=== DTR Server
|
154
|
+
|
155
|
+
* Start DTR Server on M3: dtr -s -a M3_IP.
|
156
|
+
|
157
|
+
=== Setup Mercurial repository on M1
|
158
|
+
|
159
|
+
* Init Mercurial repository in '~/pet_store' directory: hg init
|
160
|
+
* Edit .hgignore file to ignore files don't need while running tests. In this example, we will ignore files: db/schema.rb, .dtr_env_pstore, dtr_runners.pid and dtr_server*; and directories: public, tmp and log.
|
161
|
+
* Commit .hgignore and then commit code into Mercurial repository.
|
162
|
+
* Start 'hg serve' in '~/pet_store', the default port would be 8000. We'll use the default port in this example.
|
163
|
+
* We'll clone the repository to M2 and M3 later.
|
164
|
+
|
165
|
+
=== Build Script
|
166
|
+
|
167
|
+
* Add an environment variable on all machines: export DEV_BUILD_SERVER=M3_IP
|
168
|
+
* Add an environment variable on development machine M1: export DTR_MASTER_ENV=http: //M1_IP:8000/pet_store. The environment variable DTR_MASTER_ENV would be copied to all DTR Runner Agent for sharing information between DTR Master machine and DTR Runner Agents.
|
169
|
+
* Create a rake file at '~/pet_store' directory called: dtr_tasks.rake
|
170
|
+
|
171
|
+
DEV_BUILD_SERVER = ENV['DEV_BUILD_SERVER']
|
172
|
+
DEV_REPOSITORY_URL = ENV['DTR_MASTER_ENV']
|
173
|
+
|
174
|
+
task :dtr => ['hg:check', 'dtr:uf']
|
175
|
+
|
176
|
+
namespace :hg do
|
177
|
+
task :reinit do
|
178
|
+
Dir.glob("*").each do |f|
|
179
|
+
#remove all files except files start with 'dtr_' including dtr runner pid file and current file dtr_tasks.rake
|
180
|
+
next if f =~ /^dtr_/
|
181
|
+
FileUtils.rm_rf(f)
|
182
|
+
end
|
183
|
+
FileUtils.rm_rf(".hg")
|
184
|
+
FileUtils.rm_rf(".hgignore")
|
185
|
+
puts %x[hg init]
|
186
|
+
puts %x[hg pull -u -y #{DEV_REPOSITORY_URL}]
|
187
|
+
puts %x[mkdir tmp]
|
188
|
+
puts %x[mkdir log]
|
189
|
+
end
|
190
|
+
task :check do
|
191
|
+
http = Net::HTTP.new("localhost", "8000")
|
192
|
+
begin
|
193
|
+
http.get("/")
|
194
|
+
rescue Exception
|
195
|
+
raise "Mercurial server is not running!"
|
196
|
+
end
|
197
|
+
|
198
|
+
raise "Please commit changes into Mercurial repository" if %x[hg st] =~ /.+/
|
199
|
+
end
|
200
|
+
end
|
201
|
+
|
202
|
+
namespace :dtr do
|
203
|
+
task :runner_agent do
|
204
|
+
puts %x[dtr -R;dtr -r runner -a '#{DEV_BUILD_SERVER}' -i 'rake --rakefile dtr_tasks.rake hg:reinit;rake db:migrate db:test:prepare' -D]
|
205
|
+
end
|
206
|
+
|
207
|
+
require 'dtr'
|
208
|
+
|
209
|
+
DTR.broadcast_list = [DEV_BUILD_SERVER]
|
210
|
+
|
211
|
+
DTR::MPTask.new(:uf) do |t|
|
212
|
+
t.libs << "test"
|
213
|
+
t.test_files = FileList['test/unit/**/*test.rb', 'test/functional/**/*test.rb']
|
214
|
+
t.processes = ENV['P'] || 1
|
215
|
+
t.runner_options = "-a '#{DEV_BUILD_SERVER}' -i 'rake db:migrate db:test:prepare'"
|
216
|
+
t.start_server = false
|
217
|
+
t.verbose = false
|
218
|
+
end
|
219
|
+
end
|
220
|
+
|
221
|
+
* The script above can re-init Mercurial repository. Runner Agent will run the 'hg:reinit' task before start Runner(see the 'runner_agent' task in the script above), so that Runner Agent can support any developer's codebase to run tests.
|
222
|
+
* Commit dtr_tasks.rake into Mercurial repository.
|
223
|
+
|
224
|
+
=== Runner Agent
|
225
|
+
|
226
|
+
* Clone repository from M1 to M2 in home directory: hg clone http: //M1_IP:8000/pet_store
|
227
|
+
* Start runner agent in the directory ~/pet_store on M2: rake --rakefile dtr_tasks.rake dtr:runner_agent
|
228
|
+
* Start runner agent on M3 same with above.
|
229
|
+
|
230
|
+
=== Run DTR Master on M1
|
231
|
+
|
232
|
+
* Commit all changes into Mercurial
|
233
|
+
* rake --rakefile dtr_tasks.rake dtr
|
234
|
+
* After you started the DTR Master, you can type the following to monitor the DTR Server status: dtr -a $DEV_BUILD_SERVER -m
|
235
|
+
* For output into console, open the debug option: dtr -a $DEV_BUILD_SERVER -d -m
|
236
|
+
|
237
|
+
== Credits
|
238
|
+
|
239
|
+
[<b>Josh Price</b>] For fixing tests packer in release 0.0.1.
|
240
|
+
|
241
|
+
[<b>Wang Pengchao</b>] For sharing lots of ideas.
|
242
|
+
|
243
|
+
[<b>Barrow H Kwan</b>] For patch of specifying DTR server port.
|
244
|
+
|
245
|
+
[<b>Mingle team</b>(http://studios.thoughtworks.com/mingle-project-intelligence)] For making all these happen.
|
246
|
+
|
247
|
+
== License
|
248
|
+
|
249
|
+
DTR is available under an Apache License Version 2.
|
250
|
+
|
251
|
+
== Support
|
252
|
+
|
253
|
+
The DTR homepage is http://dtr.rubyforge.org. You can find the DTR
|
254
|
+
RubyForge page at http://rubyforge.org/projects/dtr or Google Code
|
255
|
+
project at http://code.google.com/p/dtrunner.
|
256
|
+
|
257
|
+
Feel free to submit commits or feature requests. If you send a patch,
|
258
|
+
remember to update the corresponding unit tests. If fact, I prefer
|
259
|
+
new feature to be submitted in the form of new unit tests.
|
260
|
+
|
261
|
+
For other information, feel free to ask on the ruby-talk mailing list
|
262
|
+
or contact mailto:swing1979@gmail.com.
|
263
|
+
|
264
|
+
== Usage
|
265
|
+
|
266
|
+
DTR client is invoked from the command line using:
|
267
|
+
|
268
|
+
% dtr [<em>options</em> ...]
|
269
|
+
|
270
|
+
=== Options are:
|
271
|
+
|
272
|
+
-p, --port PORT Port number DTR will listen to. Default is 3344.
|
273
|
+
-r runner1_name,runner2_name Start DTR test runner agent with unique runner names.
|
274
|
+
-a, --server_address ADDRESS Specify dtr server address, domain name or ip address, e.g. 192.168.0.1. Default is 'localhost'.
|
275
|
+
-i, --setup COMMAND Set command for initializing test runner test environment, e.g. 'rake db:test:prepare'. Default is do nothing.
|
276
|
+
-m, --monitor Monitor the status of the dtr rinda server, e.g. dtr -a 10.11.1.2 -m
|
277
|
+
-c, --clean_server Clean server environment, shutdown all runners registered.
|
278
|
+
-b, --be_silent Only show error messages
|
279
|
+
-s, --server Start DTR service server. There must be a DTR server running.
|
280
|
+
-D, --daemon Start server/runners in daemon mode. Gem 'daemons' must be installed
|
281
|
+
-S, --stop_server Stop server run in daemon mode.
|
282
|
+
-R, --stop_runners Stop runners run in daemon mode.
|
283
|
+
-d, --debug output debug log
|
284
|
+
-v, --version Show version
|
285
|
+
-h, --help Show this help doc
|
286
|
+
|
287
|
+
Type "dtr --help" for an up-to-date option summary.
|
288
|
+
|
289
|
+
= Other stuff
|
290
|
+
|
291
|
+
Author:: Li Xiao <swing1979@gmail.com>
|
292
|
+
Requires:: Ruby 1.8.5 or later
|
293
|
+
License:: Copyright 2007-2008 by Li Xiao.
|
294
|
+
Released under an Apache License 2. See the LICENSE file
|
295
|
+
included in the distribution.
|
296
|
+
|
297
|
+
== Warranty
|
298
|
+
|
299
|
+
This software is provided "as is" and without any express or
|
300
|
+
implied warranties, including, without limitation, the implied
|
301
|
+
warranties of merchantibility and fitness for a particular
|
302
|
+
purpose.
|