_build/mim2/rel/mongooseim/bin/mongooseimctl started _build/mim1/rel/mongooseim/bin/mongooseimctl started Tmux new-window -n reg1 '_build/fed1/rel/mongooseim/bin/mongooseimctl live' Tmux new-window -n fed1 '_build/fed1/rel/mongooseim/bin/mongooseimctl live' Tmux new-window -n mim3 '_build/mim3/rel/mongooseim/bin/mongooseimctl live' Tmux new-window -n mim2 '_build/mim2/rel/mongooseim/bin/mongooseimctl live' Tmux new-window -n mim1 '_build/mim1/rel/mongooseim/bin/mongooseimctl live' Wait for the tests to finish and celebrate (or wallow in despair and grief)! In shell #6: $ cd $MONGOOSEIM/_build/reg1/rel/mongooseim In shell #5: $ cd $MONGOOSEIM/_build/fed1/rel/mongooseim In shell #4: $ cd $MONGOOSEIM/_build/mim3/rel/mongooseim In shell #3: $ cd $MONGOOSEIM/_build/mim2/rel/mongooseim In shell #2: $ cd $MONGOOSEIM/_build/mim1/rel/mongooseim tools/test-runner.sh -skip-small-tests -db mssql -preset rdbms_mssql_mnesia -test-hosts mim -dev-nodes mim1 - rdbms -skip-cover # Inits a single MongooseIM node (works for some tests only) tools/test-runner.sh -skip-small-tests -db mysql pgsql -preset mysql_mnesia pgsql_mnesia - mam:rdbms_muc_light # Runs MAM tests for MUC light with MySQL and Postgres tools/test-runner.sh -skip-small-tests -db mysql -preset mysql_mnesia - privacy private Most important options are preset and database: # Runs privacy_SUITE and private_SUITE with MySQL tools/test-runner.sh -skip-big-tests ejabberd_config:reload_cluster -verboseĮnd-to-end tests (a.k.a. # Run reload_cluster group in ejabberd_config_SUITE, show progress tools/test-runner.sh -skip-big-tests sha -skip-cover tools/test-runner.sh -skip-big-tests -verbose Unit test running example using test runner: # Run all small tests, show progress If any of the tests fail the summary log is printed to stdout.ĭetailed test results in a nice HTML format are saved in _build/test/logs/ct_run./ If all the tests pass, you wll get no output and summary log will be available in ct.log. Rebar recompiles all the code automatically, there is no need for a separate compilation step. rebar3 ct -suite test/my_selected_SUITE. rebar3 ct to run just a selected suite, use. The test suites are located in test/ directory. They are very useful for developing/debugging libraries. These test suites are aimed at testing various modules and libraries standalone, without launching a MongooseIM instance. skip-small-tests -skip-setup-db -dev-nodes -test-hosts -skip-cover -skip-preset.Īnd mam is used to run mam_SUITE suite only. tools/test-runner.sh -rerun-big-tests - mam We can just execute the same command, but it would rebuild nodes and start skip-stop-nodes is optional here, because if any big test fails, then nodes tools/test-runner.sh -skip-small-tests -db mysql -preset mysql_mnesia -skip-stop-nodes Very often we want to restart a specific suite when some test failed.įor example, some test has failed in mam_SUITE. tools/test-runner.sh -show-small-reports To enable completion in bash or zsh, run: source tools/test-runner-complete.sh Test runner supports shell TAB completion. The command runs both big (feature) and small (unit) tests. tools/test-runner.sh -db redis -preset internal_mnesia The help command prints a list of supported options./tools/test-runner.sh -help The test runner script is used to compile MongooseIM and run tests. Reloading configuration on a running system. Cluster configuration and node management.How to Build MongooseIM from source code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |