poolparty 0.2.18 → 0.2.69
Sign up to get free protection for your applications and to get access to all the features.
- data/Manifest.txt +142 -47
- data/PostInstall.txt +5 -5
- data/README.txt +25 -4
- data/Rakefile +46 -2
- data/bin/cloud +12 -21
- data/bin/cloud-add-keypair +18 -13
- data/bin/cloud-configure +11 -18
- data/bin/cloud-contract +7 -17
- data/bin/cloud-ensure-provisioning +39 -0
- data/bin/cloud-expand +9 -17
- data/bin/cloud-handle-load +27 -0
- data/bin/cloud-list +3 -9
- data/bin/cloud-maintain +12 -18
- data/bin/cloud-osxcopy +3 -9
- data/bin/cloud-provision +20 -21
- data/bin/cloud-refresh +4 -13
- data/bin/cloud-run +3 -4
- data/bin/cloud-ssh +3 -2
- data/bin/cloud-start +18 -21
- data/bin/cloud-stats +17 -0
- data/bin/cloud-terminate +4 -7
- data/bin/messenger-get-current-nodes +14 -0
- data/bin/pool +12 -12
- data/bin/pool-describe +0 -1
- data/bin/{pool-spec → pool-generate} +1 -0
- data/bin/pool-init +28 -0
- data/bin/pool-list +14 -12
- data/bin/pool-start +11 -17
- data/bin/server-build-messenger +13 -6
- data/bin/server-fire-cmd +1 -1
- data/bin/server-get-load +5 -16
- data/bin/server-list-active +3 -10
- data/bin/server-rerun +4 -4
- data/bin/server-send-command +18 -0
- data/bin/server-show-stats +17 -0
- data/bin/server-start-client +29 -0
- data/bin/server-start-master +13 -14
- data/bin/server-start-node +14 -15
- data/bin/server-stop-client +3 -0
- data/bin/server-stop-master +3 -0
- data/bin/server-stop-node +3 -0
- data/bin/server-update-hosts +48 -0
- data/config/hoe.rb +4 -3
- data/examples/plugin_without_plugin_directory.rb +1 -2
- data/generators/poolspec/USAGE +2 -2
- data/generators/poolspec/poolspec_generator.rb +2 -1
- data/generators/poolspec/templates/pool_spec_template.erb +3 -2
- data/lib/erlang/messenger/Rakefile +12 -0
- data/lib/erlang/messenger/ebin/client.app +19 -0
- data/lib/erlang/messenger/ebin/master.app +1 -1
- data/lib/erlang/messenger/ebin/node.app +1 -1
- data/lib/erlang/messenger/ebin/pm_client_rel-0.1.rel +1 -0
- data/lib/erlang/messenger/ebin/pm_master_rel-0.1.rel +1 -1
- data/lib/erlang/messenger/ebin/pm_node_rel-0.1.rel +1 -1
- data/lib/erlang/messenger/include/defines.hrl +27 -0
- data/lib/erlang/messenger/lib/eunit/.svn/all-wcprops +53 -0
- data/lib/erlang/messenger/lib/eunit/.svn/entries +140 -0
- data/lib/erlang/messenger/lib/eunit/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/.svn/prop-base/NOTES.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/AUTHORS.svn-base +2 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/CHANGELOG.svn-base +14 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/COPYING.svn-base +504 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/NOTES.svn-base +276 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/README.svn-base +3 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/sys.config.svn-base +9 -0
- data/lib/erlang/messenger/lib/eunit/.svn/text-base/vsn.mk.svn-base +1 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/all-wcprops +59 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/entries +142 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/erlang.png.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/eunit.html.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/index.html.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/modules-frame.html.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/overview-summary.html.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/prop-base/packages-frame.html.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/edoc-info.svn-base +3 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/erlang.png.svn-base +0 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/eunit.html.svn-base +172 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/index.html.svn-base +17 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/modules-frame.html.svn-base +12 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/overview-summary.html.svn-base +984 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/overview.edoc.svn-base +980 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/packages-frame.html.svn-base +11 -0
- data/lib/erlang/messenger/lib/eunit/doc/.svn/text-base/stylesheet.css.svn-base +55 -0
- data/lib/erlang/messenger/lib/eunit/ebin/.svn/all-wcprops +5 -0
- data/lib/erlang/messenger/lib/eunit/ebin/.svn/dir-prop-base +8 -0
- data/lib/erlang/messenger/lib/eunit/ebin/.svn/entries +28 -0
- data/lib/erlang/messenger/lib/eunit/ebin/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/all-wcprops +23 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/entries +66 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/prop-base/eunit_examples.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/prop-base/fib.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/text-base/eunit_examples.erl.svn-base +339 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/text-base/fib.erl.svn-base +19 -0
- data/lib/erlang/messenger/lib/eunit/examples/.svn/text-base/tests.txt.svn-base +1 -0
- data/lib/erlang/messenger/lib/eunit/include/.svn/all-wcprops +11 -0
- data/lib/erlang/messenger/lib/eunit/include/.svn/entries +41 -0
- data/lib/erlang/messenger/lib/eunit/include/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/include/.svn/prop-base/eunit.hrl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/include/.svn/text-base/eunit.hrl.svn-base +313 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/all-wcprops +113 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/entries +259 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/format +1 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/autoload.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/code_monitor.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_autoexport.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_data.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_internal.hrl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_lib.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_proc.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_serial.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_server.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_striptests.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_test.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_tests.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/eunit_tty.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/prop-base/file_monitor.erl.svn-base +5 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/autoload.erl.svn-base +388 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/code_monitor.erl.svn-base +243 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit.app.src.svn-base +21 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit.appup.src.svn-base +1 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit.erl.svn-base +196 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_autoexport.erl.svn-base +102 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_data.erl.svn-base +798 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_internal.hrl.svn-base +48 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_lib.erl.svn-base +682 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_proc.erl.svn-base +552 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_serial.erl.svn-base +157 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_server.erl.svn-base +340 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_striptests.erl.svn-base +64 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_test.erl.svn-base +334 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_tests.erl.svn-base +45 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/eunit_tty.erl.svn-base +272 -0
- data/lib/erlang/messenger/lib/eunit/src/.svn/text-base/file_monitor.erl.svn-base +409 -0
- data/lib/erlang/messenger/pm_client_rel-0.1.boot +0 -0
- data/lib/erlang/messenger/pm_client_rel-0.1.script +238 -0
- data/lib/erlang/messenger/pm_master_rel-0.1.boot +0 -0
- data/lib/erlang/messenger/pm_master_rel-0.1.script +82 -85
- data/lib/erlang/messenger/pm_node_rel-0.1.boot +0 -0
- data/lib/erlang/messenger/pm_node_rel-0.1.script +80 -85
- data/lib/erlang/messenger/src/client_app.erl +39 -0
- data/lib/erlang/messenger/src/client_server.erl +60 -0
- data/lib/erlang/messenger/src/pm_client.erl +48 -18
- data/lib/erlang/messenger/src/pm_client_old.erl +52 -0
- data/lib/erlang/messenger/src/pm_client_supervisor.erl +38 -0
- data/lib/erlang/messenger/src/pm_cluster.erl +20 -16
- data/lib/erlang/messenger/src/pm_event_manager.erl +27 -0
- data/lib/erlang/messenger/src/pm_master.erl +126 -34
- data/lib/erlang/messenger/src/pm_master_event_handler.erl +72 -0
- data/lib/erlang/messenger/src/pm_master_supervisor.erl +9 -10
- data/lib/erlang/messenger/src/pm_node.erl +107 -30
- data/lib/erlang/messenger/src/pm_node_supervisor.erl +13 -15
- data/lib/erlang/messenger/src/pm_packager.erl +5 -2
- data/lib/erlang/messenger/src/pm_strings.erl +11 -0
- data/lib/erlang/messenger/src/utils.erl +43 -8
- data/lib/erlang/messenger/useful_snippets +17 -0
- data/lib/poolparty/aska/aska.rb +150 -0
- data/lib/poolparty/base_packages/haproxy.rb +19 -26
- data/lib/poolparty/base_packages/heartbeat.rb +48 -47
- data/lib/poolparty/base_packages/poolparty.rb +88 -36
- data/lib/poolparty/base_packages/runit.rb +21 -0
- data/lib/poolparty/config/postlaunchmessage.txt +5 -0
- data/lib/poolparty/core/array.rb +4 -1
- data/lib/poolparty/core/class.rb +2 -0
- data/lib/poolparty/core/exception.rb +2 -1
- data/lib/poolparty/core/hash.rb +2 -2
- data/lib/poolparty/core/kernel.rb +3 -3
- data/lib/poolparty/core/metaid.rb +15 -0
- data/lib/poolparty/core/object.rb +42 -2
- data/lib/poolparty/core/string.rb +21 -6
- data/lib/poolparty/core/symbol.rb +9 -0
- data/lib/poolparty/dependency_resolutions/puppet.rb +20 -7
- data/lib/poolparty/exceptions/CloudNotFoundException.rb +7 -0
- data/lib/poolparty/exceptions/LoadRulesException.rb +7 -0
- data/lib/poolparty/exceptions/MasterException.rb +10 -0
- data/lib/poolparty/helpers/binary.rb +37 -4
- data/lib/poolparty/helpers/console.rb +25 -8
- data/lib/poolparty/helpers/nice_printer.rb +36 -0
- data/lib/poolparty/helpers/optioner.rb +51 -16
- data/lib/poolparty/helpers/provisioner_base.rb +117 -28
- data/lib/poolparty/helpers/provisioners/master.rb +102 -35
- data/lib/poolparty/helpers/provisioners/slave.rb +25 -9
- data/lib/poolparty/modules/cloud_dsl.rb +13 -0
- data/lib/poolparty/modules/cloud_resourcer.rb +51 -8
- data/lib/poolparty/modules/configurable.rb +1 -1
- data/lib/poolparty/modules/definable_resource.rb +2 -2
- data/lib/poolparty/modules/file_writer.rb +37 -6
- data/lib/poolparty/modules/method_missing_sugar.rb +8 -3
- data/lib/poolparty/modules/pretty_printer.rb +1 -0
- data/lib/poolparty/modules/resourcing_dsl.rb +4 -2
- data/lib/poolparty/modules/thread_pool.rb +106 -0
- data/lib/poolparty/monitors/base_monitor.rb +65 -6
- data/lib/poolparty/monitors/monitors/cpu_monitor.rb +1 -1
- data/lib/poolparty/monitors/monitors/memory_monitor.rb +28 -1
- data/lib/poolparty/monitors/monitors/web_monitor.rb +18 -0
- data/lib/poolparty/net/messenger.rb +72 -0
- data/lib/poolparty/net/remote.rb +5 -2
- data/lib/poolparty/net/remote_bases/ec2/ec2_response_object.rb +66 -0
- data/lib/poolparty/net/remote_bases/ec2.rb +133 -131
- data/lib/poolparty/net/remote_instance.rb +28 -6
- data/lib/poolparty/net/remoter.rb +117 -64
- data/lib/poolparty/net/remoter_base.rb +49 -11
- data/lib/poolparty/plugins/deploydirectory.rb +66 -0
- data/lib/poolparty/plugins/line.rb +5 -4
- data/lib/poolparty/plugins/rsyncmirror.rb +26 -0
- data/lib/poolparty/plugins/runit.rb +96 -0
- data/lib/poolparty/plugins/svn.rb +1 -1
- data/lib/poolparty/pool/base.rb +47 -18
- data/lib/poolparty/pool/cloud.rb +121 -65
- data/lib/poolparty/pool/custom_resource.rb +4 -20
- data/lib/poolparty/pool/loggable.rb +3 -8
- data/lib/poolparty/pool/plugin.rb +14 -19
- data/lib/poolparty/pool/plugin_model.rb +8 -8
- data/lib/poolparty/pool/pool.rb +28 -11
- data/lib/poolparty/pool/resource.rb +109 -40
- data/lib/poolparty/pool/resources/class_package.rb +74 -33
- data/lib/poolparty/pool/resources/conditional.rb +32 -10
- data/lib/poolparty/pool/resources/custom_service.rb +30 -0
- data/lib/poolparty/pool/resources/exec.rb +6 -5
- data/lib/poolparty/pool/resources/gem_package.rb +52 -0
- data/lib/poolparty/pool/resources/mount.rb +22 -0
- data/lib/poolparty/pool/resources/package.rb +13 -3
- data/lib/poolparty/pool/resources/sshkey.rb +1 -1
- data/lib/poolparty/pool/resources/variable.rb +4 -0
- data/lib/poolparty/pool/script.rb +8 -6
- data/lib/poolparty/templates/haproxy.conf +1 -1
- data/lib/poolparty/templates/messenger/client/log-run.erb +2 -0
- data/lib/poolparty/templates/messenger/client/run.erb +4 -0
- data/lib/poolparty/templates/messenger/master/log-run.erb +2 -0
- data/lib/poolparty/templates/messenger/master/run.erb +4 -0
- data/lib/poolparty/templates/messenger/node/log-run.erb +2 -0
- data/lib/poolparty/templates/messenger/node/run.erb +4 -0
- data/lib/poolparty/templates/poolparty.monitor +1 -1
- data/lib/poolparty/templates/puppet.conf +0 -0
- data/lib/poolparty/templates/puppetcleaner +6 -0
- data/lib/poolparty/templates/puppetrerun +9 -0
- data/lib/poolparty/templates/puppetrunner +8 -0
- data/lib/poolparty/templates/yaws.conf +19 -0
- data/lib/poolparty/version.rb +1 -1
- data/lib/poolparty.rb +35 -6
- data/lib/poolpartycl.rb +4 -0
- data/log/pool.logs +0 -0
- data/poolparty.gemspec +574 -61
- data/spec/poolparty/aska/aska_spec.rb +122 -0
- data/spec/poolparty/bin/console_spec.rb +18 -0
- data/spec/poolparty/core/hash_spec.rb +4 -4
- data/spec/poolparty/core/object_spec.rb +29 -0
- data/spec/poolparty/core/string_spec.rb +6 -0
- data/spec/poolparty/core/time_spec.rb +0 -3
- data/spec/poolparty/helpers/binary_spec.rb +2 -2
- data/spec/poolparty/helpers/optioner_spec.rb +1 -4
- data/spec/poolparty/helpers/provisioner_base_spec.rb +14 -1
- data/spec/poolparty/helpers/provisioners/master_spec.rb +3 -3
- data/spec/poolparty/modules/cloud_resourcer_spec.rb +3 -3
- data/spec/poolparty/modules/configurable_spec.rb +4 -1
- data/spec/poolparty/monitors/base_monitor_spec.rb +94 -2
- data/spec/poolparty/monitors/monitors/cpu_monitor_spec.rb +0 -1
- data/spec/poolparty/monitors/monitors/memory_monitor_spec.rb +47 -0
- data/spec/poolparty/{helpers → net}/messenger_spec.rb +3 -1
- data/spec/poolparty/net/remote_bases/ec2_spec.rb +46 -5
- data/spec/poolparty/net/remote_instance_spec.rb +2 -1
- data/spec/poolparty/net/remote_spec.rb +30 -8
- data/spec/poolparty/net/remoter_base_spec.rb +4 -1
- data/spec/poolparty/net/remoter_spec.rb +11 -108
- data/spec/poolparty/plugins/deploydirectory_spec.rb +51 -0
- data/spec/poolparty/pool/base_spec.rb +43 -33
- data/spec/poolparty/pool/cloud_spec.rb +299 -248
- data/spec/poolparty/pool/custom_resource_spec.rb +10 -5
- data/spec/poolparty/pool/example_spec.rb +0 -84
- data/spec/poolparty/pool/plugin_model_spec.rb +3 -2
- data/spec/poolparty/pool/plugin_spec.rb +89 -62
- data/spec/poolparty/pool/pool_spec.rb +17 -2
- data/spec/poolparty/pool/resource_spec.rb +341 -236
- data/spec/poolparty/pool/resources/class_package_spec.rb +102 -66
- data/spec/poolparty/pool/resources/conditional_spec.rb +65 -26
- data/spec/poolparty/pool/resources/cron_spec.rb +3 -2
- data/spec/poolparty/pool/resources/exec_spec.rb +1 -1
- data/spec/poolparty/pool/resources/gem_spec.rb +18 -14
- data/spec/poolparty/pool/resources/remote_file_spec.rb +1 -1
- data/spec/poolparty/pool/resources/variable_spec.rb +1 -1
- data/spec/poolparty/pool/script_spec.rb +58 -37
- data/spec/poolparty/pool/test_plugins/webserver.rb +1 -0
- data/spec/poolparty/spec_helper.rb +16 -5
- data/tasks/deployment.rake +19 -3
- data/tasks/development.rake +11 -2
- data/tasks/ec2.rake +9 -1
- data/website/index.html +2 -2
- metadata +167 -70
- data/bin/pool-provision +0 -34
- data/erl_crash.dump +0 -8409
- data/examples/with_apache_plugin.rb +0 -22
- data/lib/erlang/messenger/Makefile +0 -15
- data/lib/erlang/messenger/ebin/master_app.beam +0 -0
- data/lib/erlang/messenger/ebin/node_app.beam +0 -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_supervisor.beam +0 -0
- data/lib/erlang/messenger/ebin/pm_node.beam +0 -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/Makefile +0 -28
- 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.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/src/Makefile +0 -46
- data/lib/erlang/messenger/src/pm_event_handler.erl +0 -21
- data/lib/poolparty/config/allowed_commands.yml +0 -1
- data/lib/poolparty/helpers/messenger.rb +0 -29
- data/lib/poolparty/plugins/git.rb +0 -39
- data/lib/poolparty/pool/resources/gem.rb +0 -28
- data/lib/poolparty/pool/tmp/.ppkeys +0 -3
- data/lib/poolparty/pool/tmp/happydayz +0 -1
- data/lib/poolparty/pool/tmp/install_master.sh +0 -33
- data/lib/poolparty/pool/tmp/pool.spec +0 -11
- data/lib/poolparty/pool/tmp/poolparty.pp +0 -600
- data/lib/poolparty/pool/tmp/tc-instances.list +0 -1
- data/lib/poolparty/templates/fileserver.conf +0 -4
- data/spec/poolparty/plugins/git_spec.rb +0 -33
- data/test_manifest.pp +0 -658
@@ -0,0 +1,980 @@
|
|
1
|
+
|
2
|
+
-*- html -*-
|
3
|
+
|
4
|
+
EUnit overview page
|
5
|
+
|
6
|
+
@title EUnit - a Lightweight Unit Testing Framework for Erlang
|
7
|
+
|
8
|
+
@author Richard Carlsson <richardc@it.uu.se>
|
9
|
+
[http://user.it.uu.se/~richardc/]
|
10
|
+
@author Micka�l R�mond <mickael.remond@process-one.net>
|
11
|
+
[http://www.process-one.net/]
|
12
|
+
@copyright 2004-2007 Micka�l R�mond, Richard Carlsson
|
13
|
+
@version {@version}, {@date} {@time}
|
14
|
+
|
15
|
+
@doc EUnit is a unit testing framework for Erlang. It is very powerful
|
16
|
+
and flexible, is easy to use, and has small syntactical overhead.
|
17
|
+
|
18
|
+
<ul>
|
19
|
+
<li>{@section Unit Testing}</li>
|
20
|
+
<li>{@section Terminology}</li>
|
21
|
+
<li>{@section Getting started}</li>
|
22
|
+
<li>{@section EUnit macros}</li>
|
23
|
+
<li>{@section EUnit test representation}</li>
|
24
|
+
</ul>
|
25
|
+
|
26
|
+
EUnit builds on ideas from the family of unit testing frameworks for
|
27
|
+
Object Oriented languages that originated with JUnit by Beck and Gamma
|
28
|
+
(and Beck's previous framework SUnit for Smalltalk). However, EUnit uses
|
29
|
+
techniques more adapted to functional and concurrent programming, and is
|
30
|
+
typically less verbose than its relatives.
|
31
|
+
|
32
|
+
Although EUnit uses many preprocessor macros, they have been designed to
|
33
|
+
be as nonintrusive as possible, and should not cause conflicts with
|
34
|
+
existing code. Adding EUnit tests to a module should thus not normally
|
35
|
+
require modifying code. Furthermore, tests that only exercise the
|
36
|
+
exported functions of a module can always be placed in a completely
|
37
|
+
separate module, avoiding any conflicts entirely.
|
38
|
+
|
39
|
+
== Unit Testing ==
|
40
|
+
|
41
|
+
Unit Testing is testing of individual program "units" in relative
|
42
|
+
isolation. There is no particular size requirement: a unit can be a
|
43
|
+
function, a module, a process, or even a whole application, but the most
|
44
|
+
typical testing units are individual functions or modules. In order to
|
45
|
+
test a unit, you specify a set of individual tests, set up the smallest
|
46
|
+
necessary environment for being able to run those tests (often, you
|
47
|
+
don't need to do any setup at all), you run the tests and collect the
|
48
|
+
results, and finally you do any necessary cleanup so that the test can
|
49
|
+
be run again later. A Unit Testing Framework tries to help you in each
|
50
|
+
stage of this process, so that it is easy to write tests, easy to run
|
51
|
+
them, and easy to see which tests failed (so you can fix the bugs).
|
52
|
+
|
53
|
+
=== Advantages of unit testing ===
|
54
|
+
|
55
|
+
<dl>
|
56
|
+
<dt>Reduces the risks of changing the program</dt>
|
57
|
+
<dd>Most programs will be modified during their lifetime: bugs will be
|
58
|
+
fixed, features will be added, optimizations may become necessary, or
|
59
|
+
the code will need to be refactored or cleaned up in other ways to
|
60
|
+
make it easier to work with. But every change to a working program is
|
61
|
+
a risk of introducing new bugs - or reintroducing bugs that had
|
62
|
+
previously been fixed. Having a set of unit tests that you can run
|
63
|
+
with very little effort makes it easy to know that the code still
|
64
|
+
works as it should (this use is called <em>regression testing</em>;
|
65
|
+
see {@section Terminology}). This goes a long way to reduce the
|
66
|
+
resistance to changing and refactoring code.</dd>
|
67
|
+
<dt>Helps guide and speed up the development process</dt>
|
68
|
+
<dd>By focusing on getting the code to pass the tests, the programmer
|
69
|
+
can become more productive, not overspecify or get lost in premature
|
70
|
+
optimizations, and create code that is correct from the very beginning
|
71
|
+
(so-called <em>test-driven development</em>; see {@section
|
72
|
+
Terminology}).</dd>
|
73
|
+
<dt>Helps separate interface from implementation</dt>
|
74
|
+
<dd>When writing tests, the programmer may discover dependencies
|
75
|
+
(in order to get the tests to run) that ought not to be there, and
|
76
|
+
which need to be abstracted away to get a cleaner design. This helps
|
77
|
+
eliminate bad dependencies before they spread throughout the
|
78
|
+
code.</dd>
|
79
|
+
<dt>Makes component integration easier</dt>
|
80
|
+
<dd>By testing in a bottom-up fashion, beginning with the smallest
|
81
|
+
program units and creating a confidence in that they work as they
|
82
|
+
should, it becomes easier to test that a higher-level component,
|
83
|
+
consisting of several such units, also behaves according to
|
84
|
+
specification (known as <em>integration testing</em>; see {@section
|
85
|
+
Terminology}).</dd>
|
86
|
+
<dt>Is self-documenting</dt>
|
87
|
+
<dd>The tests can be read as documentation, typically showing both
|
88
|
+
examples of correct and incorrect usage, along with the expected
|
89
|
+
consequences.</dd>
|
90
|
+
</dl>
|
91
|
+
|
92
|
+
== Terminology ==
|
93
|
+
|
94
|
+
<dl>
|
95
|
+
<dt>Unit testing</dt>
|
96
|
+
<dd>Testing that a program unit behaves as it is supposed to do (in
|
97
|
+
itself), according to its specifications. Unit tests have an important
|
98
|
+
function as regression tests, when the program later is modified for
|
99
|
+
some reason, since they check that the program still behaves according
|
100
|
+
to specification.</dd>
|
101
|
+
<dt>Regression testing</dt>
|
102
|
+
<dd>Running a set of tests after making changes to a program, to check
|
103
|
+
that the program behaves as it did before the changes (except, of
|
104
|
+
course, for any intentional changes in behaviour). Unit tests are
|
105
|
+
important as regression tests, but regression testing can involve more
|
106
|
+
than just unit testing, and may also test behaviour that might not be
|
107
|
+
part of the normal specification (such as bug-for-bug-compatibility).
|
108
|
+
</dd>
|
109
|
+
<dt>Integration testing</dt>
|
110
|
+
<dd>Testing that a number of individually developed program units
|
111
|
+
(assumed to already have been separately unit tested) work together as
|
112
|
+
expected. Depending on the system being developed, integration testing
|
113
|
+
may be as simple as "just another level of unit testing", but might
|
114
|
+
also involve other kinds of tests (compare <em>system testing</em>).
|
115
|
+
</dd>
|
116
|
+
<dt>System testing</dt>
|
117
|
+
<dd>Testing that a complete system behaves according to its
|
118
|
+
specification. Specifically, system testing should not require knowing
|
119
|
+
any details about the implementation. It typically involves testing
|
120
|
+
many different aspects of the system behaviour apart from the basic
|
121
|
+
functionality, such as performance, usability, and reliability.</dd>
|
122
|
+
<dt>Test-driven development</dt>
|
123
|
+
<dd>A program development technique where you continuously write tests
|
124
|
+
<em>before</em> you implement the code that is supposed to pass those
|
125
|
+
tests. This can help you focus on solving the right problems, and not
|
126
|
+
make a more complicated implementation than necessary, by letting the
|
127
|
+
unit tests determine when a program is "done": if it fulfils its
|
128
|
+
specifications, there is no need to keep adding functionality.</dd>
|
129
|
+
<dt>Mock object</dt>
|
130
|
+
<dd>Sometimes, testing some unit `A' (e.g., a function) requires that
|
131
|
+
it collaborates somehow with some other unit `B' (perhaps being passed
|
132
|
+
as an argument, or by reference) - but `B' has not been implemented
|
133
|
+
yet. A "mock object" - an object which, for the purposes of testing
|
134
|
+
`A', looks and behaves like a real `B' - might then be used instead.
|
135
|
+
(This is of course only useful if it would be significantly more work
|
136
|
+
to implement a real `B' than to create a mock object.)</dd>
|
137
|
+
<dt>Test case</dt>
|
138
|
+
<dd>A single, well-defined test, that somehow can be uniquely
|
139
|
+
identified. When executed, the test case either <em>passes</em> or
|
140
|
+
<em>fails</em>; the test report should identify exactly which test
|
141
|
+
cases failed.</dd>
|
142
|
+
<dt>Test suite</dt>
|
143
|
+
<dd>A collection of test cases, generally with a specific, common
|
144
|
+
target for testing, such as a single function, module, or subsystem. A
|
145
|
+
test suite may also be recursively composed by smaller test
|
146
|
+
suites.</dd>
|
147
|
+
</dl>
|
148
|
+
|
149
|
+
== Getting started ==
|
150
|
+
<ul>
|
151
|
+
<li>{@section Including the EUnit header file}</li>
|
152
|
+
<li>{@section Writing simple test functions}</li>
|
153
|
+
<li>{@section Running EUnit}</li>
|
154
|
+
<li>{@section Writing test generating functions}</li>
|
155
|
+
<li>{@section An example}</li>
|
156
|
+
<li>{@section Disabling testing}</li>
|
157
|
+
<li>{@section Avoiding compile-time dependency on EUnit}</li>
|
158
|
+
</ul>
|
159
|
+
|
160
|
+
=== Including the EUnit header file ===
|
161
|
+
|
162
|
+
The simplest way to use EUnit in an Erlang module is to add the
|
163
|
+
following line at the beginning of the module (after the `-module'
|
164
|
+
declaration, but before any function definitions):
|
165
|
+
```-include_lib("eunit/include/eunit.hrl").'''
|
166
|
+
|
167
|
+
This will have the following effect:
|
168
|
+
<ul>
|
169
|
+
<li>Creates an exported function `test()' (unless testing is turned
|
170
|
+
off, and the module does not already contain a test() function), that
|
171
|
+
can be used to run all the unit tests defined in the module</li>
|
172
|
+
<li>Causes all functions whose names match `..._test()' or `..._test_()'
|
173
|
+
to be automatically exported from the module (unless testing is
|
174
|
+
turned off, or the `EUNIT_NOAUTO' macro is defined)</li>
|
175
|
+
<li>Makes all the preprocessor macros of EUnit available, to help
|
176
|
+
writing tests</li>
|
177
|
+
</ul>
|
178
|
+
|
179
|
+
<strong>Note:</strong> For `-include_lib(...)' to work, the Erlang
|
180
|
+
module search path <em>must</em> contain a directory whose name ends in
|
181
|
+
`eunit/ebin' (pointing to the `ebin' subdirectory of the EUnit
|
182
|
+
installation directory). If EUnit is installed as `lib/eunit' under your
|
183
|
+
Erlang/OTP system directory, its `ebin' subdirectory will be
|
184
|
+
automatically added to the search path when Erlang starts. Otherwise,
|
185
|
+
you need to add the directory explicitly, by passing a `-pa' flag to the
|
186
|
+
`erl' or `erlc' command. For example, a Makefile could contain the
|
187
|
+
following action for compiling `.erl' files:
|
188
|
+
```erlc -pa "path/to/eunit/ebin" $(ERL_COMPILE_FLAGS) -o$(EBIN) $<'''
|
189
|
+
or if you want Eunit to always be available when you run Erlang
|
190
|
+
interactively, you can add a line like the following to your
|
191
|
+
`$HOME/.erlang' file:
|
192
|
+
```code:add_path("/path/to/eunit/ebin").'''
|
193
|
+
|
194
|
+
=== Writing simple test functions ===
|
195
|
+
|
196
|
+
The EUnit framework makes it extremely easy to write unit tests in
|
197
|
+
Erlang. There are a few different ways of writing them, though, so we
|
198
|
+
start with the simplest:
|
199
|
+
|
200
|
+
A function with a name ending in `..._test()' is recognized by EUnit as
|
201
|
+
a simple test function - it takes no arguments, and its execution either
|
202
|
+
succeeds (returning some arbitrary value that EUnit will throw away), or
|
203
|
+
fails by throwing an exception of some kind (or by not terminating, in
|
204
|
+
which case it will be aborted after a while).
|
205
|
+
|
206
|
+
An example of a simple test function could be the following:
|
207
|
+
```reverse_test() -> lists:reverse([1,2,3]).'''
|
208
|
+
This just tests that the function `lists:reverse(List)' does not crash
|
209
|
+
when `List' is `[1,2,3]'. It is not a great test, but many people write
|
210
|
+
simple functions like this one to test the basic functionality of their
|
211
|
+
code, and those tests can be used directly by EUnit, without changes,
|
212
|
+
as long as their function names match.
|
213
|
+
|
214
|
+
==== Use exceptions to signal failure ====
|
215
|
+
|
216
|
+
To write more interesting tests, we need to make them crash (throw an
|
217
|
+
exception) when they don't get the result they expect. A simple way of
|
218
|
+
doing this is to use pattern matching with `=', as in the following
|
219
|
+
examples:
|
220
|
+
```reverse_nil_test() -> [] = lists:reverse([]).
|
221
|
+
reverse_one_test() -> [1] = lists:reverse([1]).
|
222
|
+
reverse_two_test() -> [2,1] = lists:reverse([1,2]).
|
223
|
+
'''
|
224
|
+
If there was some bug in `lists:reverse/1' that made it return something
|
225
|
+
other than `[2,1]' when it got `[1,2]' as input, then the last test
|
226
|
+
above would throw a `badmatch' error. The first two (we assume they do
|
227
|
+
not get a `badmatch') would simply return `[]' and `[1]', respectively,
|
228
|
+
so both succeed. (Note that EUnit is not psychic: if you write a test
|
229
|
+
that returns a value, even if it is the wrong value, EUnit will consider
|
230
|
+
it a success. You must make sure that the test is written so that it
|
231
|
+
causes a crash if the result is not what it should be.)
|
232
|
+
|
233
|
+
==== Using assert macros ====
|
234
|
+
|
235
|
+
If you want to use Boolean operators for your tests, the `assert'
|
236
|
+
macro comes in handy (see {@section EUnit macros} for details):
|
237
|
+
```length_test() -> ?assert(length([1,2,3]) == 3).'''
|
238
|
+
The `?assert(Expression)' macro will evaluate `Expression', and if that
|
239
|
+
does not evaluate to `true', it will throw an exception; otherwise it
|
240
|
+
just returns `ok'. In the above example, the test will thus fail if the
|
241
|
+
call to `length' does not return 3.
|
242
|
+
|
243
|
+
=== Running EUnit ===
|
244
|
+
|
245
|
+
If you have added the declaration
|
246
|
+
`-include_lib("eunit/include/eunit.hrl")' to your module, as described
|
247
|
+
above, you only need to compile the module, and run the automatically
|
248
|
+
exported function `test()'. For example, if your module was named `m',
|
249
|
+
then calling `m:test()' will run EUnit on all the tests defined in the
|
250
|
+
module. You do not need to write `-export' declarations for the test
|
251
|
+
functions. This is all done by magic.
|
252
|
+
|
253
|
+
==== EUnit captures standard output ====
|
254
|
+
|
255
|
+
If your test code writes to the standard output, you may be surprised to
|
256
|
+
see that the text does not appear on the console when the tests are
|
257
|
+
running. This is because EUnit captures all standard output from test
|
258
|
+
functions (this also includes setup and cleanup functions, but not
|
259
|
+
generator functions), so that it can be included in the test report if
|
260
|
+
errors occur. To bypass EUnit and print text directly to the console
|
261
|
+
while testing, you can write to the 'user' output stream, as in
|
262
|
+
`io:format(user, "~w", [Term])'. The recommended way of doing this is to
|
263
|
+
use the EUnit {@section Debugging Macros}, which make it much simpler.
|
264
|
+
|
265
|
+
=== Writing test generating functions ===
|
266
|
+
|
267
|
+
A drawback of simple test functions is that you must write a separate
|
268
|
+
function (with a separate name) for each test case. A more compact way
|
269
|
+
of writing tests (and much more flexible, as we shall see), is to write
|
270
|
+
functions that <em>return</em> tests, instead of <em>being</em> tests.
|
271
|
+
|
272
|
+
A function with a name ending in `..._test_()' (note the final
|
273
|
+
underscore) is recognized by EUnit as a <em>test generator</em>
|
274
|
+
function. Test generators return a <em>representation</em> of a <em>set
|
275
|
+
of tests</em> to be executed by EUnit.
|
276
|
+
|
277
|
+
==== Representing a test as data ====
|
278
|
+
|
279
|
+
The most basic representation of a test is a single fun-expression that
|
280
|
+
takes no arguments. For example, the following test generator:
|
281
|
+
```basic_test_() ->
|
282
|
+
fun () -> ?assert(1 + 1 == 2) end.'''
|
283
|
+
will have the same effect as the following simple test:
|
284
|
+
```simple_test() ->
|
285
|
+
?assert(1 + 1 == 2).'''
|
286
|
+
(in fact, EUnit will handle all simple tests just like it handles
|
287
|
+
fun-expressions: it will put them in a list, and run them one by one).
|
288
|
+
|
289
|
+
==== Using macros to write tests ====
|
290
|
+
|
291
|
+
To make tests more compact and readable, as well as automatically add
|
292
|
+
information about the line number in the source code where a test
|
293
|
+
occurred (and reduce the number of characters you have to type), you can
|
294
|
+
use the `_test' macro (note the initial underscore character), like
|
295
|
+
this:
|
296
|
+
```basic_test_() ->
|
297
|
+
?_test(?assert(1 + 1 == 2)).'''
|
298
|
+
The `_test' macro takes any expression (the "body") as argument, and
|
299
|
+
places it within a fun-expression (along with some extra information).
|
300
|
+
The body can be any kind of test expression, just like the body of a
|
301
|
+
simple test function.
|
302
|
+
|
303
|
+
==== Underscore-prefixed macros create test objects ====
|
304
|
+
|
305
|
+
But this example can be made even shorter! Most test macros, such as the
|
306
|
+
family of `assert' macros, have a corresponding form with an initial
|
307
|
+
underscore character, which automatically adds a `?_test(...)' wrapper.
|
308
|
+
The above example can then simply be written:
|
309
|
+
```basic_test_() ->
|
310
|
+
?_assert(1 + 1 == 2).'''
|
311
|
+
which has exactly the same meaning (note the `_assert' instead of
|
312
|
+
`assert'). You can think of the initial underscore as signalling
|
313
|
+
<em>test object</em>.
|
314
|
+
|
315
|
+
=== An example ===
|
316
|
+
|
317
|
+
Sometimes, an example says more than a thousand words. The following
|
318
|
+
small Erlang module shows how EUnit can be used in practice.
|
319
|
+
```-module(fib).
|
320
|
+
-export([fib/1]).
|
321
|
+
-include_lib("eunit/include/eunit.hrl").
|
322
|
+
|
323
|
+
fib(0) -> 1;
|
324
|
+
fib(1) -> 1;
|
325
|
+
fib(N) when N > 1 -> fib(N-1) + fib(N-2).
|
326
|
+
|
327
|
+
fib_test_() ->
|
328
|
+
[?_assert(fib(0) == 1),
|
329
|
+
?_assert(fib(1) == 1),
|
330
|
+
?_assert(fib(2) == 2),
|
331
|
+
?_assert(fib(3) == 3),
|
332
|
+
?_assert(fib(4) == 5),
|
333
|
+
?_assert(fib(5) == 8),
|
334
|
+
?_assertException(error, function_clause, fib(-1)),
|
335
|
+
?_assert(fib(31) == 2178309)
|
336
|
+
].'''
|
337
|
+
|
338
|
+
(Author's note: When I first wrote this example, I happened to write a
|
339
|
+
`*' instead of `+' in the `fib' function. Of course, this showed up
|
340
|
+
immediately when I ran the tests.)
|
341
|
+
|
342
|
+
See {@section EUnit test representation} for a full list of all the ways
|
343
|
+
you can specify test sets in EUnit.
|
344
|
+
|
345
|
+
=== Disabling testing ===
|
346
|
+
|
347
|
+
Testing can be turned off by defining the `NOTEST' macro when compiling,
|
348
|
+
for example as an option to `erlc', as in:
|
349
|
+
```erlc -DNOTEST my_module.erl'''
|
350
|
+
or by adding a macro definition to the code, <em>before the EUnit header
|
351
|
+
file is included</em>:
|
352
|
+
```-define(NOTEST, 1).'''
|
353
|
+
(the value is not important, but should typically be 1 or `true').
|
354
|
+
Note that unless the `EUNIT_NOAUTO' macro is defined, disabling testing
|
355
|
+
will also automatically strip all test functions from the code, except
|
356
|
+
for any that are explicitly declared as exported.
|
357
|
+
|
358
|
+
For instance, to use EUnit in your application, but with testing turned
|
359
|
+
off by default, put the following lines in a header file:
|
360
|
+
```-define(NOTEST, true).
|
361
|
+
-include_lib("eunit/include/eunit.hrl").'''
|
362
|
+
and then make sure that every module of your application includes that
|
363
|
+
header file. This means that you have a only a single place to modify in
|
364
|
+
order to change the default setting for testing. To override the `NOTEST'
|
365
|
+
setting without modifying the code, you can define `TEST' in a compiler
|
366
|
+
option, like this:
|
367
|
+
```erlc -DTEST my_module.erl'''
|
368
|
+
|
369
|
+
See {@section Compilation control macros} for details about these
|
370
|
+
macros.
|
371
|
+
|
372
|
+
=== Avoiding compile-time dependency on EUnit ===
|
373
|
+
|
374
|
+
If you are distributing the source code for your application for other
|
375
|
+
people to compile and run, you probably want to ensure that the code
|
376
|
+
compiles even if EUnit is not available. Like the example in the
|
377
|
+
previous section, you can put the following lines in a common header
|
378
|
+
file:
|
379
|
+
```-ifdef(TEST).
|
380
|
+
-include_lib("eunit/include/eunit.hrl").
|
381
|
+
-endif.'''
|
382
|
+
and, of course, also make sure that you place all test code that uses
|
383
|
+
EUnit macros within `-ifdef(TEST)' or `-ifdef(EUNIT)' sections.
|
384
|
+
|
385
|
+
|
386
|
+
== EUnit macros ==
|
387
|
+
|
388
|
+
Although all the functionality of EUnit is avaliable even without the
|
389
|
+
use of preprocessor macros, the EUnit header file defines a number of
|
390
|
+
such macros in order to make it as easy as possible to write unit tests
|
391
|
+
as compactly as possible and without getting too many details in the
|
392
|
+
way.
|
393
|
+
|
394
|
+
Except where explicitly stated, using EUnit macros will never introduce
|
395
|
+
run-time dependencies on the EUnit library code, regardless of whether
|
396
|
+
your code is compiled with testing enabled or disabled.
|
397
|
+
|
398
|
+
<ul>
|
399
|
+
<li>{@section Basic macros}</li>
|
400
|
+
<li>{@section Compilation control macros}</li>
|
401
|
+
<li>{@section Utility macros}</li>
|
402
|
+
<li>{@section Assert macros}</li>
|
403
|
+
<li>{@section Macros for running external commands}</li>
|
404
|
+
<li>{@section Debugging Macros}</li>
|
405
|
+
</ul>
|
406
|
+
|
407
|
+
=== Basic macros ===
|
408
|
+
|
409
|
+
<dl>
|
410
|
+
<dt>`_test(Expr)'</dt>
|
411
|
+
<dd>Turns `Expr' into a "test object", by wrapping it in a
|
412
|
+
fun-expression and a source line number. Technically, this is the same
|
413
|
+
as `{?LINE, fun () -> (Expr) end}'.
|
414
|
+
</dd>
|
415
|
+
</dl>
|
416
|
+
|
417
|
+
=== Compilation control macros ===
|
418
|
+
|
419
|
+
<dl>
|
420
|
+
<dt>`EUNIT'</dt>
|
421
|
+
<dd>This macro is always defined to `true' whenever EUnit is enabled at
|
422
|
+
compile time. This is typically used to place testing code within
|
423
|
+
conditional compilation, as in:
|
424
|
+
```-ifdef(EUNIT).
|
425
|
+
% test code here
|
426
|
+
...
|
427
|
+
-endif.'''
|
428
|
+
e.g., to ensure that the code can be compiled without including the
|
429
|
+
EUnit header file, when testing is disabled. See also the macros `TEST'
|
430
|
+
and `NOTEST'.
|
431
|
+
</dd>
|
432
|
+
<dt>`TEST'</dt>
|
433
|
+
<dd>This macro is always defined (to `true', unless previously defined
|
434
|
+
by the user to have another value) whenever EUnit is enabled at compile
|
435
|
+
time. This can be used to place testing code within conditional
|
436
|
+
compilation; see also the macros `NOTEST' and `EUNIT'.
|
437
|
+
|
438
|
+
For testing code that is strictly dependent on EUnit, it may be
|
439
|
+
preferable to use the `EUNIT' macro for this purpose, while for code
|
440
|
+
that uses more generic testing conventions, using the `TEST' macro may
|
441
|
+
be preferred.
|
442
|
+
|
443
|
+
The `TEST' macro can also be used to override the `NOTEST' macro. If
|
444
|
+
`TEST' is defined <em>before</em> the EUnit header file is
|
445
|
+
included (even if `NOTEST' is also defined), then the code will be
|
446
|
+
compiled with EUnit enabled.
|
447
|
+
</dd>
|
448
|
+
<dt>`NOTEST'</dt>
|
449
|
+
<dd>This macro is always defined (to `true', unless previously defined
|
450
|
+
by the user to have another value) whenever EUnit is <em>disabled</em>
|
451
|
+
at compile time. (Compare the `TEST' macro.)
|
452
|
+
|
453
|
+
This macro can also be used for conditional compilation, but is more
|
454
|
+
typically used to disable testing: If `NOTEST' is defined
|
455
|
+
<em>before</em> the EUnit header file is included, and `TEST'
|
456
|
+
is <em>not</em> defined, then the code will be compiled with EUnit
|
457
|
+
disabled. See also {@section Disabling testing}.
|
458
|
+
</dd>
|
459
|
+
|
460
|
+
<dt>`EUNIT_NOAUTO'</dt>
|
461
|
+
<dd>If this macro is defined, the automatic exporting or stripping of
|
462
|
+
test functions will be disabled.
|
463
|
+
</dd>
|
464
|
+
</dl>
|
465
|
+
|
466
|
+
=== Utility macros ===
|
467
|
+
|
468
|
+
The following macros can make tests more compact and readable:
|
469
|
+
|
470
|
+
<dl>
|
471
|
+
<dt>`LET(Var,Arg,Expr)'</dt>
|
472
|
+
<dd>Creates a local binding `Var = Arg' in `Expr'. (This is the same as
|
473
|
+
`(fun(Var)->(Expr)end)(Arg)'.) Note that the binding is not exported
|
474
|
+
outside of `Expr', and that within `Expr', this binding of `Var' will
|
475
|
+
shadow any binding of `Var' in the surrounding scope.
|
476
|
+
</dd>
|
477
|
+
<dt>`IF(Cond,TrueCase,FalseCase)'</dt>
|
478
|
+
<dd>Evaluates `TrueCase' if `Cond' evaluates to `true', or otherwise
|
479
|
+
evaluates `FalseCase' if `Cond' evaluates to `false'. (This is the same
|
480
|
+
as `(case (Cond) of true->(TrueCase); false->(FalseCase) end)'.) Note
|
481
|
+
that it is an error if `Cond' does not yield a boolean value.
|
482
|
+
</dd>
|
483
|
+
</dl>
|
484
|
+
|
485
|
+
=== Assert macros ===
|
486
|
+
|
487
|
+
(Note that these macros also have corresponding forms which start with
|
488
|
+
an "`_'" (underscore) character, as in `?_assert(BoolExpr)', that create
|
489
|
+
a "test object" instead of performing the test immediately. This is
|
490
|
+
equivalent to writing `?_test(assert(BoolExpr))', etc.)
|
491
|
+
|
492
|
+
<dl>
|
493
|
+
<dt>`assert(BoolExpr)'</dt>
|
494
|
+
<dd>Evaluates the expression `BoolExpr', if testing is enabled. Unless
|
495
|
+
the result is `true', an informative exception will be generated. If
|
496
|
+
there is no exception, the result of the macro expression is the atom
|
497
|
+
`ok', and the value of `BoolExpr' is discarded. If testing is disabled,
|
498
|
+
the macro will not generate any code except the atom `ok', and
|
499
|
+
`BoolExpr' will not be evaluated.
|
500
|
+
|
501
|
+
Typical usage:
|
502
|
+
```?assert(f(X, Y) == [])'''
|
503
|
+
|
504
|
+
The `assert' macro can be used anywhere in a program, not just in unit
|
505
|
+
tests, to check pre/postconditions and invariants. For example:
|
506
|
+
```some_recursive_function(X, Y, Z) ->
|
507
|
+
?assert(X + Y > Z),
|
508
|
+
...'''
|
509
|
+
</dd>
|
510
|
+
<dt>`assertNot(BoolExpr)'</dt>
|
511
|
+
<dd>Equivalent to `assert(not (BoolExpr))'.
|
512
|
+
</dd>
|
513
|
+
<dt>`assertMatch(GuardedPattern, Expr)'</dt>
|
514
|
+
<dd>Evaluates `Expr' and matches the result against `GuardedPattern', if
|
515
|
+
testing is enabled. If the match fails, an informative exception will be
|
516
|
+
generated; see the `assert' macro for further details. `GuardedPattern'
|
517
|
+
can be anything that you can write on the left hand side of the `->'
|
518
|
+
symbol in a case-clause, except that it cannot contain comma-separated
|
519
|
+
guard tests.
|
520
|
+
|
521
|
+
The main reason for using `assertMatch' also for simple matches, instead
|
522
|
+
of matching with `=', is that it produces more detailed error messages.
|
523
|
+
|
524
|
+
Examples:
|
525
|
+
```?assertMatch({found, {fred, _}}, lookup(bloggs, Table))'''
|
526
|
+
```?assertMatch([X|_] when X > 0, binary_to_list(B))'''
|
527
|
+
</dd>
|
528
|
+
<dt>`assertEqual(Expect, Expr)'</dt>
|
529
|
+
<dd>Evaluates the expressions `Expect' and `Expr' and compares the
|
530
|
+
results for equality, if testing is enabled. If the values are not
|
531
|
+
equal, an informative exception will be generated; see the `assert'
|
532
|
+
macro for further details.
|
533
|
+
|
534
|
+
`assertEqual' is more suitable than than `assertMatch' when the
|
535
|
+
left-hand side is a computed value rather than a simple pattern, and
|
536
|
+
gives more details than `?assert(Expect =:= Expr)'.
|
537
|
+
|
538
|
+
Examples:
|
539
|
+
```?assertEqual("b" ++ "a", lists:reverse("ab"))'''
|
540
|
+
```?assertEqual(foo(X), bar(Y))'''
|
541
|
+
</dd>
|
542
|
+
<dt>`assertException(ClassPattern, TermPattern, Expr)'</dt>
|
543
|
+
<dt>`assertError(TermPattern, Expr)'</dt>
|
544
|
+
<dt>`assertExit(TermPattern, Expr)'</dt>
|
545
|
+
<dt>`assertThrow(TermPattern, Expr)'</dt>
|
546
|
+
<dd>Evaluates `Expr', catching any exception and testing that it matches
|
547
|
+
the expected `ClassPattern:TermPattern'. If the match fails, or if no
|
548
|
+
exception is thrown by `Expr', an informative exception will be
|
549
|
+
generated; see the `assert' macro for further details. The
|
550
|
+
`assertError', `assertExit', and `assertThrow' macros, are equivalent to
|
551
|
+
using `assertException' with a `ClassPattern' of `error', `exit', or
|
552
|
+
`throw', respectively.
|
553
|
+
|
554
|
+
Examples:
|
555
|
+
```?assertError(badarith, X/0)'''
|
556
|
+
```?assertExit(normal, exit(normal))'''
|
557
|
+
```?assertException(throw, {not_found,_}, throw({not_found,42}))'''
|
558
|
+
</dd>
|
559
|
+
</dl>
|
560
|
+
|
561
|
+
=== Macros for running external commands ===
|
562
|
+
|
563
|
+
Keep in mind that external commands are highly dependent on the
|
564
|
+
operating system. You can use the standard library function `os:type()'
|
565
|
+
in test generator functions, to produce different sets of tests
|
566
|
+
depending on the current operating system.
|
567
|
+
|
568
|
+
Note: these macros introduce a run-time dependency on the EUnit library
|
569
|
+
code, if compiled with testing enabled.
|
570
|
+
|
571
|
+
<dl>
|
572
|
+
<dt>`assertCmd(CommandString)'</dt>
|
573
|
+
<dd>Runs `CommandString' as an external command, if testing is enabled.
|
574
|
+
Unless the returned status value is 0, an informative exception will be
|
575
|
+
generated. If there is no exception, the result of the macro expression
|
576
|
+
is the atom `ok'. If testing is disabled, the macro will not generate
|
577
|
+
any code except the atom `ok', and the command will not be executed.
|
578
|
+
|
579
|
+
Typical usage:
|
580
|
+
```?assertCmd("mkdir foo")'''
|
581
|
+
</dd>
|
582
|
+
<dt>`assertCmdStatus(N, CommandString)'</dt>
|
583
|
+
<dd>Like the `assertCmd(CommandString)' macro, but generates an
|
584
|
+
exception unless the returned status value is `N'.
|
585
|
+
</dd>
|
586
|
+
<dt>`assertCmdOutput(Text, CommandString)'</dt>
|
587
|
+
<dd>Runs `CommandString' as an external command, if testing is enabled.
|
588
|
+
Unless the output produced by the command exactly matches the specified
|
589
|
+
string `Text', an informative exception will be generated. (Note that
|
590
|
+
the output is normalized to use a single LF character as line break on
|
591
|
+
all platforms.) If there is no exception, the result of the macro
|
592
|
+
expression is the atom `ok'. If testing is disabled, the macro will not
|
593
|
+
generate any code except the atom `ok', and the command will not be
|
594
|
+
executed.
|
595
|
+
</dd>
|
596
|
+
<dt>`cmd(CommandString)'</dt>
|
597
|
+
<dd>Runs `CommandString' as an external command. Unless the returned
|
598
|
+
status value is 0 (indicating success), an informative exception will be
|
599
|
+
generated; otherwise, the result of the macro expression is the output
|
600
|
+
produced by the command, as a flat string. The output is normalized to
|
601
|
+
use a single LF character as line break on all platforms.
|
602
|
+
|
603
|
+
This macro is useful in the setup and cleanup sections of fixtures,
|
604
|
+
e.g., for creating and deleting files or perform similar operating
|
605
|
+
system specific tasks, to make sure that the test system is informed of
|
606
|
+
any failures.
|
607
|
+
|
608
|
+
A Unix-specific example:
|
609
|
+
```{setup,
|
610
|
+
fun () -> ?cmd("mktemp") end,
|
611
|
+
fun (FileName) -> ?cmd("rm " ++ FileName) end,
|
612
|
+
...}'''
|
613
|
+
</dd>
|
614
|
+
</dl>
|
615
|
+
|
616
|
+
=== Debugging Macros ===
|
617
|
+
|
618
|
+
To help with debugging, EUnit defines several useful macros for printing
|
619
|
+
messages directly to the console (rather than to the standard output).
|
620
|
+
Furthermore, these macros all use the same basic format, which includes
|
621
|
+
the file and line number where they occur, making it possible in some
|
622
|
+
development environments (e.g., when running Erlang in an Emacs buffer)
|
623
|
+
to simply click on the message and jump directly to the corresponding
|
624
|
+
line in the code.
|
625
|
+
|
626
|
+
If the macro `NODEBUG' is defined before the EUnit header file is
|
627
|
+
included, these macros have no effect.
|
628
|
+
|
629
|
+
<dl>
|
630
|
+
<dt>`debugHere'</dt>
|
631
|
+
<dd>Just prints a marker showing the current file and line number. Note
|
632
|
+
that this is an argument-less macro. The result is always `ok'.</dd>
|
633
|
+
<dt>`debugMsg(Text)'</dt>
|
634
|
+
<dd>Outputs the message `Text' (which can be a plain string, an IO-list,
|
635
|
+
or just an atom). The result is always `ok'.</dd>
|
636
|
+
<dt>`debugFmt(FmtString, Args)'</dt>
|
637
|
+
<dd>This formats the text like `io:format(FmtString, Args)' and outputs
|
638
|
+
it like `debugMsg'. The result is always `ok'.</dd>
|
639
|
+
<dt>`debugVal(Expr)'</dt>
|
640
|
+
<dd>Prints both the source code for `Expr' and its current value. E.g.,
|
641
|
+
`?debugVal(f(X))' might be displayed as "`f(X) = 42'". (Large terms are
|
642
|
+
shown truncated.) The result is always the value of `Expr', so this
|
643
|
+
macro can be wrapped around any expression to display its value when
|
644
|
+
the code is compiled with debugging enabled.</dd>
|
645
|
+
<dt>`debugTime(Text,Expr)'</dt>
|
646
|
+
<dd>Prints `Text' and the wall clock time for evaluation of `Expr'. The
|
647
|
+
result is always the value of `Expr', so this macro can be wrapped
|
648
|
+
around any expression to show its run time when the code is compiled
|
649
|
+
with debugging enabled. For example, `List1 = ?debugTime("sorting",
|
650
|
+
lists:sort(List))' might show as "`sorting: 0.015 s'".</dd>
|
651
|
+
|
652
|
+
</dl>
|
653
|
+
|
654
|
+
|
655
|
+
== EUnit test representation ==
|
656
|
+
|
657
|
+
The way EUnit represents tests and test sets as data is flexible,
|
658
|
+
powerful, and concise. This section describes the representation in
|
659
|
+
detail.
|
660
|
+
|
661
|
+
<ul>
|
662
|
+
<li>{@section Simple test objects}</li>
|
663
|
+
<li>{@section Test sets and deep lists}</li>
|
664
|
+
<li>{@section Titles}</li>
|
665
|
+
<li>{@section Primitives}</li>
|
666
|
+
<li>{@section Control}</li>
|
667
|
+
<li>{@section Fixtures}</li>
|
668
|
+
<li>{@section Lazy generators}</li>
|
669
|
+
</ul>
|
670
|
+
|
671
|
+
=== Simple test objects ===
|
672
|
+
|
673
|
+
A <em>simple test object</em> is one of the following:
|
674
|
+
<ul>
|
675
|
+
<li>A nullary functional value (i.e., a fun that takes zero
|
676
|
+
arguments). Examples:
|
677
|
+
```fun () -> ... end'''
|
678
|
+
```fun some_function/0'''
|
679
|
+
```fun some_module:some_function/0'''
|
680
|
+
</li>
|
681
|
+
<li>A pair of atoms `{ModuleName, FunctionName}', referring to the
|
682
|
+
function `ModuleName:FunctionName/0'</li>
|
683
|
+
<li>A pair `{LineNumber, SimpleTest}', where `LineNumber' is a
|
684
|
+
nonnegative integer and `SimpleTest' is another simple test
|
685
|
+
object. `LineNumber' should indicate the source line of the test.
|
686
|
+
Pairs like this are usually only created via `?_test(...)' macros;
|
687
|
+
see {@section Basic macros}.</li>
|
688
|
+
</ul>
|
689
|
+
In brief, a simple test object consists of a single function that takes
|
690
|
+
no arguments (possibly annotated with some additional metadata, i.e., a
|
691
|
+
line number). Evaluation of the function either <em>succeeds</em>, by
|
692
|
+
returning some value (which is ignored), or <em>fails</em>, by throwing
|
693
|
+
an exception.
|
694
|
+
|
695
|
+
=== Test sets and deep lists ===
|
696
|
+
|
697
|
+
A test set can be easily created by placing a sequence of test objects
|
698
|
+
in a list. If `T_1', ..., `T_N' are individual test objects, then `[T_1,
|
699
|
+
..., T_N]' is a test set consisting of those objects (in that order).
|
700
|
+
|
701
|
+
Test sets can be joined in the same way: if `S_1', ..., `S_K' are test
|
702
|
+
sets, then `[S_1, ..., S_K]' is also a test set, where the tests of
|
703
|
+
`S_i' are ordered before those of `S_(i+1)', for each subset `S_i'.
|
704
|
+
|
705
|
+
Thus, the main representation of test sets is <em>deep lists</em>, and
|
706
|
+
a simple test object can be viewed as a test set containing only a
|
707
|
+
single test; there is no difference between `T' and `[T]'.
|
708
|
+
|
709
|
+
|
710
|
+
=== Titles ===
|
711
|
+
|
712
|
+
Any test or test set `T' can be annotated with a title, by wrapping it
|
713
|
+
in a pair `{Title, T}', where `Title' is a string. For convenience, any
|
714
|
+
test which is normally represented using a tuple can simply be given a
|
715
|
+
title string as the first element, i.e., writing `{"The Title", ...}'
|
716
|
+
instead of adding an extra tuple wrapper as in `{"The Title", {...}}'.
|
717
|
+
|
718
|
+
|
719
|
+
=== Primitives ===
|
720
|
+
|
721
|
+
The following are primitives, which do not contain other test sets as
|
722
|
+
arguments:
|
723
|
+
<dl>
|
724
|
+
<dt>`{generator, GenFun::(() -> Tests)}'
|
725
|
+
</dt>
|
726
|
+
<dd>The generator function `GenFun' is called to produce a test
|
727
|
+
set.
|
728
|
+
</dd>
|
729
|
+
<dt>`{generator, ModuleName::atom(), FunctionName::atom()}'
|
730
|
+
</dt>
|
731
|
+
<dd>The function `ModuleName:FunctionName()' is called to produce a test
|
732
|
+
set.
|
733
|
+
</dd>
|
734
|
+
<dt>`ModuleName::atom()'
|
735
|
+
</dt>
|
736
|
+
<dd>A single atom represents a module name, and is equivalent to
|
737
|
+
`{module, ModuleName}'. This is often used as in the call
|
738
|
+
`eunit:test(some_module)'.
|
739
|
+
</dd>
|
740
|
+
<dt>`{module, ModuleName::atom()}'
|
741
|
+
</dt>
|
742
|
+
<dd>This composes a test set from the exported test functions of the
|
743
|
+
named module, i.e., those functions with arity zero whose names end
|
744
|
+
with `_test' or `_test_'. Basically, the `..._test()' functions become
|
745
|
+
simple tests, while the `..._test_()' functions become generators.
|
746
|
+
|
747
|
+
In addition, EUnit will also look for another module whose name is
|
748
|
+
`ModuleName' plus the suffix `_tests', and if it exists, all the tests
|
749
|
+
from that module will also be added. (If `ModuleName' already contains
|
750
|
+
the suffix `_tests', this is not done.) E.g., the specification
|
751
|
+
`{module, mymodule}' will run all tests in the modules `mymodule' and
|
752
|
+
`mymodule_tests'. Typically, the `_tests' module should only contain
|
753
|
+
test cases that use the public interface of the main module (and no
|
754
|
+
other code).
|
755
|
+
</dd>
|
756
|
+
<dt>`{application, AppName::atom(), Info::list()}'
|
757
|
+
</dt>
|
758
|
+
<dd>This is a normal Erlang/OTP application descriptor, as found in an
|
759
|
+
`.app' file. The resulting test set consists of the modules listed in
|
760
|
+
the `modules' entry in `Info'.
|
761
|
+
</dd>
|
762
|
+
<dt>`{application, AppName::atom()}'
|
763
|
+
</dt>
|
764
|
+
<dd>This creates a test set from all the modules belonging to the
|
765
|
+
specified application, by consulting the application's `.app' file
|
766
|
+
(see `{file, FileName}'), or if no such file exists, by testing all
|
767
|
+
object files in the application's <tt>ebin</tt>-directory (see `{dir,
|
768
|
+
Path}'); if that does not exist, the `code:lib_dir(AppName)' directory
|
769
|
+
is used.
|
770
|
+
</dd>
|
771
|
+
<dt>`Path::string()'
|
772
|
+
</dt>
|
773
|
+
<dd>A single string represents the path of a file or directory, and is
|
774
|
+
equivalent to `{file, Path}', or `{dir, Path}', respectively, depending
|
775
|
+
on what `Path' refers to in the file system.
|
776
|
+
</dd>
|
777
|
+
<dt>`{file, FileName::string()}'
|
778
|
+
</dt>
|
779
|
+
<dd>If `FileName' has a suffix that indicates an object file (`.beam'),
|
780
|
+
EUnit will try to reload the module from the specified file and test it.
|
781
|
+
Otherwise, the file is assumed to be a text file containing test
|
782
|
+
specifications, which will be read using the standard library function
|
783
|
+
`file:path_consult/2'.
|
784
|
+
|
785
|
+
Unless the file name is absolute, the file is first searched for
|
786
|
+
relative to the current directory, and then using the normal search path
|
787
|
+
(`code:get_path()'). This means that the names of typical "app" files
|
788
|
+
can be used directly, without a path, e.g., `"mnesia.app"'.
|
789
|
+
</dd>
|
790
|
+
<dt>`{dir, Path::string()}'
|
791
|
+
</dt>
|
792
|
+
<dd>This tests all object files in the specified directory, as if they
|
793
|
+
had been individually specified using `{file, FileName}'.
|
794
|
+
</dd>
|
795
|
+
<dt>`{with, X::any(), [AbstractTestFun::((any()) -> any())]}'
|
796
|
+
</dt>
|
797
|
+
<dd>Distributes the value `X' over the unary functions in the list,
|
798
|
+
turning them into nullary test functions. An `AbstractTestFun' is like
|
799
|
+
an ordinary test fun, but takes one argument instead of zero - it's
|
800
|
+
basically missing some information before it can be a proper test. In
|
801
|
+
practice, `{with, X, [F_1, ..., F_N]}' is equivalent to `[fun () ->
|
802
|
+
F_1(X) end, ..., fun () -> F_N(X) end]'. This is particularly useful if
|
803
|
+
your abstract test functions are already implemented as proper
|
804
|
+
functions: `{with, FD, [fun filetest_a/1, fun filetest_b/1, fun
|
805
|
+
filetest_c/1]}' is equivalent to `[fun () -> filetest_a(FD) end, fun ()
|
806
|
+
-> filetest_b(FD) end, fun () -> filetest_c(FD) end]', but much more
|
807
|
+
compact. See also {@section Fixtures}, below.
|
808
|
+
</dd>
|
809
|
+
</dl>
|
810
|
+
|
811
|
+
=== Control ===
|
812
|
+
|
813
|
+
The following representations control how and where tests are executed:
|
814
|
+
<dl>
|
815
|
+
<dt>`{spawn, Tests}'</dt>
|
816
|
+
<dd>Runs the specified tests in a separate subprocess, while the current
|
817
|
+
test process waits for it to finish. This is useful for tests that need
|
818
|
+
a fresh, isolated process state. (Note that EUnit always starts at least
|
819
|
+
one such a subprocess automatically; tests are never executed by the
|
820
|
+
caller's own process.)</dd>
|
821
|
+
<dt>`{spawn, Node::atom(), Tests}'</dt>
|
822
|
+
<dd>Like `{spawn, Tests}', but runs the specified tests on the given
|
823
|
+
Erlang node.</dd>
|
824
|
+
<dt>`{timeout, Time::number(), Tests}'</dt>
|
825
|
+
<dd>Runs the specified tests under the given timeout. Time is in
|
826
|
+
seconds; e.g., 60 means one minute and 0.1 means 1/10th of a second. If
|
827
|
+
the timeout is exceeded, the unfinished tests will be forced to
|
828
|
+
terminate. Note that if a timeout is set around a fixture, it includes
|
829
|
+
the time for setup and cleanup, and if the timeout is triggered, the
|
830
|
+
entire fixture is abruptly terminated (without running the
|
831
|
+
cleanup).</dd>
|
832
|
+
<dt>`{inorder, Tests}'</dt>
|
833
|
+
<dd>Runs the specified tests in strict order. Also see `{inparallel,
|
834
|
+
Tests}'. By default, tests are neither marked as `inorder' or
|
835
|
+
`inparallel', but may be executed as the test framework chooses.</dd>
|
836
|
+
<dt>`{inparallel, Tests}'</dt>
|
837
|
+
<dd>Runs the specified tests in parallel (if possible). Also see
|
838
|
+
`{inorder, Tests}'.</dd>
|
839
|
+
<dt>`{inparallel, N::integer(), Tests}'</dt>
|
840
|
+
<dd>Like `{inparallel, Tests}', but running no more than `N' subtests
|
841
|
+
simultaneously.</dd>
|
842
|
+
</dl>
|
843
|
+
|
844
|
+
=== Fixtures ===
|
845
|
+
|
846
|
+
A "fixture" is some state that is necessary for a particular set of
|
847
|
+
tests to run. EUnit's support for fixtures makes it easy to set up such
|
848
|
+
state locally for a test set, and automatically tear it down again when
|
849
|
+
the test set is finished, regardless of the outcome (success, failures,
|
850
|
+
timeouts, etc.).
|
851
|
+
|
852
|
+
To make the descriptions simpler, we first list some definitions:
|
853
|
+
<center>
|
854
|
+
<table border="0" cellspacing="4">
|
855
|
+
<tr>
|
856
|
+
<td>`Setup'</td><td>`() -> (R::any())'</td>
|
857
|
+
</tr>
|
858
|
+
<tr>
|
859
|
+
<td>`SetupX'</td><td>`(X::any()) -> (R::any())'</td>
|
860
|
+
</tr>
|
861
|
+
<tr>
|
862
|
+
<td>`Cleanup'</td><td>`(R::any()) -> any()'</td>
|
863
|
+
</tr>
|
864
|
+
<tr>
|
865
|
+
<td>`CleanupX'</td><td>`(X::any(), R::any()) -> any()'</td>
|
866
|
+
</tr>
|
867
|
+
<tr>
|
868
|
+
<td>`Instantiator'</td><td>`((R::any()) -> Tests) | {with, [AbstractTestFun::((any()) -> any())]}'</td>
|
869
|
+
</tr>
|
870
|
+
<tr>
|
871
|
+
<td>`Where'</td><td>`local | spawn | {spawn, Node::atom()}'</td>
|
872
|
+
</tr>
|
873
|
+
</table>
|
874
|
+
</center>
|
875
|
+
(these are explained in more detail further below.)
|
876
|
+
|
877
|
+
The following representations specify fixture handling for test sets:
|
878
|
+
<dl>
|
879
|
+
<dt>`{setup, Setup, Tests | Instantiator}'</dt>
|
880
|
+
<dt>`{setup, Setup, Cleanup, Tests | Instantiator}'</dt>
|
881
|
+
<dt>`{setup, Where, Setup, Tests | Instantiator}'</dt>
|
882
|
+
<dt>`{setup, Where, Setup, Cleanup, Tests | Instantiator}'</dt>
|
883
|
+
<dd>`setup' sets up a single fixture for running all of the specified
|
884
|
+
tests, with optional teardown afterwards. The arguments are described in
|
885
|
+
detail below.
|
886
|
+
</dd>
|
887
|
+
<dt>`{node, Node::atom(), Tests | Instantiator}'</dt>
|
888
|
+
<dt>`{node, Node::atom(), Args::string(), Tests | Instantiator}'</dt>
|
889
|
+
<dd>`node' is like `setup', but with a built-in behaviour: it starts a
|
890
|
+
slave node for the duration of the tests. The atom `Node' should have
|
891
|
+
the format `nodename@full.machine.name', and `Args' are the optional
|
892
|
+
arguments to the new node; see `slave:start_link/3' for details.
|
893
|
+
</dd>
|
894
|
+
<dt>`{foreach, Where, Setup, Cleanup, [Tests | Instantiator]}'</dt>
|
895
|
+
<dt>`{foreach, Setup, Cleanup, [Tests | Instantiator]}'</dt>
|
896
|
+
<dt>`{foreach, Where, Setup, [Tests | Instantiator]}'</dt>
|
897
|
+
<dt>`{foreach, Setup, [Tests | Instantiator]}'</dt>
|
898
|
+
<dd>`foreach' is used to set up a fixture and optionally tear it down
|
899
|
+
afterwards, repeated for each single one of the specified test sets.
|
900
|
+
</dd>
|
901
|
+
<dt>`{foreachx, Where, SetupX, CleanupX,
|
902
|
+
Pairs::[{X::any(), ((X::any(), R::any()) -> Tests)}]}'</dt>
|
903
|
+
<dt>`{foreachx, SetupX, CleanupX, Pairs}'</dt>
|
904
|
+
<dt>`{foreachx, Where, SetupX, Pairs}'</dt>
|
905
|
+
<dt>`{foreachx, SetupX, Pairs}'</dt>
|
906
|
+
<dd>`foreachx' is like `foreach', but uses a list of pairs, each
|
907
|
+
containing an extra argument `X' and an extended instantiator function.
|
908
|
+
</dd>
|
909
|
+
</dl>
|
910
|
+
|
911
|
+
A `Setup' function is executed just before any of the specified tests
|
912
|
+
are run, and a `Cleanup' function is executed when no more of the
|
913
|
+
specified tests will be run, regardless of the reason. A `Setup'
|
914
|
+
function takes no argument, and returns some value which will be passed
|
915
|
+
as it is to the `Cleanup' function. A `Cleanup' function should do
|
916
|
+
whatever necessary and return some arbitrary value, such as the atom
|
917
|
+
`ok'. (`SetupX' and `CleanupX' functions are similar, but receive one
|
918
|
+
additional argument: some value `X', which depends on the context.) When
|
919
|
+
no `Cleanup' function is specified, a dummy function is used which has
|
920
|
+
no effect.
|
921
|
+
|
922
|
+
An `Instantiator' function receives the same value as the `Cleanup'
|
923
|
+
function, i.e., the value returned by the `Setup' function. It should
|
924
|
+
then behave much like a generator (see {@section Primitives}), and
|
925
|
+
return a test set whose tests have been <em>instantiated</em> with the
|
926
|
+
given value. A special case is the syntax `{with, [AbstractTestFun]}'
|
927
|
+
which represents an instantiator function that distributes the value
|
928
|
+
over a list of unary functions; see {@section Primitives}: `{with, X,
|
929
|
+
[...]}' for more details.
|
930
|
+
|
931
|
+
A `Where' term controls how the specified tests are executed. The
|
932
|
+
default is `spawn', which means that the current process handles the
|
933
|
+
setup and teardown, while the tests are executed in a subprocess.
|
934
|
+
`{spawn, Node}' is like `spawn', but runs the subprocess on the
|
935
|
+
specified node. `local' means that the current process will handle both
|
936
|
+
setup/teardown and running the tests - the drawback is that if a test
|
937
|
+
times out so that the process is killed, the <em>cleanup will not be
|
938
|
+
performed</em>; hence, avoid this for persistent fixtures such as file
|
939
|
+
operations. In general, 'local' should only be used when:
|
940
|
+
<ul>
|
941
|
+
<li>the setup/teardown needs to be executed by the process that will
|
942
|
+
run the tests;</li>
|
943
|
+
<li>no further teardown needs to be done if the process is killed
|
944
|
+
(i.e., no state outside the process was affected by the setup)</li>
|
945
|
+
</ul>
|
946
|
+
|
947
|
+
=== Lazy generators ===
|
948
|
+
|
949
|
+
Sometimes, it can be convenient not to produce the whole set of test
|
950
|
+
descriptions before the testing begins; for example, if you want to
|
951
|
+
generate a huge amount of tests that would take up too much space to
|
952
|
+
keep in memory all at once.
|
953
|
+
|
954
|
+
It is fairly easy to write a generator which, each time it is called,
|
955
|
+
either produces an empty list if it is done, or otherwise produces a
|
956
|
+
list containing a single test case plus a new generator which will
|
957
|
+
produce the rest of the tests. This demonstrates the basic pattern:
|
958
|
+
|
959
|
+
```lazy_test_() ->
|
960
|
+
lazy_gen(10000).
|
961
|
+
|
962
|
+
lazy_gen(N) ->
|
963
|
+
{generator,
|
964
|
+
fun () ->
|
965
|
+
if N > 0 ->
|
966
|
+
[?_test(...)
|
967
|
+
| lazy_gen(N-1)];
|
968
|
+
true ->
|
969
|
+
[]
|
970
|
+
end
|
971
|
+
end}.'''
|
972
|
+
|
973
|
+
When EUnit traverses the test representation in order to run the tests,
|
974
|
+
the new generator will not be called to produce the next test until the
|
975
|
+
previous test has been executed.
|
976
|
+
|
977
|
+
Note that it is easiest to write this kind of recursive generator using
|
978
|
+
a help function, like the `lazy_gen/1' function above. It can also be
|
979
|
+
written using a recursive fun, if you prefer to not clutter your
|
980
|
+
function namespace and are comfortable with writing that kind of code.
|