poolparty 0.2.6 → 0.2.18
Sign up to get free protection for your applications and to get access to all the features.
- data/Manifest.txt +123 -4
- data/PostInstall.txt +2 -1
- data/bin/cloud +16 -7
- data/bin/cloud-provision +9 -5
- data/bin/cloud-run +19 -0
- data/bin/cloud-ssh +2 -7
- data/bin/cloud-start +2 -1
- data/bin/pool +3 -3
- data/bin/server-build-messenger +20 -0
- data/bin/server-fire-cmd +14 -0
- data/bin/server-get-load +29 -0
- data/bin/server-list-active +25 -0
- data/bin/server-list-responding +24 -0
- data/bin/server-rerun +24 -0
- data/bin/server-start-master +27 -0
- data/bin/server-start-node +33 -0
- data/config/requirements.rb +1 -1
- data/erl_crash.dump +8409 -0
- data/lib/erlang/messenger/Emakefile +1 -0
- data/lib/erlang/messenger/Makefile +15 -0
- data/lib/erlang/messenger/README +5 -0
- data/lib/erlang/messenger/Rakefile +60 -0
- data/lib/erlang/messenger/control +11 -0
- data/lib/erlang/messenger/ebin/master.app +19 -0
- data/lib/erlang/messenger/ebin/master_app.beam +0 -0
- data/lib/erlang/messenger/ebin/node.app +19 -0
- data/lib/erlang/messenger/ebin/node_app.beam +0 -0
- data/lib/erlang/messenger/ebin/packager.app +19 -0
- data/lib/erlang/messenger/ebin/pm_client.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_cluster.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_event_handler.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_master.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_master_rel-0.1.rel +1 -0
- data/lib/erlang/messenger/ebin/pm_master_supervisor.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_node.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_node_rel-0.1.rel +1 -0
- data/lib/erlang/messenger/ebin/pm_node_supervisor.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_packager.beam +0 -0
- data/lib/erlang/messenger/ebin/utils.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/AUTHORS +2 -0
- data/lib/erlang/messenger/lib/eunit/CHANGELOG +14 -0
- data/lib/erlang/messenger/lib/eunit/COPYING +504 -0
- data/lib/erlang/messenger/lib/eunit/Makefile +28 -0
- data/lib/erlang/messenger/lib/eunit/NOTES +276 -0
- data/lib/erlang/messenger/lib/eunit/README +3 -0
- data/lib/erlang/messenger/lib/eunit/doc/edoc-info +3 -0
- data/lib/erlang/messenger/lib/eunit/doc/erlang.png +0 -0
- data/lib/erlang/messenger/lib/eunit/doc/eunit.html +172 -0
- data/lib/erlang/messenger/lib/eunit/doc/index.html +17 -0
- data/lib/erlang/messenger/lib/eunit/doc/modules-frame.html +12 -0
- data/lib/erlang/messenger/lib/eunit/doc/overview-summary.html +984 -0
- data/lib/erlang/messenger/lib/eunit/doc/overview.edoc +980 -0
- data/lib/erlang/messenger/lib/eunit/doc/packages-frame.html +11 -0
- data/lib/erlang/messenger/lib/eunit/doc/stylesheet.css +55 -0
- data/lib/erlang/messenger/lib/eunit/ebin/autoload.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/code_monitor.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit.app +21 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit.appup +1 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_autoexport.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_data.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_lib.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_proc.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_serial.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_server.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_striptests.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_test.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_tests.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/eunit_tty.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/ebin/file_monitor.beam +0 -0
- data/lib/erlang/messenger/lib/eunit/examples/eunit_examples.erl +339 -0
- data/lib/erlang/messenger/lib/eunit/examples/fib.erl +19 -0
- data/lib/erlang/messenger/lib/eunit/examples/tests.txt +1 -0
- data/lib/erlang/messenger/lib/eunit/include/eunit.hrl +313 -0
- data/lib/erlang/messenger/lib/eunit/src/Makefile +46 -0
- data/lib/erlang/messenger/lib/eunit/src/autoload.erl +388 -0
- data/lib/erlang/messenger/lib/eunit/src/code_monitor.erl +243 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit.app.src +21 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit.appup.src +1 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit.erl +196 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_autoexport.erl +102 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_data.erl +798 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_internal.hrl +48 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_lib.erl +682 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_proc.erl +552 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_serial.erl +157 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_server.erl +340 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_striptests.erl +64 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_test.erl +334 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_tests.erl +45 -0
- data/lib/erlang/messenger/lib/eunit/src/eunit_tty.erl +272 -0
- data/lib/erlang/messenger/lib/eunit/src/file_monitor.erl +409 -0
- data/lib/erlang/messenger/lib/eunit/sys.config +9 -0
- data/lib/erlang/messenger/lib/eunit/vsn.mk +1 -0
- data/lib/erlang/messenger/pm_master_rel-0.1.boot +0 -0
- data/lib/erlang/messenger/pm_master_rel-0.1.script +242 -0
- data/lib/erlang/messenger/pm_node_rel-0.1.boot +0 -0
- data/lib/erlang/messenger/pm_node_rel-0.1.script +242 -0
- data/lib/erlang/messenger/src/master_app.erl +39 -0
- data/lib/erlang/messenger/src/node_app.erl +39 -0
- data/lib/erlang/messenger/src/pm_client.erl +19 -0
- data/lib/erlang/messenger/src/pm_cluster.erl +57 -0
- data/lib/erlang/messenger/src/pm_event_handler.erl +21 -0
- data/lib/erlang/messenger/src/pm_master.erl +118 -0
- data/lib/erlang/messenger/src/pm_master_supervisor.erl +40 -0
- data/lib/erlang/messenger/src/pm_node.erl +124 -0
- data/lib/erlang/messenger/src/pm_node_supervisor.erl +40 -0
- data/lib/erlang/messenger/src/pm_packager.erl +73 -0
- data/lib/erlang/messenger/src/utils.erl +38 -0
- data/lib/poolparty/base_packages/haproxy.rb +9 -2
- data/lib/poolparty/base_packages/heartbeat.rb +40 -28
- data/lib/poolparty/base_packages/poolparty.rb +39 -16
- data/lib/poolparty/base_packages/ruby.rb +2 -3
- data/lib/poolparty/config/allowed_commands.yml +1 -0
- data/lib/poolparty/core/array.rb +5 -2
- data/lib/poolparty/core/hash.rb +16 -2
- data/lib/poolparty/core/string.rb +9 -2
- data/lib/poolparty/core/symbol.rb +2 -2
- data/lib/poolparty/dependency_resolutions/base.rb +12 -0
- data/lib/poolparty/dependency_resolutions/puppet.rb +49 -0
- data/lib/poolparty/exceptions/UnacceptableCommand.rb +5 -0
- data/lib/poolparty/helpers/console.rb +3 -2
- data/lib/poolparty/helpers/display.rb +3 -3
- data/lib/poolparty/helpers/messenger.rb +29 -0
- data/lib/poolparty/helpers/optioner.rb +6 -2
- data/lib/poolparty/helpers/provisioner_base.rb +18 -11
- data/lib/poolparty/helpers/provisioners/master.rb +24 -22
- data/lib/poolparty/helpers/provisioners/slave.rb +8 -4
- data/lib/poolparty/modules/definable_resource.rb +1 -0
- data/lib/poolparty/modules/file_writer.rb +11 -10
- data/lib/poolparty/modules/method_missing_sugar.rb +1 -1
- data/lib/poolparty/modules/pretty_printer.rb +11 -11
- data/lib/poolparty/modules/resourcing_dsl.rb +61 -0
- data/lib/poolparty/monitors/base_monitor.rb +17 -3
- data/lib/poolparty/monitors/monitors/cpu_monitor.rb +15 -0
- data/lib/poolparty/monitors/monitors/memory_monitor.rb +23 -0
- data/lib/poolparty/net/remote_instance.rb +6 -1
- data/lib/poolparty/net/remoter.rb +23 -5
- data/lib/poolparty/net/remoter_base.rb +5 -1
- data/lib/poolparty/plugins/git.rb +22 -24
- data/lib/poolparty/pool/base.rb +22 -6
- data/lib/poolparty/pool/cloud.rb +28 -4
- data/lib/poolparty/pool/custom_resource.rb +6 -6
- data/lib/poolparty/pool/loggable.rb +3 -0
- data/lib/poolparty/pool/pool.rb +1 -1
- data/lib/poolparty/pool/resource.rb +58 -94
- data/lib/poolparty/pool/resources/class_package.rb +6 -6
- data/lib/poolparty/pool/resources/conditional.rb +5 -1
- data/lib/poolparty/pool/resources/exec.rb +6 -2
- data/lib/poolparty/pool/resources/gem.rb +22 -8
- data/lib/poolparty/pool/resources/remote_file.rb +5 -1
- data/lib/poolparty/pool/resources/symlink.rb +25 -0
- data/lib/poolparty/pool/resources/variable.rb +8 -7
- data/lib/poolparty/pool/tmp/.ppkeys +3 -0
- data/lib/poolparty/pool/tmp/happydayz +1 -0
- data/lib/poolparty/pool/tmp/install_master.sh +33 -0
- data/lib/poolparty/pool/tmp/pool.spec +11 -0
- data/lib/poolparty/pool/tmp/poolparty.pp +600 -0
- data/lib/poolparty/pool/tmp/tc-instances.list +1 -0
- data/lib/poolparty/templates/cib.xml +54 -0
- data/lib/poolparty/templates/ha.cf +12 -3
- data/lib/poolparty/templates/haproxy.conf +3 -3
- data/lib/poolparty/templates/haresources +3 -0
- data/lib/poolparty/templates/poolparty.monitor +14 -0
- data/lib/poolparty/templates/puppet.conf +3 -4
- data/lib/poolparty/version.rb +1 -1
- data/lib/poolparty.rb +9 -6
- data/poolparty.gemspec +7 -6
- data/setup.rb +3 -3
- data/spec/poolparty/bin/console_spec.rb +1 -1
- data/spec/poolparty/core/array_spec.rb +5 -0
- data/spec/poolparty/core/hash_spec.rb +19 -1
- data/spec/poolparty/core/string_spec.rb +13 -0
- data/spec/poolparty/dependency_resolutions/base_spec.rb +11 -0
- data/spec/poolparty/helpers/messenger_spec.rb +14 -0
- data/spec/poolparty/helpers/optioner_spec.rb +2 -1
- data/spec/poolparty/helpers/provisioner_base_spec.rb +1 -1
- data/spec/poolparty/helpers/provisioners/master_spec.rb +2 -2
- data/spec/poolparty/helpers/provisioners/slave_spec.rb +3 -3
- data/spec/poolparty/modules/file_writer_spec.rb +9 -0
- data/spec/poolparty/monitors/base_monitor_spec.rb +19 -0
- data/spec/poolparty/monitors/monitors/cpu_monitor_spec.rb +17 -0
- data/spec/poolparty/net/remote_instance_spec.rb +6 -1
- data/spec/poolparty/net/remote_spec.rb +51 -42
- data/spec/poolparty/net/remoter_spec.rb +2 -1
- data/spec/poolparty/plugins/git_spec.rb +2 -2
- data/spec/poolparty/pool/base_spec.rb +20 -2
- data/spec/poolparty/pool/cloud_spec.rb +30 -1
- data/spec/poolparty/pool/custom_resource_spec.rb +2 -2
- data/spec/poolparty/pool/plugin_spec.rb +4 -4
- data/spec/poolparty/pool/pool_spec.rb +1 -1
- data/spec/poolparty/pool/resource_spec.rb +66 -0
- data/spec/poolparty/pool/resources/gem_spec.rb +29 -3
- data/spec/poolparty/pool/resources/symlink_spec.rb +22 -0
- data/spec/poolparty/pool/resources/variable_spec.rb +4 -0
- data/spec/poolparty/spec_helper.rb +5 -0
- data/tasks/cloud.rake +0 -54
- data/tasks/development.rake +0 -12
- data/tasks/ec2.rake +1 -16
- data/tasks/instance.rake +0 -61
- data/test_manifest.pp +286 -166
- data/website/index.html +5 -5
- data/website/index.txt +3 -3
- metadata +137 -8
- data/bin/pool-start-monitor +0 -1
- data/lib/erlang/eb_server.erl +0 -27
- data/lib/poolparty/plugins/gem_package.rb +0 -17
- data/spec/poolparty/modules/tmp/willy/nilly.rb +0 -1
@@ -0,0 +1,276 @@
|
|
1
|
+
|
2
|
+
EUnit Developer notebook
|
3
|
+
========================
|
4
|
+
|
5
|
+
Concepts and features
|
6
|
+
---------------------
|
7
|
+
|
8
|
+
- Separation of tests and test runners (different ways of reporting)
|
9
|
+
|
10
|
+
* Tests are represented by data structures
|
11
|
+
* Traversal and execution are separated
|
12
|
+
* TODO: Cannot enumerate all tests in advance for really large sets
|
13
|
+
|
14
|
+
- Test engine as a producer/iterator: run next, step back, repeat...
|
15
|
+
|
16
|
+
* Iterators working (reverse/single stepping currently not used)
|
17
|
+
* TODO: Need to be able to stop after N failures
|
18
|
+
|
19
|
+
- Test module - a container (as in 'eunit:run(M)'); automatic test collection
|
20
|
+
|
21
|
+
* Works; a module name can be used to represent its set of tests.
|
22
|
+
|
23
|
+
- Single tests (exported nullary functions, to be called directly)
|
24
|
+
|
25
|
+
* Works; has drawbacks (no comments, context, or order, many
|
26
|
+
functions)
|
27
|
+
|
28
|
+
- Abstraction of tests, for reuse
|
29
|
+
|
30
|
+
* Tests are just nullary funs; this is both simple and powerful
|
31
|
+
* You can use 'fun name/arity' or 'fun module:name/arity' for sharing code
|
32
|
+
* Generator functions are used to create specialized test funs
|
33
|
+
|
34
|
+
- Executing a test by calling directly should have observable
|
35
|
+
failure/success, and tests should not in themselves output test
|
36
|
+
results to console or otherwise
|
37
|
+
|
38
|
+
* Tests succeed by returning properly (any return value)
|
39
|
+
* Tests fail by throwing an exception (any exception)
|
40
|
+
|
41
|
+
- It should be possible to run single tests without eunit runtime support
|
42
|
+
|
43
|
+
* Just apply a test function to an empty argument list and see if it
|
44
|
+
throws an exception or not
|
45
|
+
* More complex test representations (grouping, setup/teardown etc.)
|
46
|
+
need eunit support functions
|
47
|
+
|
48
|
+
- It should be possible to write tests without requiring eunit headers
|
49
|
+
|
50
|
+
* Using plain tuples, funs, atoms, and lists to represent tests; not
|
51
|
+
more difficult, just less convenient.
|
52
|
+
|
53
|
+
- Tests are identified by: module/sourcefile, test function name, and
|
54
|
+
line number (if available)
|
55
|
+
|
56
|
+
* This is also used in listings of test sets
|
57
|
+
* Funs have useful metadata, which allows most of the identifying
|
58
|
+
info to be extracted automatically
|
59
|
+
|
60
|
+
- Test functions must be identified as either directly callable or as
|
61
|
+
returning one or more test representations (the latter is referred to
|
62
|
+
as a "generator"). We cannot just try to call any function and check
|
63
|
+
the result - it would not be possible to _collect_ tests without
|
64
|
+
accidentally _executing_ tests in that case. So, the simplest form of
|
65
|
+
test generator function should return a nullary fun. This can be
|
66
|
+
tested directly and easily by a user.
|
67
|
+
|
68
|
+
* Using a '_test_' suffix (as opposed to a '_test' suffix) for test
|
69
|
+
generator functions (that return test *representations*) is a good
|
70
|
+
idea, since it makes it easy to accomodate both styles of writing
|
71
|
+
tests, does not break existing code, allows both types of functions
|
72
|
+
to be automatically detected, and makes it easy to write wrapper
|
73
|
+
functions. The underscore just before the opening parenthesis makes
|
74
|
+
it more visible than most other variants.
|
75
|
+
|
76
|
+
- Conditional compilation of test code
|
77
|
+
|
78
|
+
* Defining the NOTEST macro is used to disable testing code; this is
|
79
|
+
used by all the eunit header files.
|
80
|
+
* Testing can be disabled by default by including eunit_off.hrl
|
81
|
+
instead of eunit.hrl, or before any other eunit header file; then,
|
82
|
+
defining the TEST macro externally will enable the testing code.
|
83
|
+
The same effect is achieved by defining NOTEST before including
|
84
|
+
eunit.hrl or any other eunit header file, but using eunit_off.hrl
|
85
|
+
is always independent of the actual macro name used for control.
|
86
|
+
|
87
|
+
- Exporting test functions manually is annoying and easy to forget
|
88
|
+
- Decorating a normal module with common eunit entry functions
|
89
|
+
|
90
|
+
* Including eunit.hrl inserts a parse transform (unless NOTEST or
|
91
|
+
EUNIT_NOAUTO is defined) which automatically exports functions
|
92
|
+
identified as test functions with the proper suffixes and arity,
|
93
|
+
and adds a test/0 function to the module (unless it exists).
|
94
|
+
|
95
|
+
- Label of a single test
|
96
|
+
|
97
|
+
* {"...", Test}, also works for groups.
|
98
|
+
|
99
|
+
- Context of a single test; set up and tear down of context; multiple
|
100
|
+
tests within same context (single set up/tear down)
|
101
|
+
|
102
|
+
* {setup, Setup, Teardown, Generator}
|
103
|
+
* {setup, Setup, Generator} works as a simple let-binding
|
104
|
+
|
105
|
+
- Multiple tests using same context (individual set up/tear down)
|
106
|
+
|
107
|
+
* {foreach, Setup, Teardown, [Generator]}
|
108
|
+
{foreach1, Setup, Teardown, [{Arg, Generator}]}
|
109
|
+
|
110
|
+
- Aggregation of tests in an order-dependent sequence; aggregation of
|
111
|
+
tests in explicitly parallel sets
|
112
|
+
|
113
|
+
* {inorder, T} | {inparallel, T}
|
114
|
+
|
115
|
+
- Aggregation of tests in unspecified-order sets
|
116
|
+
|
117
|
+
* Deep lists represent generic test sets
|
118
|
+
|
119
|
+
- Test suites: label of a test suite, composition of test suites
|
120
|
+
|
121
|
+
* Deep lists and {"label", DeepList} work fine for this purpose
|
122
|
+
|
123
|
+
- Defining test suites without modifying code or creating new modules.
|
124
|
+
|
125
|
+
* This does not create new tests - just select specific modules or
|
126
|
+
functions. If there is need for expressiveness beyond a simple list
|
127
|
+
of constant terms (no funs), it should be put in a module. Hence, a
|
128
|
+
facility for "consulting" files should be sufficient.
|
129
|
+
* Works (simply writing "filename" or {file, "filename"}).
|
130
|
+
|
131
|
+
- Extra header files for better macro namespace separation (eunit_...)
|
132
|
+
|
133
|
+
* Seems to be overkill - the leading underscore in the normal macros
|
134
|
+
lessens the need for such double definitions
|
135
|
+
|
136
|
+
- Running tests in parallel
|
137
|
+
|
138
|
+
* Works (also running N tests at a time)
|
139
|
+
* TODO: Restructure to start new job as soon as slot is available
|
140
|
+
|
141
|
+
- Running a test or set of tests in a new process (like setup/teardown)
|
142
|
+
|
143
|
+
* Works
|
144
|
+
|
145
|
+
- Running tests on a separate (existing) node
|
146
|
+
|
147
|
+
* Implemented as {spawn, Node, Tests}: assuming a specific node
|
148
|
+
exists, run a set of tests on that node, rather than locally, the
|
149
|
+
main idea being that a number of test sets could be run in parallel
|
150
|
+
on separate machines (and maybe none are run locally)
|
151
|
+
|
152
|
+
- Running OS commands, testing output and result values
|
153
|
+
|
154
|
+
* Works; output is normalized to LF only for linebreaks on all platforms
|
155
|
+
* TODO: Better Windows support (not much tested)
|
156
|
+
* TODO: Is it possible to capture stderr separately somehow?
|
157
|
+
|
158
|
+
- Starting one or more additional nodes to run tests or suites on
|
159
|
+
|
160
|
+
* {node, foo@bar.baz, Instantiator}
|
161
|
+
* {node, foo, Instantiator}
|
162
|
+
|
163
|
+
- Whole-application testing (using .app files?)
|
164
|
+
|
165
|
+
* {application, AppName}
|
166
|
+
* {file, AppFile}
|
167
|
+
|
168
|
+
- Identification of tests within a test set (e.g., which succeeded,
|
169
|
+
which failed, repeating selected tests or groups of tests, etc.)
|
170
|
+
|
171
|
+
* The numbering scheme in listings take care of this point
|
172
|
+
|
173
|
+
- Running EUnit from command line, as a standalone tool
|
174
|
+
|
175
|
+
* TODO: Command line interface similar to that of edoc
|
176
|
+
|
177
|
+
- Open source (licensed under the GNU Lesser General Public Licence)
|
178
|
+
|
179
|
+
* Header files can be used without tainting, according to LGPL
|
180
|
+
|
181
|
+
- Marking tests as known failures, for handling known bugs
|
182
|
+
|
183
|
+
* TODO: Known-failure is necessary to avoid writing "inverted-logic" tests
|
184
|
+
* TODO: Is it possible to handle known timout/setup failures?
|
185
|
+
|
186
|
+
- Diagnostic tests which never fail, but may cause warnings
|
187
|
+
|
188
|
+
Assorted notes which may or may not be useful, e.g. for documentation
|
189
|
+
---------------------------------------------------------------------
|
190
|
+
|
191
|
+
Tests for exported functions of a module should preferably be in a
|
192
|
+
separate module. This is good in many ways, but mainly boils down to
|
193
|
+
that modifying test code should not have to imply modifying source code,
|
194
|
+
and vice versa. At the same time, it should be possible for a module to
|
195
|
+
export test functions for private functions, and to have these tests
|
196
|
+
conditionally compiled (use -ifdef(EUNIT) or -ifdef(TEST) for this).
|
197
|
+
|
198
|
+
Pyunit uses 'failIf' and 'failUnless' as standard test names, and
|
199
|
+
'assert' as a synonym for 'failUnless'. I have settled on 'assert' and
|
200
|
+
'assertNot' as the standard names. Maybe I'll add 'failUnless' and
|
201
|
+
'failIf' as synonyms, if users ask for it.
|
202
|
+
|
203
|
+
Junit/Pyunit get a lot of context embedding for free due to the object
|
204
|
+
oriented languages (using class members and inheritance); in Erlang,
|
205
|
+
context must be passed to tests as arguments or through local variable
|
206
|
+
bindings if there are multiple tests within a function clause. This is
|
207
|
+
particularly important for reuse of tests with small variations. To be
|
208
|
+
able to instantiate the environment of a set of tests when executing a
|
209
|
+
setup, the setup must be a function which returns the test set and the
|
210
|
+
cleanup function.
|
211
|
+
|
212
|
+
A list of tests represents an order-independent set. Usually, the tests
|
213
|
+
will be run in order, but it is not required and tests may also be
|
214
|
+
executed in parallel if they are included in an 'inparallel'-context.
|
215
|
+
Labeling a set of tests does not change its meaning in any way.
|
216
|
+
|
217
|
+
Wrapping a set of tests in a 'setup' implies that the setup is executed,
|
218
|
+
then _all_ the tests (those returned by the generator fun) are executed,
|
219
|
+
and finally the cleanup is executed regardless of whether any tests
|
220
|
+
failed or not. If the setup itself failed, the whole test set _and_ the
|
221
|
+
cleanup is skipped (there is no setup-result that can be passed to the
|
222
|
+
cleanup).
|
223
|
+
|
224
|
+
Wrapping a (deep) list of generators in a 'foreach' is equivalent to
|
225
|
+
wrapping each individual generator in the list in a corresponding
|
226
|
+
'setup', regardless of nesting depth. E.g., foreach(a, [foreach(b, [t1,
|
227
|
+
t2]), foreach(c, [t3, t4])]) is equivalent to [setup(a, setup(b, t1)),
|
228
|
+
setup(a, setup(b, t2)), setup(a, setup(c, t3)), setup(a, setup(c, t4))].
|
229
|
+
Note that 'foreach' does not distribute over 'setup', since the nesting
|
230
|
+
level of 'setup' must be preserved.
|
231
|
+
|
232
|
+
While a plain 'foreach' can be done over any set of generators, a
|
233
|
+
'foreach1' requires that there is a pairing of argument+generator for
|
234
|
+
each element.
|
235
|
+
|
236
|
+
See the file eunit_data.erl for a description of test representations.
|
237
|
+
|
238
|
+
Lists of tests/generators/arg-generator-pairs can all be deep, but every
|
239
|
+
sublist must be a proper list, i.e., nil-terminated.
|
240
|
+
|
241
|
+
Test Set Traversal Operations (traversal only - no execution here):
|
242
|
+
|
243
|
+
Init: create iterator from test representation.
|
244
|
+
Next: the most common operation - get the next test or group
|
245
|
+
Previous: step back to the previous operation (in the group)
|
246
|
+
Enter: enter a group, executing any side effects
|
247
|
+
Browse: enter a group without triggering side effects
|
248
|
+
Up: leave the current group
|
249
|
+
|
250
|
+
Problem: cannot browse a 'setup'-group unless you are able to instantiate
|
251
|
+
the generator fun, and to do that you either need the actual result from
|
252
|
+
the 'setup' fun, or you need to know if the generator fun expects an
|
253
|
+
argument matching a certain pattern, such as a 3-tuple. You could then
|
254
|
+
pass dummy values such as 'undefined' for the components, since they
|
255
|
+
will not be used unless you try to run one of the instantiated tests or
|
256
|
+
a setup fun of a subgroup.
|
257
|
+
|
258
|
+
If there was never a fun that returned a list of tests, but only funs
|
259
|
+
around single tests, it would be simple - just don't apply any funs
|
260
|
+
while traversing. But then it would be necessary to wrap each test
|
261
|
+
within a 'setup' in its own generator fun, which would be a pain, and it
|
262
|
+
would not be possible to nest 'setup' groups in an easy way (variables
|
263
|
+
bound in the outer group would have to be explicitly passed to the
|
264
|
+
generator funs in the inner group, using manual closure conversion). This
|
265
|
+
is simply not tolerable. So, dummy value instantiation is the only way
|
266
|
+
to go, if it should be possible at all to browse test groups without
|
267
|
+
executing setup/cleanup funs.
|
268
|
+
|
269
|
+
Solution: a 'browser' function that tries to pass variants of dummy
|
270
|
+
values to a fun until it either succeeds or fails with some other error
|
271
|
+
than 'fun_clause'. This has been implemented and is the basis of the
|
272
|
+
test listing function.
|
273
|
+
|
274
|
+
When a setup-group is being browsed, its tests cannot be executed (since
|
275
|
+
they are instantiated with dummy values), and its subgroups can only be
|
276
|
+
further Browsed, not Entered, for the same reason.
|
Binary file
|
@@ -0,0 +1,172 @@
|
|
1
|
+
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
2
|
+
<html>
|
3
|
+
<head>
|
4
|
+
<title>Module eunit</title>
|
5
|
+
<link rel="stylesheet" type="text/css" href="stylesheet.css" title="EDoc">
|
6
|
+
</head>
|
7
|
+
<body bgcolor="white">
|
8
|
+
<div class="navbar"><a name="#navbar_top"></a><table width="100%" border="0" cellspacing="0" cellpadding="2" summary="navigation bar"><tr><td><a href="overview-summary.html" target="overviewFrame">Overview</a></td><td><a href="http://www.erlang.org/"><img src="erlang.png" align="right" border="0" alt="erlang logo"></a></td></tr></table></div>
|
9
|
+
<hr>
|
10
|
+
|
11
|
+
<h1>Module eunit</h1>
|
12
|
+
<ul class="index"><li><a href="#description">Description</a></li><li><a href="#index">Function Index</a></li><li><a href="#functions">Function Details</a></li></ul>This module is the normal EUnit user interface.
|
13
|
+
<p>Copyright � 2004-2007 Micka�l R�mond, Richard Carlsson</p>
|
14
|
+
|
15
|
+
<p><b>Version:</b> 2.0 beta 1, Oct 12 2008 14:17:27</p>
|
16
|
+
<p><b>Authors:</b> Micka�l R�mond (<a href="mailto:mickael.remond@process-one.net"><tt>mickael.remond@process-one.net</tt></a>) [<em>web site:</em> <tt><a href="http://www.process-one.net/" target="_top">http://www.process-one.net/</a></tt>], Richard Carlsson (<a href="mailto:richardc@it.uu.se"><tt>richardc@it.uu.se</tt></a>) [<em>web site:</em> <tt><a href="http://user.it.uu.se/~richardc/" target="_top">http://user.it.uu.se/~richardc/</a></tt>].</p>
|
17
|
+
|
18
|
+
<h2><a name="description">Description</a></h2>This module is the normal EUnit user interface.
|
19
|
+
<h2><a name="index">Function Index</a></h2>
|
20
|
+
<table width="100%" border="1" cellspacing="0" cellpadding="2" summary="function index"><tr><td valign="top"><a href="#list-1">list/1</a></td><td></td></tr>
|
21
|
+
<tr><td valign="top"><a href="#start-0">start/0</a></td><td></td></tr>
|
22
|
+
<tr><td valign="top"><a href="#start-1">start/1</a></td><td></td></tr>
|
23
|
+
<tr><td valign="top"><a href="#stop-0">stop/0</a></td><td></td></tr>
|
24
|
+
<tr><td valign="top"><a href="#stop-1">stop/1</a></td><td></td></tr>
|
25
|
+
<tr><td valign="top"><a href="#submit-1">submit/1</a></td><td></td></tr>
|
26
|
+
<tr><td valign="top"><a href="#submit-2">submit/2</a></td><td></td></tr>
|
27
|
+
<tr><td valign="top"><a href="#submit-3">submit/3</a></td><td></td></tr>
|
28
|
+
<tr><td valign="top"><a href="#test-1">test/1</a></td><td></td></tr>
|
29
|
+
<tr><td valign="top"><a href="#test-2">test/2</a></td><td></td></tr>
|
30
|
+
<tr><td valign="top"><a href="#test-3">test/3</a></td><td></td></tr>
|
31
|
+
<tr><td valign="top"><a href="#testp-1">testp/1</a></td><td></td></tr>
|
32
|
+
<tr><td valign="top"><a href="#watch-1">watch/1</a></td><td></td></tr>
|
33
|
+
<tr><td valign="top"><a href="#watch-2">watch/2</a></td><td></td></tr>
|
34
|
+
<tr><td valign="top"><a href="#watch-3">watch/3</a></td><td></td></tr>
|
35
|
+
<tr><td valign="top"><a href="#watch_app-1">watch_app/1</a></td><td></td></tr>
|
36
|
+
<tr><td valign="top"><a href="#watch_app-2">watch_app/2</a></td><td></td></tr>
|
37
|
+
<tr><td valign="top"><a href="#watch_app-3">watch_app/3</a></td><td></td></tr>
|
38
|
+
<tr><td valign="top"><a href="#watch_path-1">watch_path/1</a></td><td></td></tr>
|
39
|
+
<tr><td valign="top"><a href="#watch_path-2">watch_path/2</a></td><td></td></tr>
|
40
|
+
<tr><td valign="top"><a href="#watch_path-3">watch_path/3</a></td><td></td></tr>
|
41
|
+
<tr><td valign="top"><a href="#watch_regexp-1">watch_regexp/1</a></td><td></td></tr>
|
42
|
+
<tr><td valign="top"><a href="#watch_regexp-2">watch_regexp/2</a></td><td></td></tr>
|
43
|
+
<tr><td valign="top"><a href="#watch_regexp-3">watch_regexp/3</a></td><td></td></tr>
|
44
|
+
</table>
|
45
|
+
|
46
|
+
<h2><a name="functions">Function Details</a></h2>
|
47
|
+
|
48
|
+
<h3 class="function"><a name="list-1">list/1</a></h3>
|
49
|
+
<div class="spec">
|
50
|
+
<p><tt>list(T) -> any()</tt></p>
|
51
|
+
</div>
|
52
|
+
|
53
|
+
<h3 class="function"><a name="start-0">start/0</a></h3>
|
54
|
+
<div class="spec">
|
55
|
+
<p><tt>start() -> any()</tt></p>
|
56
|
+
</div>
|
57
|
+
|
58
|
+
<h3 class="function"><a name="start-1">start/1</a></h3>
|
59
|
+
<div class="spec">
|
60
|
+
<p><tt>start(Server) -> any()</tt></p>
|
61
|
+
</div>
|
62
|
+
|
63
|
+
<h3 class="function"><a name="stop-0">stop/0</a></h3>
|
64
|
+
<div class="spec">
|
65
|
+
<p><tt>stop() -> any()</tt></p>
|
66
|
+
</div>
|
67
|
+
|
68
|
+
<h3 class="function"><a name="stop-1">stop/1</a></h3>
|
69
|
+
<div class="spec">
|
70
|
+
<p><tt>stop(Server) -> any()</tt></p>
|
71
|
+
</div>
|
72
|
+
|
73
|
+
<h3 class="function"><a name="submit-1">submit/1</a></h3>
|
74
|
+
<div class="spec">
|
75
|
+
<p><tt>submit(T) -> any()</tt></p>
|
76
|
+
</div>
|
77
|
+
|
78
|
+
<h3 class="function"><a name="submit-2">submit/2</a></h3>
|
79
|
+
<div class="spec">
|
80
|
+
<p><tt>submit(T, Options) -> any()</tt></p>
|
81
|
+
</div>
|
82
|
+
|
83
|
+
<h3 class="function"><a name="submit-3">submit/3</a></h3>
|
84
|
+
<div class="spec">
|
85
|
+
<p><tt>submit(Server, T, Options) -> any()</tt></p>
|
86
|
+
</div>
|
87
|
+
|
88
|
+
<h3 class="function"><a name="test-1">test/1</a></h3>
|
89
|
+
<div class="spec">
|
90
|
+
<p><tt>test(T) -> any()</tt></p>
|
91
|
+
</div>
|
92
|
+
|
93
|
+
<h3 class="function"><a name="test-2">test/2</a></h3>
|
94
|
+
<div class="spec">
|
95
|
+
<p><tt>test(T, Options) -> any()</tt></p>
|
96
|
+
</div>
|
97
|
+
|
98
|
+
<h3 class="function"><a name="test-3">test/3</a></h3>
|
99
|
+
<div class="spec">
|
100
|
+
<p><tt>test(Server, T, Options) -> any()</tt></p>
|
101
|
+
</div>
|
102
|
+
|
103
|
+
<h3 class="function"><a name="testp-1">testp/1</a></h3>
|
104
|
+
<div class="spec">
|
105
|
+
<p><tt>testp(T) -> any()</tt></p>
|
106
|
+
</div>
|
107
|
+
|
108
|
+
<h3 class="function"><a name="watch-1">watch/1</a></h3>
|
109
|
+
<div class="spec">
|
110
|
+
<p><tt>watch(Target) -> any()</tt></p>
|
111
|
+
</div>
|
112
|
+
|
113
|
+
<h3 class="function"><a name="watch-2">watch/2</a></h3>
|
114
|
+
<div class="spec">
|
115
|
+
<p><tt>watch(Target, Options) -> any()</tt></p>
|
116
|
+
</div>
|
117
|
+
|
118
|
+
<h3 class="function"><a name="watch-3">watch/3</a></h3>
|
119
|
+
<div class="spec">
|
120
|
+
<p><tt>watch(Server, Target, Options) -> any()</tt></p>
|
121
|
+
</div>
|
122
|
+
|
123
|
+
<h3 class="function"><a name="watch_app-1">watch_app/1</a></h3>
|
124
|
+
<div class="spec">
|
125
|
+
<p><tt>watch_app(Name) -> any()</tt></p>
|
126
|
+
</div>
|
127
|
+
|
128
|
+
<h3 class="function"><a name="watch_app-2">watch_app/2</a></h3>
|
129
|
+
<div class="spec">
|
130
|
+
<p><tt>watch_app(Name, Options) -> any()</tt></p>
|
131
|
+
</div>
|
132
|
+
|
133
|
+
<h3 class="function"><a name="watch_app-3">watch_app/3</a></h3>
|
134
|
+
<div class="spec">
|
135
|
+
<p><tt>watch_app(Server, Name, Options) -> any()</tt></p>
|
136
|
+
</div>
|
137
|
+
|
138
|
+
<h3 class="function"><a name="watch_path-1">watch_path/1</a></h3>
|
139
|
+
<div class="spec">
|
140
|
+
<p><tt>watch_path(Target) -> any()</tt></p>
|
141
|
+
</div>
|
142
|
+
|
143
|
+
<h3 class="function"><a name="watch_path-2">watch_path/2</a></h3>
|
144
|
+
<div class="spec">
|
145
|
+
<p><tt>watch_path(Target, Options) -> any()</tt></p>
|
146
|
+
</div>
|
147
|
+
|
148
|
+
<h3 class="function"><a name="watch_path-3">watch_path/3</a></h3>
|
149
|
+
<div class="spec">
|
150
|
+
<p><tt>watch_path(Server, Target, Options) -> any()</tt></p>
|
151
|
+
</div>
|
152
|
+
|
153
|
+
<h3 class="function"><a name="watch_regexp-1">watch_regexp/1</a></h3>
|
154
|
+
<div class="spec">
|
155
|
+
<p><tt>watch_regexp(Target) -> any()</tt></p>
|
156
|
+
</div>
|
157
|
+
|
158
|
+
<h3 class="function"><a name="watch_regexp-2">watch_regexp/2</a></h3>
|
159
|
+
<div class="spec">
|
160
|
+
<p><tt>watch_regexp(Target, Options) -> any()</tt></p>
|
161
|
+
</div>
|
162
|
+
|
163
|
+
<h3 class="function"><a name="watch_regexp-3">watch_regexp/3</a></h3>
|
164
|
+
<div class="spec">
|
165
|
+
<p><tt>watch_regexp(Server, Target, Options) -> any()</tt></p>
|
166
|
+
</div>
|
167
|
+
<hr>
|
168
|
+
|
169
|
+
<div class="navbar"><a name="#navbar_bottom"></a><table width="100%" border="0" cellspacing="0" cellpadding="2" summary="navigation bar"><tr><td><a href="overview-summary.html" target="overviewFrame">Overview</a></td><td><a href="http://www.erlang.org/"><img src="erlang.png" align="right" border="0" alt="erlang logo"></a></td></tr></table></div>
|
170
|
+
<p><i>Generated by EDoc, Oct 12 2008, 14:17:27.</i></p>
|
171
|
+
</body>
|
172
|
+
</html>
|
@@ -0,0 +1,17 @@
|
|
1
|
+
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
2
|
+
<html>
|
3
|
+
<head>
|
4
|
+
<title>The eunit application</title>
|
5
|
+
</head>
|
6
|
+
<frameset cols="20%,80%">
|
7
|
+
<frame src="modules-frame.html" name="modulesFrame" title="">
|
8
|
+
|
9
|
+
<frame src="overview-summary.html" name="overviewFrame" title="">
|
10
|
+
<noframes>
|
11
|
+
<h2>This page uses frames</h2>
|
12
|
+
<p>Your browser does not accept frames.
|
13
|
+
<br>You should go to the <a href="overview-summary.html">non-frame version</a> instead.
|
14
|
+
</p>
|
15
|
+
</noframes>
|
16
|
+
</frameset>
|
17
|
+
</html>
|
@@ -0,0 +1,12 @@
|
|
1
|
+
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
2
|
+
<html>
|
3
|
+
<head>
|
4
|
+
<title>The eunit application</title>
|
5
|
+
<link rel="stylesheet" type="text/css" href="stylesheet.css" title="EDoc">
|
6
|
+
</head>
|
7
|
+
<body bgcolor="white">
|
8
|
+
<h2 class="indextitle">Modules</h2>
|
9
|
+
<table width="100%" border="0" summary="list of modules">
|
10
|
+
<tr><td><a href="eunit.html" target="overviewFrame" class="module">eunit</a></td></tr></table>
|
11
|
+
</body>
|
12
|
+
</html>
|