text:
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>

    <copyright>
      <year>2003</year><year>2016</year>
      <holder>Ericsson AB. All Rights Reserved.</holder>
    </copyright>
    <legalnotice>
      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at

          http://www.apache.org/licenses/LICENSE-2.0

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.

    </legalnotice>

    <title>Running Tests and Analyzing Results</title>
    <prepared>Peter Andersson, Kenneth Lundin</prepared>
    <docno></docno>
    <date></date>
    <rev></rev>
    <file>run_test_chapter.xml</file>

    <title>Using the Common Test Framework</title>

The <c>Common Test</c> framework provides a high-level
    operator interface for testing, providing the following features:

    <list type="bulleted">
	<item>Automatic compilation of test suites (and help modules)</item>
	<item>Creation of extra HTML pages for improved overview.</item>
	<item>Single-command interface for running all available tests</item>
	<item>Handling of configuration files specifying data related to
	  the System Under Test (SUT) (and any other variable data)</item>
	<item>Mode for running multiple independent test sessions in parallel with
	  central control and configuration</item>
      </list>

    <title>Automatic Compilation of Test Suites and Help Modules</title>

When <c>Common Test</c> starts, it automatically attempts to compile any
      suites included in the specified tests. If particular
      suites are specified, only those suites are compiled. If a
      particular test object directory is specified (meaning all suites
      in this directory are to be part of the test), <c>Common Test</c> runs
      function <c>make:all/1</c> in the directory to compile the suites.

If compilation fails for one or more suites, the compilation errors
      are printed to tty and the operator is asked if the test run is to proceed
      without the missing suites, or be aborted. If the operator chooses to proceed,
      the tests having missing suites are noted in the HTML log. If <c>Common Test</c> is
      unable to prompt the user after compilation failure (if <c>Common Test</c> does not
      control <c>stdin</c>), the test run proceeds automatically without the missing
      suites. This behavior can however be modified with the
      <c><![CDATA[ct_run]]></c> flag <c><![CDATA[-abort_if_missing_suites]]></c>,
      or the <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso> option
      <c><![CDATA[{abort_if_missing_suites,TrueOrFalse}]]></c>. If
      <c><![CDATA[abort_if_missing_suites]]></c> is set to <c>true</c>, the test run
      stops immediately if some suites fail to compile.

Any help module (that is, regular Erlang module with name not ending with
      "_SUITE") that resides in the same test object directory as a suite,
      which is part of the test, is also automatically compiled. A help
      module is not mistaken for a test suite (unless it has a "_SUITE" name).
      All help modules in a particular test object directory
      are compiled, no matter if all or only particular suites in the directory
      are part of the test.

If test suites or help modules include header files stored in other
      locations than the test directory, these include directories can be specified
      by using flag <c><![CDATA[-include]]></c> with
      <seealso marker="ct_run"><c>ct_run</c></seealso>,
      or option <c><![CDATA[include]]></c> with <c><![CDATA[ct:run_test/1]]></c>.
      Also, an include path can be specified with an OS
      environment variable, <c><![CDATA[CT_INCLUDE_PATH]]></c>.

Example (bash):

<c>$ export CT_INCLUDE_PATH=~testuser/common_suite_files/include:~testuser/common_lib_files/include</c>

<c>Common Test</c> passes all include directories (specified either with flag/option
      <c><![CDATA[include]]></c>, or variable <c><![CDATA[CT_INCLUDE_PATH]]></c>
      , or both, to the compiler.

Include directories can also be specified in test specifications,
      see <seealso marker="#test_specifications">Test Specifications</seealso>.

If the user wants to run all test suites for a test object (or an OTP application)
      by specifying only the top directory (for example, with start flag/option <c>dir</c>),
      <c>Common Test</c> primarily looks for test suite modules in a subdirectory named
      <c>test</c>. If this subdirectory does not exist, the specified top directory
      is assumed to be the test directory, and test suites are read from
      there instead.

To disable the automatic compilation feature, use flag
      <c><![CDATA[-no_auto_compile]]></c> with <c><![CDATA[ct_run]]></c>, or
      option <c><![CDATA[{auto_compile,false}]]></c> with
      <c><![CDATA[ct:run_test/1]]></c>. With automatic compilation
      disabled, the user is responsible for compiling the test suite modules
      (and any help modules) before the test run. If the modules cannot be loaded
      from the local file system during startup of <c>Common Test</c>, the user must
      preload the modules before starting the test. <c>Common Test</c> only verifies
      that the specified test suites exist (that is, that they are, or can be, loaded).
      This is useful, for example, if the test suites are transferred and loaded as
      binaries through RPC from a remote node.

  <marker id="ct_run"></marker>
    <title>Running Tests from the OS Command Line</title>

The <seealso marker="ct_run"><c>ct_run</c></seealso> program can be used
       for running tests from the OS command line, for example, as follows:

    <list type="bulleted">
      <item><c><![CDATA[ct_run -config <configfilenames> -dir <dirs>]]></c></item>
      <item><c><![CDATA[ct_run -config <configfilenames> -suite <suiteswithfullpath>]]></c>
      </item>
      <item><c><![CDATA[ct_run -userconfig <callbackmodulename> <configfilenames> -suite <suiteswithfullpath>]]></c>
      </item>
      <item><c><![CDATA[ct_run -config <configfilenames> -suite <suitewithfullpath>
	      -group <groups> -case <casenames>]]></c></item>
    </list>

Examples:

 $ ct_run -config $CFGS/sys1.cfg $CFGS/sys2.cfg -dir $SYS1_TEST $SYS2_TEST
 $ ct_run -userconfig ct_config_xml $CFGS/sys1.xml $CFGS/sys2.xml -dir $SYS1_TEST $SYS2_TEST
 $ ct_run -suite $SYS1_TEST/setup_SUITE $SYS2_TEST/config_SUITE
 $ ct_run -suite $SYS1_TEST/setup_SUITE -case start stop
 $ ct_run -suite $SYS1_TEST/setup_SUITE -group installation -case start stop

The flags <c>dir</c>, <c>suite</c>, and <c>group/case</c> can be combined.
    For example, to run <c>x_SUITE</c> and <c>y_SUITE</c>
    in directory <c>testdir</c>, as follows:

 $ ct_run -dir ./testdir -suite x_SUITE y_SUITE

This has the same effect as the following:

 $ ct_run -suite ./testdir/x_SUITE ./testdir/y_SUITE

For details, see
    <seealso marker="run_test_chapter#group_execution">Test Case Group Execution</seealso>.

The following flags can also be used with
    <seealso marker="ct_run"><c>ct_run</c></seealso>:

    <taglist>
      <tag><c><![CDATA[-help]]></c></tag>
      <item>
Lists all available start flags.
</item>

      <tag><c><![CDATA[-logdir <dir>]]></c></tag>
      <item>
Specifies where the HTML log files are to be written.
</item>

      <tag><c><![CDATA[-label <name_of_test_run>]]></c></tag>
      <item>
Associates the test run with a name that gets printed
	in the overview HTML log files.
</item>

      <tag><c>-refresh_logs</c></tag>
      <item>
Refreshes the top-level HTML index files.
</item>

      <tag><c>-vts</c></tag>
      <item>
Starts web-based GUI (described later).
</item>

      <tag><c>-shell</c></tag>
      <item>
Starts interactive shell mode (described later).
</item>

      <tag><c>-step [step_opts]</c></tag>
      <item>
Steps through test cases using the Erlang Debugger (described later).
</item>

      <tag><c><![CDATA[-spec <testspecs>]]></c></tag>
      <item>
Uses test specification as input (described later).
</item>

      <tag><c>-allow_user_terms</c></tag>
      <item>
Allows user-specific terms in a test specification (described later).
</item>

      <tag><c>-silent_connections [conn_types]</c></tag>
      <item>
, tells <c>Common Test</c> to suppress printouts for
        specified connections (described later).
</item>

      <tag><c><![CDATA[-stylesheet <css_file>]]></c></tag>
      <item>
Points out a user HTML style sheet (described later).
</item>

      <tag><c><![CDATA[-cover <cover_cfg_file>]]></c></tag>
      <item>
To perform code coverage test (see
	<seealso marker="cover_chapter#cover">Code Coverage Analysis</seealso>).
</item>

      <tag><c><![CDATA[-cover_stop <bool>]]></c></tag>
      <item>
To specify if the <c>cover</c> tool is to be stopped
      after the test is completed (see
	<seealso marker="cover_chapter#cover_stop">Code Coverage Analysis</seealso>).
</item>

      <tag><c><![CDATA[-event_handler <event_handlers>]]></c></tag>
      <item>
To install
        <seealso marker="event_handler_chapter#event_handling">event handlers</seealso>.
</item>

      <tag><c><![CDATA[-event_handler_init <event_handlers>]]></c></tag>
      <item>
To install
        <seealso marker="event_handler_chapter#event_handling">event handlers</seealso>
      including start arguments.
</item>

      <tag><c><![CDATA[-ct_hooks <ct_hooks>]]></c></tag>
      <item>
To install
        <seealso marker="ct_hooks_chapter#installing">Common Test Hooks</seealso>
      including start arguments.
</item>

      <tag><c><![CDATA[-enable_builtin_hooks <bool>]]></c></tag>
      <item>
To enable or disable
        <seealso marker="ct_hooks_chapter#builtin_cths">Built-in Common Test Hooks</seealso>.
      Default is <c>true</c>.
</item>

      <tag><c><![CDATA[-include]]></c></tag>
      <item>
Specifies include directories (described earlier).
</item>

      <tag><c><![CDATA[-no_auto_compile]]></c></tag>
      <item>
Disables the automatic test suite compilation feature (described earlier).
</item>

      <tag><c><![CDATA[-abort_if_missing_suites]]></c></tag>
      <item>
Aborts the test run if one or more suites fail to compile (described earlier).
</item>

      <tag><c><![CDATA[-multiply_timetraps <n>]]></c></tag>
      <item>
Extends <seealso marker="write_test_chapter#timetraps">timetrap
	  time-out</seealso> values.
</item>

      <tag><c><![CDATA[-scale_timetraps <bool>]]></c></tag>
      <item>
Enables automatic <seealso marker="write_test_chapter#timetraps">timetrap
	  time-out</seealso> scaling.
</item>

      <tag><c><![CDATA[-repeat <n>]]></c></tag>
      <item>
Tells <c>Common Test</c> to repeat the tests <c>n</c> times (described later).
</item>

      <tag><c><![CDATA[-duration <time>]]></c></tag>
      <item>
Tells <c>Common Test</c> to repeat the tests for duration of time (described later).
</item>

      <tag><c><![CDATA[-until <stop_time>]]></c></tag>
      <item>
Tells <c>Common Test</c> to repeat the tests until <c>stop_time</c> (described later).
</item>

      <tag><c>-force_stop [skip_rest]</c></tag>
      <item>
On time-out, the test run is aborted when the current test job is finished. If <c>skip_rest</c>
      is provided, the remaining test cases in the current test job are skipped (described later).
</item>

      <tag><c><![CDATA[-decrypt_key <key>]]></c></tag>
      <item>
Provides a decryption key for
      <seealso marker="config_file_chapter#encrypted_config_files">encrypted configuration files</seealso>.
</item>

      <tag><c><![CDATA[-decrypt_file <key_file>]]></c></tag>
      <item>
Points out a file containing a decryption key for
        <seealso marker="config_file_chapter#encrypted_config_files">encrypted configuration files</seealso>.
</item>

      <tag><c><![CDATA[-basic_html]]></c></tag>
      <item>
Switches off HTML enhancements that can be incompatible with older browsers.
</item>

      <tag><c><![CDATA[-logopts <opts>]]></c></tag>
      <item>
Enables modification of the logging behavior, see
      <seealso marker="run_test_chapter#logopts">Log options</seealso>.
</item>

      <tag><c><![CDATA[-verbosity <levels>]]></c></tag>
      <item>
Sets <seealso marker="write_test_chapter#logging">verbosity levels
      for printouts</seealso>.
</item>

      <tag><c><![CDATA[-no_esc_chars]]></c></tag>
      <item>
Disables automatic escaping of special HTML characters.
      See the <seealso marker="write_test_chapter#logging">Logging chapter</seealso>.
</item>
    </taglist>

    <note>
Directories passed to <c>Common Test</c> can have either relative or absolute paths.
</note>

    <note>
Any start flags to the Erlang runtime system (application ERTS) can also be passed as
             parameters to <c>ct_run</c>. It is, for example, useful to be able to
	     pass directories to be added to the Erlang code server search path
	     with flag <c>-pa</c> or <c>-pz</c>. If you have common help- or library
	     modules for test suites (separately compiled), stored in other directories
	     than the test suite directories, these <c>help/lib</c> directories are preferably
	     added to the code path this way.

Example:

<c>$ ct_run -dir ./chat_server -logdir ./chat_server/testlogs -pa $PWD/chat_server/ebin</c>

The absolute path of directory <c>chat_server/ebin</c>
	     is here passed to the code server. This is essential because relative
	     paths are stored by the code server as relative, and <c>Common Test</c> changes
	     the current working directory of ERTS during the test run.

    </note>

The <c>ct_run</c> program sets the exit status before shutting down. The following values
      are defined:

    <list type="bulleted">
      <item><c>0</c> indicates a successful testrun, that is, without failed or auto-skipped test cases.</item>
      <item><c>1</c> indicates that one or more test cases have failed, or have been auto-skipped.</item>
      <item><c>2</c> indicates that the test execution has failed because of, for example, compilation errors, or an
	illegal return value from an information function.</item>
    </list>

If auto-skipped test cases do not affect the exit status. The default
      behavior can be changed using start flag:

 -exit_status ignore_config

    <note>
Executing <c>ct_run</c> without start flags is equal to the command:
    <c>ct_run -dir ./</c>
</note>

For more information about the <c>ct_run</c> program, see module
      <seealso marker="ct_run"><c>ct_run</c></seealso> and section
      <seealso marker="install_chapter#general">Installation</seealso>.

    <marker id="erlang_shell_or_program"></marker>
    <title>Running Tests from the Erlang Shell or from an Erlang Program</title>

<c>Common Test</c> provides an Erlang API for running tests. The main
      (and most flexible) function for specifying and executing tests is
      <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>.
      It takes the same start parameters as
      <seealso marker="run_test_chapter#ct_run"><c>ct_run</c></seealso>,
      but the flags are instead specified as options in a list of key-value tuples.
      For example, a test specified with <c>ct_run</c> as follows:

<c>$ ct_run -suite ./my_SUITE -logdir ./results</c>

is with <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso> specified as:

<c>1> ct:run_test([{suite,"./my_SUITE"},{logdir,"./results"}]).</c>

The function returns the test result, represented by the tuple
	<c>{Ok,Failed,{UserSkipped,AutoSkipped}}</c>, where each element is an
	integer. If test execution fails, the function returns the tuple
	<c>{error,Reason}</c>, where the term <c>Reason</c> explains the
	failure.

The default start option <c>{dir,Cwd}</c> (to run all suites in the current
      working directory) is used if the function is called with an empty
      list of options.

	  <title>Releasing the Erlang Shell</title>

During execution of tests started with
	  <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>,
	  the Erlang shell process, controlling <c>stdin</c>, remains the top-level
	  process of the <c>Common Test</c> system of processes. Consequently,
	  the Erlang shell is not available for interaction during
	  the test run. If this is not desirable, for example, because the shell
	  is needed for debugging purposes or for interaction with the SUT during test
	  execution, set start option <c>release_shell</c> to
	  <c>true</c> (in the call to <c>ct:run_test/1</c> or by
	  using the corresponding test specification term, described later). This
	  makes <c>Common Test</c> release the shell immediately after the test suite
	  compilation stage. To accomplish this, a test runner process
	  is spawned to take control of the test execution. The effect is that
	  <c>ct:run_test/1</c> returns the pid of this process rather than the
	  test result, which instead is printed to tty at the end of the test run.

	  <note>
To use the functions
	  <seealso marker="ct#break-1"><c>ct:break/1,2</c></seealso> and
	  <seealso marker="ct#continue-0"><c>ct:continue/0,1</c></seealso>,
	  <c>release_shell</c> must be set to <c>true</c>.
</note>

For details, see
        <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso> manual page.

    <marker id="group_execution"></marker>
    <title>Test Case Group Execution</title>

With the <c>ct_run</c> flag, or <c>ct:run_test/1</c> option <c>group</c>,
    one or more test case groups can be specified, optionally in combination
    with specific test cases. The syntax for specifying groups on the command line
    is as follows:

 <![CDATA[$ ct_run -group <group_names_or_paths> [-case <cases>]]]>

The syntax in the Erlang shell is as follows:

 <![CDATA[1> ct:run_test([{group,GroupsNamesOrPaths}, {case,Cases}]).]]>

Parameter <c>group_names_or_paths</c> specifies one
    or more group names and/or one or more group paths. At startup,
    <c>Common Test</c> searches for matching groups in the group definitions
    tree (that is, the list returned from <c>Suite:groups/0</c>; for details, see section
    <seealso marker="write_test_chapter#test_case_groups">Test Case Groups</seealso>.

Given a group name, say <c>g</c>, <c>Common Test</c> searches for all paths
    leading to <c>g</c>. By path is meant a sequence of nested groups,
    which must be followed to get from the top-level
    group to <c>g</c>. To execute the test cases in group <c>g</c>,
    <c>Common Test</c> must call the <c>init_per_group/2</c> function for
    each group in the path to <c>g</c>, and all corresponding <c>end_per_group/2</c>
    functions afterwards. This is because the configuration
    of a test case in <c>g</c> (and its <c>Config</c> input data) depends on
    <c>init_per_testcase(TestCase, Config)</c> and its return value, which
    in turn depends on <c>init_per_group(g, Config)</c> and its return value,
    which in turn depends on <c>init_per_group/2</c> of the group above
    <c>g</c>, and so on, all the way up to the top-level group.

This means that if there is more than one way to locate a group
    (and its test cases) in a path, the result of the group search operation
    is a number of tests, all of which are to be performed.
    <c>Common Test</c> interprets a group specification that consists of a
    single name as follows:

"Search and find all paths in the group definitions tree that lead
    to the specified group and, for each path, create a test that does the following,
    in order:

    <list type="ordered">
      <item>Executes all configuration functions in the path to the specified group.</item>
      <item>Executes all, or all matching, test cases in this group.</item>
      <item>Executes all, or all matching, test cases in all subgroups of the group."</item>
    </list>

The user can specify a specific group path with
    parameter <c>group_names_or_paths</c>. With this type of specification
    execution of unwanted groups (in otherwise matching paths),
    and/or the execution of subgroups can be avoided. The command line syntax of the
    group path is a list of group names in the path, for example:

<c>$ ct_run -suite "./x_SUITE" -group [g1,g3,g4] -case tc1 tc5</c>

The syntax in the Erlang shell is as follows (requires a list within the groups list):

<c>1> ct:run_test([{suite,"./x_SUITE"}, {group,[[g1,g3,g4]]}, {testcase,[tc1,tc5]}]).</c>

The last group in the specified path is the terminating group in
    the test, that is, no subgroups following this group are executed. In the
    previous example, <c>g4</c> is the terminating group. Hence, <c>Common Test</c>
    executes a test that calls all <c>init</c> configuration functions in the path to
    <c>g4</c>, that is, <c>g1..g3..g4</c>. It then calls test cases <c>tc1</c>
    and <c>tc5</c> in <c>g4</c>, and finally all <c>end</c> configuration functions
    in order <c>g4..g3..g1</c>.

    <note>
The group path specification does not necessarily
    have to include all groups in the path to the terminating group.
    <c>Common Test</c> searches for all matching paths if an incomplete
    group path is specified.
</note>

    <note>
Group names and group paths can be combined with parameter
    <c>group_names_or_paths</c>. Each element is treated as an individual specification
    in combination with parameter <c>cases</c>.
    The following examples illustrates this.
</note>

Examples:

 -module(x_SUITE).
 ...
 %% The group definitions:
 groups() ->
   [{top1,[],[tc11,tc12,
	      {sub11,[],[tc12,tc13]},
	      {sub12,[],[tc14,tc15,
			 {sub121,[],[tc12,tc16]}]}]},

    {top2,[],[{group,sub21},{group,sub22}]},
    {sub21,[],[tc21,{group,sub2X2}]},
    {sub22,[],[{group,sub221},tc21,tc22,{group,sub2X2}]},
    {sub221,[],[tc21,tc23]},
    {sub2X2,[],[tc21,tc24]}].

The following executes two tests, one for all cases and all subgroups
    under <c>top1</c>, and one for all under <c>top2</c>:

 $ ct_run -suite "x_SUITE" -group all
 1> ct:run_test([{suite,"x_SUITE"}, {group,all}]).

Using <c>-group top1 top2</c>, or <c>{group,[top1,top2]}</c> gives the same result.

The following executes one test for all cases and subgroups under <c>top1</c>:

 $ ct_run -suite "x_SUITE" -group top1
 1> ct:run_test([{suite,"x_SUITE"}, {group,[top1]}]).

The following runs a test executing <c>tc12</c> in <c>top1</c> and any subgroup
    under <c>top1</c> where it can be found (<c>sub11</c> and <c>sub121</c>):

 $ ct_run -suite "x_SUITE" -group top1 -case tc12
 1> ct:run_test([{suite,"x_SUITE"}, {group,[top1]}, {testcase,[tc12]}]).

The following executes <c>tc12</c> only in group <c>top1</c>:

 $ ct_run -suite "x_SUITE" -group [top1] -case tc12
 1> ct:run_test([{suite,"x_SUITE"}, {group,[[top1]]}, {testcase,[tc12]}]).

The following searches <c>top1</c> and all its subgroups for <c>tc16</c> resulting
    in that this test case executes in group <c>sub121</c>:

 $ ct_run -suite "x_SUITE" -group top1 -case tc16
 1> ct:run_test([{suite,"x_SUITE"}, {group,[top1]}, {testcase,[tc16]}]).

Using the specific path <c>-group [sub121]</c> or <c>{group,[[sub121]]}</c> gives
    the same result in this example.

The following executes two tests, one including all cases and subgroups under
    <c>sub12</c>, and one with only the test cases in <c>sub12</c>:

 $ ct_run -suite "x_SUITE" -group sub12 [sub12]
 1> ct:run_test([{suite,"x_SUITE"}, {group,[sub12,[sub12]]}]).

In the following example, <c>Common Test</c> finds and executes two tests,
    one for the path from <c>top2</c> to <c>sub2X2</c> through <c>sub21</c>,
    and one from <c>top2</c> to <c>sub2X2</c> through <c>sub22</c>:

 $ ct_run -suite "x_SUITE" -group sub2X2
 1> ct:run_test([{suite,"x_SUITE"}, {group,[sub2X2]}]).

In the following example, by specifying the unique path <c>top2 -> sub21 -> sub2X2</c>,
    only one test is executed. The second possible path, from <c>top2</c> to <c>sub2X2</c>
    (from the former example) is discarded:

 $ ct_run -suite "x_SUITE" -group [sub21,sub2X2]
 1> ct:run_test([{suite,"x_SUITE"}, {group,[[sub21,sub2X2]]}]).

The following executes only the test cases for <c>sub22</c> and in reverse order
    compared to the group definition:

 $ ct_run -suite "x_SUITE" -group [sub22] -case tc22 tc21
 1> ct:run_test([{suite,"x_SUITE"}, {group,[[sub22]]}, {testcase,[tc22,tc21]}]).

If a test case belonging to a group (according to the group definition) is executed
    without a group specification, that is, simply by
    (using the command line):

<c>$ ct_run -suite "my_SUITE" -case my_tc</c>

or (using the Erlang shell):

<c>1> ct:run_test([{suite,"my_SUITE"}, {testcase,my_tc}]).</c>

then <c>Common Test</c> ignores the group definition and executes the test case
    in the scope of the test suite only (no group configuration functions are called).

The group specification feature, as presented in this section, can also
    be used in <seealso marker="run_test_chapter#test_specifications">Test
    Specifications</seealso> (with some extra features added).

    <title>Running the Interactive Shell Mode</title>

You can start <c>Common Test</c> in an interactive shell mode where no
      automatic testing is performed. Instead, <c>Common Test</c>
      starts its utility processes, installs configuration data (if any),
      and waits for the user to call functions (typically test case support
      functions) from the Erlang shell.

The shell mode is useful, for example, for debugging test suites, analyzing
      and debugging the SUT during "simulated" test case execution, and
      trying out various operations during test suite development.

To start the interactive shell mode, start an Erlang shell
      manually and call <seealso marker="ct#install-1"><c>ct:install/1</c></seealso>
      to install any configuration data you might need (use <c>[]</c> as argument otherwise).
      Then call <seealso marker="ct#start_interactive-0"><c>ct:start_interactive/0</c></seealso>
      to start <c>Common Test</c>.

If you use the <c>ct_run</c> program, you can start
      the Erlang shell and <c>Common Test</c> in one go by using the flag <c>-shell</c> and,
      optionally, flag <c>-config</c> and/or <c>-userconfig</c>.

Examples:

    <list type="bulleted">
      <item><c>ct_run -shell</c></item>
      <item><c><![CDATA[ct_run -shell -config cfg/db.cfg]]></c></item>
      <item><c><![CDATA[ct_run -shell -userconfig db_login testuser x523qZ]]></c></item>
    </list>

If no configuration file is specified with command <c>ct_run</c>,
      a warning is displayed. If <c>Common Test</c> has been run from the same
      directory earlier, the same configuration file(s) are used again. If <c>Common Test</c>
      has not been run from this directory before, no configuration files are available.

If any functions using "required configuration data" (for example, functions
      <c>ct_telnet</c> or <c>ct_ftp</c>) are to be called from the Erlang shell, first require
      configuration data with <seealso marker="ct#require-1"><c>
      ct:require/1,2</c></seealso>. This is equivalent to a <c>require</c> statement
      in the <seealso marker="write_test_chapter#suite">Test Suite Information Function</seealso>
      or in the <seealso marker="write_test_chapter#info_function">Test Case Information Function</seealso>.

Example:

 1> ct:require(unix_telnet, unix).
 ok
 2> ct_telnet:open(unix_telnet).
 {ok,<0.105.0>}
 4> ct_telnet:cmd(unix_telnet, "ls .").
 {ok,["ls .","file1  ...",...]}

Everything that <c>Common Test</c> normally prints in the test case logs,
      are in the interactive mode written to a log named <c>ctlog.html</c>
      in directory  <c><![CDATA[ct_run.<timestamp>]]></c>. A link to this
      file is available in the file named <c>last_interactive.html</c> in the
      directory from which you execute <c>ct_run</c>. Specifying a different
      root directory for the logs than the current working directory
      is not supported.

If you wish to exit the interactive mode (for example, to start an automated
      test run with <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>),
      call function
      <seealso marker="ct#stop_interactive-0"><c>ct:stop_interactive/0</c></seealso>.
      This shuts down the running <c>ct</c> application. Associations between
      configuration names and data created with <c>require</c> are
      consequently deleted. Function
      <seealso marker="ct#start_interactive-0"><c>ct:start_interactive/0</c></seealso>
      takes you back into interactive mode, but the previous state is not restored.

    <title>Step-by-Step Execution of Test Cases with the Erlang Debugger</title>

Using <c>ct_run -step [opts]</c>, or by passing option <c>{step,Opts}</c>
       to <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>,
       the following is possible:

       <list type="bulleted">
       <item>Get the Erlang Debugger started automatically.</item>
       <item>Use its graphical interface to investigate the state of the current test case.</item>
       <item>Execute the test case step-by-step and/or set execution breakpoints.</item>
     </list>

If no extra options are specified with flag/option <c>step</c>,
       breakpoints are set automatically on the test cases that
       are to be executed by <c>Common Test</c>, and those functions only. If
       step option <c>config</c> is specified, breakpoints are also initially
       set on the configuration functions in the suite, that is,
       <c>init_per_suite/1</c>, <c>end_per_suite/1</c>,
       <c>init_per_group/2</c>, <c>end_per_group/2</c>,
       <c>init_per_testcase/2</c> and <c>end_per_testcase/2</c>.

<c>Common Test</c> enables the Debugger auto-attach feature, which means
       that for every new interpreted test case function that starts to execute,
       a new trace window automatically pops up (as each test
       case executes on a dedicated Erlang process). Whenever a new test case starts,
       <c>Common Test</c> attempts to close the inactive trace window of the previous
       test case. However, if you prefer <c>Common Test</c> to leave inactive trace
       windows, use option <c>keep_inactive</c>.

The step functionality can be used together with flag/option <c>suite</c> and
       <c>suite</c> + <c>case/testcase</c>, but not together with <c>dir</c>.

  <marker id="test_specifications"></marker>
    <title>Test Specifications</title>

	<title>General Description</title>

The most flexible way to specify what to test, is to use a
	test specification, which is a sequence of
	Erlang terms. The terms are normally declared in one or more text files
	(see <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>), but
	can also be passed to <c>Common Test</c> on the form of a list (see
	<seealso marker="ct#run_testspec-1"><c>ct:run_testspec/1</c></seealso>).
	There are two general types of terms: configuration terms and test
	specification terms.

With configuration terms it is, for example, possible to do the following:

	<list type="bulleted">
       <item>Label the test run (similar to <c>ct_run -label</c>).</item>
       <item>Evaluate any expressions before starting the test.</item>
       <item>Import configuration data (similar to <c>ct_run -config/-userconfig</c>).</item>
       <item>Specify the top-level HTML log directory (similar to <c>ct_run -logdir</c>).</item>
       <item>Enable code coverage analysis (similar to <c>ct_run -cover</c>).</item>
       <item>Install <c>Common Test Hooks</c> (similar to <c>ct_run -ch_hooks</c>).</item>
       <item>Install <c>event_handler</c> plugins (similar to <c>ct_run -event_handler</c>).</item>
       <item>Specify include directories to be passed to the compiler for
       automatic compilation (similar to <c>ct_run -include</c>).</item>
       <item>Disable the auto-compilation feature (similar to <c>ct_run -no_auto_compile</c>).</item>
       <item>Set verbosity levels (similar to <c>ct_run -verbosity</c>).</item>
     </list>

Configuration terms can be combined with <c>ct_run</c> start flags
	or <c>ct:run_test/1</c> options. The result is, for some flags/options
	and terms, that the values are merged (for example, configuration files,
	include directories, verbosity levels, and silent connections) and for
	others that the start flags/options override the test specification
	terms (for example, log directory, label, style sheet, and auto-compilation).

With test specification terms, it is possible to state exactly
	which tests to run and in which order. A test term specifies
	either one or more suites, one or more test case groups (possibly nested),
	or one or more test cases in a group (or in multiple groups) or in a suite.

Any number of test terms can be declared in sequence.
	<c>Common Test</c> compiles by default the terms into one or more tests
	to be performed in one resulting test run. A term that
	specifies a set of test cases "swallows" one that only
	specifies a subset of these cases. For example, the result of merging
	one term specifying that all cases in suite S are to be
	executed, with another term specifying only test case X and Y in
	S, is a test of all cases in S. However, if a term specifying
	test case X and Y in S is merged with a term specifying case Z
	in S, the result is a test of X, Y, and Z in S. To disable this
	behavior, that is, to instead perform each test sequentially in a
	"script-like" manner, set term <c>merge_tests</c> to <c>false</c>
	in the test specification.

A test term can also specify one or more test suites, groups,
	or test cases to be skipped. Skipped suites, groups, and cases
	are not executed and show up in the HTML log files as <c>SKIPPED</c>.

        <title>Using Multiple Test Specification Files</title>

When multiple test specification files are specified at startup (either
	with <c>ct_run -spec file1 file2 ...</c> or
	<c>ct:run_test([{spec, [File1,File2,...]}])</c>),
	<c>Common Test</c> either executes one test run per specification file,
	or joins the files and performs all tests within one single test run.
	The first behavior is the default one. The latter requires that start
	flag/option <c>join_specs</c> is provided, for example,
	<c>run_test -spec ./my_tests1.ts ./my_tests2.ts -join_specs</c>.

Joining a number of specifications, or running them separately, can
	also be accomplished with (and can be combined with) test specification
	file inclusion.

      <title>Test Specification File Inclusion</title>

With the term <c>specs</c>, a test specification can include
	other specifications. An included specification can either be joined
	with the source specification or used to produce a separate test run
	(as with start flag/option <c>join_specs</c> above).

Example:

 %% In specification file "a.spec"
 {specs, join, ["b.spec", "c.spec"]}.
 {specs, separate, ["d.spec", "e.spec"]}.
 %% Config and test terms follow
 ...

In this example, the test terms defined in files "b.spec" and "c.spec"
	are joined with the terms in source specification "a.spec"
	(if any). The inclusion of specifications "d.spec" and
	"e.spec" results in two separate, and independent, test runs
	(one for each included specification).

Option <c>join</c> does not imply that the test terms
	are merged, only that all tests are executed in one single test run.

Joined specifications share common configuration settings, such as
	the list of <c>config</c> files or <c>include</c> directories.
	For configurations that cannot be combined, such as settings for <c>logdir</c>
	or <c>verbosity</c>, it is up to the user to ensure there are no clashes
	when the test specifications are joined. Specifications included with
	option <c>separate</c> do not share configuration settings with the
	source specification. This is useful, for example, if there are clashing
	configuration settings in included specifications, making it them impossible
	to join.

If <c>{merge_tests,true}</c> is set in the source specification
	(which is the default setting), terms in joined specifications are
	merged with terms in the source specification (according to the
	description of <c>merge_tests</c> earlier).

Notice that it is always the <c>merge_tests</c> setting in the source
	specification that is used when joined with other specifications.
	Say, for example, that a source specification A, with tests TA1 and TA2, has
	<c>{merge_tests,false}</c> set, and that it includes another specification,
	B, with tests TB1 and TB2, that has <c>{merge_tests,true}</c> set.
	The result is that the test series <c>TA1,TA2,merge(TB1,TB2)</c>
	is executed. The opposite <c>merge_tests</c> settings would result in
	the test series <c>merge(merge(TA1,TA2),TB1,TB2)</c>.

The term <c>specs</c> can be used to nest specifications,
	that is, have one specification include other specifications, which in turn
	include others, and so no

	<title>Test Case Groups</title>

When a test case group is specified, the resulting test
	executes function <c>init_per_group</c>, followed by all test
	cases and subgroups (including their configuration functions), and
	finally function <c>end_per_group</c>. Also, if particular
	test cases in a group are specified, <c>init_per_group</c>
	and <c>end_per_group</c>, for the group in question, are
	called. If a group defined (in <c>Suite:group/0</c>) as
	a subgroup of another group, is specified (or if particular test
	cases of a subgroup are), <c>Common Test</c> calls the configuration
	functions for the top-level groups and for the subgroup
	in question (making it possible to pass configuration data all
	the way from <c>init_per_suite</c> down to the test cases in the
	subgroup).

The test specification uses the same mechanism for specifying
	test case groups through names and paths, as explained in section
	<seealso marker="run_test_chapter#group_execution">Test Case Group Execution</seealso>,
	with the addition of element <c>GroupSpec</c>.

Element <c>GroupSpec</c> makes it possible to specify
	group execution properties that overrides those in the
	group definition (that is, in <c>groups/0</c>). Execution properties for
	subgroups might be overridden as well. This feature makes it possible to
	change properties of groups at the time of execution,
	without having to edit the test suite. The same feature is available for
	<c>group</c> elements in the <c>Suite:all/0</c> list. For details and examples,
	see section <seealso marker="write_test_chapter#test_case_groups">
	Test Case Groups</seealso>.

	<title>Test Specification Syntax</title>

Test specifications can be used to run tests both in a single
	test host environment and in a distributed <c>Common Test</c> environment
	(Large Scale Testing). The node parameters in term <c>init</c> are only
	relevant in the latter (see section
	<seealso marker="ct_master_chapter#test_specifications">Test Specifications</seealso>
	in Large Scale Testing). For details about the various terms, see the
	corresponding sections in the User's Guide, for example, the following:

	<list type="bulleted">
       <item>The <seealso marker="run_test_chapter#ct_run"><c>ct_run</c>
	program</seealso> for an overview of available start flags
	(as most flags have a corresponding configuration term)</item>
       <item><seealso marker="write_test_chapter#logging">Logging</seealso>
	(for terms <c>verbosity</c>, <c>stylesheet</c>, <c>basic_html</c> and <c>esc_chars</c>)</item>
       <item><seealso marker="config_file_chapter#top">External Configuration Data</seealso>
	(for terms <c>config</c> and <c>userconfig</c>)</item>
       <item><seealso marker="event_handler_chapter#event_handling">Event
	Handling</seealso> (for the <c>event_handler</c> term)</item>
       <item><seealso marker="ct_hooks_chapter#installing">Common Test Hooks</seealso>
	(for term <c>ct_hooks</c>)</item>
	</list>

Configuration terms:

 {merge_tests, Bool}.

 {define, Constant, Value}.

 {specs, InclSpecsOption, TestSpecs}.

 {node, NodeAlias, Node}.

 {init, InitOptions}.
 {init, [NodeAlias], InitOptions}.

 {label, Label}.
 {label, NodeRefs, Label}.

 {verbosity, VerbosityLevels}.
 {verbosity, NodeRefs, VerbosityLevels}.

 {stylesheet, CSSFile}.
 {stylesheet, NodeRefs, CSSFile}.

 {silent_connections, ConnTypes}.
 {silent_connections, NodeRefs, ConnTypes}.

 {multiply_timetraps, N}.
 {multiply_timetraps, NodeRefs, N}.

 {scale_timetraps, Bool}.
 {scale_timetraps, NodeRefs, Bool}.

 {cover, CoverSpecFile}.
 {cover, NodeRefs, CoverSpecFile}.

 {cover_stop, Bool}.
 {cover_stop, NodeRefs, Bool}.

 {include, IncludeDirs}.
 {include, NodeRefs, IncludeDirs}.

 {auto_compile, Bool},
 {auto_compile, NodeRefs, Bool},

 {abort_if_missing_suites, Bool},
 {abort_if_missing_suites, NodeRefs, Bool},

 {config, ConfigFiles}.
 {config, ConfigDir, ConfigBaseNames}.
 {config, NodeRefs, ConfigFiles}.
 {config, NodeRefs, ConfigDir, ConfigBaseNames}.

 {userconfig, {CallbackModule, ConfigStrings}}.
 {userconfig, NodeRefs, {CallbackModule, ConfigStrings}}.

 {logdir, LogDir}.
 {logdir, NodeRefs, LogDir}.

 {logopts, LogOpts}.
 {logopts, NodeRefs, LogOpts}.

 {create_priv_dir, PrivDirOption}.
 {create_priv_dir, NodeRefs, PrivDirOption}.

 {event_handler, EventHandlers}.
 {event_handler, NodeRefs, EventHandlers}.
 {event_handler, EventHandlers, InitArgs}.
 {event_handler, NodeRefs, EventHandlers, InitArgs}.

 {ct_hooks, CTHModules}.
 {ct_hooks, NodeRefs, CTHModules}.

 {enable_builtin_hooks, Bool}.

 {basic_html, Bool}.
 {basic_html, NodeRefs, Bool}.

 {esc_chars, Bool}.
 {esc_chars, NodeRefs, Bool}.

 {release_shell, Bool}.

Test terms:

 {suites, Dir, Suites}.
 {suites, NodeRefs, Dir, Suites}.

 {groups, Dir, Suite, Groups}.
 {groups, NodeRefs, Dir, Suite, Groups}.

 {groups, Dir, Suite, Groups, {cases,Cases}}.
 {groups, NodeRefs, Dir, Suite, Groups, {cases,Cases}}.

 {cases, Dir, Suite, Cases}.
 {cases, NodeRefs, Dir, Suite, Cases}.

 {skip_suites, Dir, Suites, Comment}.
 {skip_suites, NodeRefs, Dir, Suites, Comment}.

 {skip_groups, Dir, Suite, GroupNames, Comment}.
 {skip_groups, NodeRefs, Dir, Suite, GroupNames, Comment}.

 {skip_cases, Dir, Suite, Cases, Comment}.
 {skip_cases, NodeRefs, Dir, Suite, Cases, Comment}.

	<marker id="types"></marker>

Types:

 Bool            = true | false
 Constant        = atom()
 Value           = term()
 InclSpecsOption = join | separate
 TestSpecs       = string() | [string()]
 NodeAlias       = atom()
 Node            = node()
 NodeRef         = NodeAlias | Node | master
 NodeRefs        = all_nodes | [NodeRef] | NodeRef
 InitOptions     = term()
 Label           = atom() | string()
 VerbosityLevels = integer() | [{Category,integer()}]
 Category        = atom()
 CSSFile         = string()
 ConnTypes       = all | [atom()]
 N               = integer()
 CoverSpecFile   = string()
 IncludeDirs     = string() | [string()]
 ConfigFiles     = string() | [string()]
 ConfigDir       = string()
 ConfigBaseNames = string() | [string()]
 CallbackModule  = atom()
 ConfigStrings   = string() | [string()]
 LogDir          = string()
 LogOpts         = [term()]
 PrivDirOption   = auto_per_run | auto_per_tc | manual_per_tc
 EventHandlers   = atom() | [atom()]
 InitArgs        = [term()]
 CTHModules      = [CTHModule |
		    {CTHModule, CTHInitArgs} |
		    {CTHModule, CTHInitArgs, CTHPriority}]
 CTHModule       = atom()
 CTHInitArgs     = term()
 Dir             = string()
 Suites          = atom() | [atom()] | all
 Suite           = atom()
 Groups          = GroupPath | [GroupPath] | GroupSpec | [GroupSpec] | all
 GroupPath       = [GroupName]
 GroupSpec       = GroupName | {GroupName,Properties} | {GroupName,Properties,GroupSpec}
 GroupName       = atom()
 GroupNames      = GroupName | [GroupName]
 Cases           = atom() | [atom()] | all
 Comment         = string() | ""

The difference between the <c>config</c> terms above is that with
	<c>ConfigDir</c>, <c>ConfigBaseNames</c> is a list of base names,
	that is, without directory paths. <c>ConfigFiles</c> must be full names,
	including paths. For example, the following two terms have the same meaning:

 {config, ["/home/testuser/tests/config/nodeA.cfg",
           "/home/testuser/tests/config/nodeB.cfg"]}.

 {config, "/home/testuser/tests/config", ["nodeA.cfg","nodeB.cfg"]}.

	  <note>
Any relative paths, specified in the test specification, are
	  relative to the directory containing the test specification file if
	  <c>ct_run -spec TestSpecFile ...</c> or
	  <c>ct:run:test([{spec,TestSpecFile},...])</c>
	  executes the test.

The path is relative to the top-level log directory if
	  <c>ct:run:testspec(TestSpec)</c> executes the test.
</note>

	  <title>Constants</title>

The term <c>define</c> introduces a constant that is used to
	  replace the name <c>Constant</c> with <c>Value</c>, wherever it is found in
	  the test specification. This replacement occurs during an initial iteration
	  through the test specification. Constants can be used anywhere in the test
	  specification, for example, in any lists and tuples, and even in strings
	  and inside the value part of other constant definitions. A constant can
	  also be part of a node name, but that is the only place where a constant
	  can be part of an atom.

	  <note>
For the sake of readability, the name of the constant must always
	  begin with an uppercase letter, or a <c>$</c>, <c>?</c>, or <c>_</c>.
	  This means that it must always be single quoted (as the constant name is
	  an atom, not text).
</note>

The main benefit of constants is that they can be used to reduce the size
	  (and avoid repetition) of long strings, such as file paths.

Examples:

 %% 1a. no constant
 {config, "/home/testuser/tests/config", ["nodeA.cfg","nodeB.cfg"]}.
 {suites, "/home/testuser/tests/suites", all}.

 %% 1b. with constant
 {define, 'TESTDIR', "/home/testuser/tests"}.
 {config, "'TESTDIR'/config", ["nodeA.cfg","nodeB.cfg"]}.
 {suites, "'TESTDIR'/suites", all}.

 %% 2a. no constants
 {config, [testnode@host1, testnode@host2], "../config", ["nodeA.cfg","nodeB.cfg"]}.
 {suites, [testnode@host1, testnode@host2], "../suites", [x_SUITE, y_SUITE]}.

 %% 2b. with constants
 {define, 'NODE', testnode}.
 {define, 'NODES', ['NODE'@host1, 'NODE'@host2]}.
 {config, 'NODES', "../config", ["nodeA.cfg","nodeB.cfg"]}.
 {suites, 'NODES', "../suites", [x_SUITE, y_SUITE]}.

Constants make the test specification term <c>alias</c>, in previous
	    versions of <c>Common Test</c>, redundant. This term is deprecated but
	    remains supported in upcoming <c>Common Test</c> releases. Replacing <c>alias</c>
	    terms with <c>define</c> is strongly recommended though. An example
	    of such replacement follows:

 %% using the old alias term
 {config, "/home/testuser/tests/config/nodeA.cfg"}.
 {alias, suite_dir, "/home/testuser/tests/suites"}.
 {groups, suite_dir, x_SUITE, group1}.

 %% replacing with constants
 {define, 'TestDir', "/home/testuser/tests"}.
 {define, 'CfgDir', "'TestDir'/config"}.
 {define, 'SuiteDir', "'TestDir'/suites"}.
 {config, 'CfgDir', "nodeA.cfg"}.
 {groups, 'SuiteDir', x_SUITE, group1}.

Constants can well replace term <c>node</c> also, but
	      this still has a declarative value, mainly when used in combination
	      with <c>NodeRefs == all_nodes</c>
	      (see <seealso marker="#types">Types</seealso>).

	  <title>Example</title>

Here follows a simple test specification example:

 {define, 'Top', "/home/test"}.
 {define, 'T1', "'Top'/t1"}.
 {define, 'T2', "'Top'/t2"}.
 {define, 'T3', "'Top'/t3"}.
 {define, 'CfgFile', "config.cfg"}.

 {logdir, "'Top'/logs"}.

 {config, ["'T1'/'CfgFile'", "'T2'/'CfgFile'", "'T3'/'CfgFile'"]}.

 {suites, 'T1', all}.
 {skip_suites, 'T1', [t1B_SUITE,t1D_SUITE], "Not implemented"}.
 {skip_cases, 'T1', t1A_SUITE, [test3,test4], "Irrelevant"}.
 {skip_cases, 'T1', t1C_SUITE, [test1], "Ignore"}.

 {suites, 'T2', [t2B_SUITE,t2C_SUITE]}.
 {cases, 'T2', t2A_SUITE, [test4,test1,test7]}.

 {skip_suites, 'T3', all, "Not implemented"}.

The example specifies the following:

	  <list type="bulleted">
	    <item>The specified <c>logdir</c> directory is used for storing
	    the HTML log files (in subdirectories tagged with node name,
	    date, and time).</item>
	    <item>The variables in the specified test system configuration files are
	    imported for the test.</item>
	    <item>The first test to run includes all suites for system <c>t1</c>.
	    Suites <c>t1B</c> and <c>t1D</c> are excluded from the test. Test cases
	    <c>test3</c> and <c>test4</c> in <c>t1A</c> and <c>test1</c> case in <c>t1C</c>
	    are also excluded from the test.</item>
	    <item>The second test to run is for system <c>t2</c>. The included suites are
	    <c>t2B</c> and <c>t2C</c>. Test cases <c>test4</c>, <c>test1</c>, and <c>test7</c> in suite
	    <c>t2A</c> are also included. The test cases are executed in the specified order.</item>
	    <item>The last test to run is for system <c>t3</c>. Here, all suites are skipped and this
	    is explicitly noted in the log files.</item>
	  </list>

	  <title>The init Term</title>

With term <c>init</c> it is possible to specify initialization options
	  for nodes defined in the test specification. There are options
	  to start the node and to evaluate any function on the node.
	  For details, see section <seealso marker="ct_master_chapter#ct_slave">Automatic Startup of
	  Test Target Nodes</seealso> in section Using Common Test for Large Scale Testing.

	  <title>User-Specific Terms</title>

The user can provide a test specification including (for <c>Common Test</c>)
	  unrecognizable terms. If this is desired, use flag <c>-allow_user_terms</c>
	  when starting tests with <c>ct_run</c>. This forces <c>Common Test</c> to ignore
	  unrecognizable terms. In this mode, <c>Common Test</c> is not able to check the
	  specification for errors as efficiently as if the scanner runs in default mode.
	  If <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso> is used
	  for starting the tests, the relaxed scanner mode is enabled by tuple
	  <c>{allow_user_terms,true}</c>.

	  <title>Reading Test Specification Terms</title>

Terms in the current test specification
	  (that is, the specification that has been used to configure and run the current test)
	  can be looked up.
	  The function <seealso marker="ct#get_testspec_terms-0"><c>get_testspec_terms()</c></seealso>
	  returns a list of all test specification terms (both configuration terms and test terms),
	  and <c>get_testspec_terms(Tags)</c> returns the term (or a list of terms) matching the
	  tag (or tags) in <c>Tags</c>.

For example, in the test specification:

 ...
 {label, my_server_smoke_test}.
 {config, "../../my_server_setup.cfg"}.
 {config, "../../my_server_interface.cfg"}.
 ...

And in, for example, a test suite or a <c>Common Test Hook</c> function:

 ...
 [{label,[{_Node,TestType}]}, {config,CfgFiles}] =
     ct:get_testspec_terms([label,config]),

 [verify_my_server_cfg(TestType, CfgFile) || {Node,CfgFile} <- CfgFiles,
					     Node == node()];
 ...

    <title>Running Tests from the Web-Based GUI</title>

The web-based GUI, Virtual Test Server (VTS), is started with the
      <seealso marker="run_test_chapter#ct_run"><c>ct_run</c></seealso>
      program. From the GUI, you can load configuration files and select
      directories, suites, and cases to run. You can also state the
      configuration files, directories, suites, and cases on the command line
      when starting the web-based GUI.

Examples:

    <list type="bulleted">
      <item><c>ct_run -vts</c></item>
      <item><c><![CDATA[ct_run -vts -config <configfilename>]]></c></item>
      <item><c><![CDATA[ct_run -vts -config <configfilename> -suite <suitewithfullpath>
	      -case <casename>]]></c></item>
    </list>

From the GUI you can run tests and view the result and the logs.

<c>ct_run -vts</c> tries to open the <c>Common Test</c> start
      page in an existing web browser window, or start the browser if it is
      not running. Which browser to start can be specified with
      the browser start command option:

<c><![CDATA[ct_run -vts -browser <browser_start_cmd>]]></c>

Example:

<c><![CDATA[$ ct_run -vts -browser 'firefox&']]></c>

      <note>
The browser must run as a separate OS process, otherwise VTS hangs.
</note>

If no specific browser start command is specified, Firefox is
        the default browser on Unix platforms, and Internet Explorer on Windows.
	If <c>Common Test</c> fails to start a browser automatically, or <c>none</c> is
	specified as the value for <c>-browser</c> (that is, <c>-browser none</c>), start your
	favourite browser manually and type the URL that <c>Common Test</c>
	displays in the shell.

    <marker id="log_files"></marker>
    <title>Log Files</title>

As the execution of the test suites proceed, events are logged in
      the following four different ways:

      <list type="bulleted">
	<item>Text to the operator console.</item>
	<item>Suite-related information is sent to the major log file.</item>
	<item>Case-related information is sent to the minor log file.</item>
	<item>The HTML overview log file is updated with test results.</item>
	<item>A link to all runs executed from a certain directory is written in
	  the log named <c>all_runs.html</c> and direct links to all tests (the
	  latest results) are written to the top-level <c>index.html</c>.</item>
      </list>

Typically the operator, possibly running hundreds or thousands of
	test cases, does not want to fill the console with details
	about, or printouts from, specific test cases. By default, the
	operator only sees the following:

      <list type="bulleted">
	<item>A confirmation that the test has started and information about how
	  many test cases are executed in total.</item>
	<item>A small note about each failed test case.</item>
	<item>A summary of all the run test cases.</item>
	<item>A confirmation when the test run is complete.</item>
	<item>Some special information, such as error reports, progress
	  reports, and printouts written with <c>erlang:display/1</c>, or <c>io:format/3</c>
	  specifically addressed to a receiver other than <c>standard_io</c>
	  (for example, the default group leader process <c>user</c>).</item>
      </list>

To dig deeper into the general results, or
        the result of a specific test case, the operator can do so by
	following the links in the HTML presentation and read the
	major or minor log files. The "all_runs.html" page is a good
	starting point. It is located in <c>logdir</c> and contains
	a link to each test run, including a quick overview (with date and time,
	node name, number of tests, test names, and test result totals).

An "index.html" page is written for each test run (that is, stored in
	the <c>ct_run</c> directory tagged with node name, date, and time). This
	file provides an overview of all individual tests performed in the
	same test run. The test names follow the following convention:

      <list type="bulleted">
	<item><c>TopLevelDir.TestDir</c> (all suites in <c>TestDir</c> executed)</item>
	<item><c>TopLevelDir.TestDir:suites</c> (specific suites executed)</item>
	<item><c>TopLevelDir.TestDir.Suite</c> (all cases in <c>Suite</c> executed)</item>
	<item><c>TopLevelDir.TestDir.Suite:cases</c> (specific test cases executed)</item>
	<item><c>TopLevelDir.TestDir.Suite.Case</c> (only <c>Case</c> executed)</item>
      </list>

The "test run index" page includes a link to the <c>Common Test</c>
        Framework Log file in which information about imported
        configuration data and general test progress is written. This
        log file is useful to get snapshot information about the test
        run during execution. It can also be helpful when
        analyzing test results or debugging test suites.

The "test run index" page indicates if a test has missing
        suites (that is, suites that <c>Common Test</c> failed to
        compile). Names of the missing suites can be found in the
        <c>Common Test</c> Framework Log file.

The major log file shows a detailed report of the test run. It
        includes test suite and test case names, execution time, the
	exact reason for failures, and so on. The information is available in both
	a file with textual and with HTML representation. The HTML file shows a
	summary that gives a good overview of the test run. It also has links
	to each individual test case log file for quick viewing with an HTML
	browser.

The minor log files contain full details of every single test
	case, each in a separate file. This way, it is
	straightforward	to compare the latest results to that of previous
	test runs, even if the set of test cases changes. If application SASL
	is running, its logs are also printed to the current minor log file by the
	<seealso marker="common_test:ct_hooks_chapter#builtin_cths">
	  cth_log_redirect built-in hook</seealso>.

The full name of the minor log file (that is, the name of the file
	including the absolute directory path) can be read during execution
	of the test case. It comes as value in tuple
	<c>{tc_logfile,LogFileName}</c> in the <c>Config</c> list (which means it
	can also be read by a pre- or post <c>Common Test Hook</c> function). Also,
	at the start of a test case, this data is sent with an event
	to any installed event handler.	For details, see section
	<seealso marker="event_handler_chapter#event_handling">Event Handling</seealso>.

The log files are written continuously during a test run and links are
	always created initially when a test starts. Thevtest progress can therefore
	be followed simply by refreshing pages in the HTML browser.
	Statistics totals are not presented until a test is complete however.

	  <marker id="logopts"></marker>
	  <title>Log Options</title>

With start flag <c>logopts</c> options that modify some aspects
	  of the logging behavior can be specified.
	  The following options are available:

	  <taglist>
	    <tag><c>no_src</c></tag>
	    <item>
The HTML version of the test suite source code is not
	    generated during the test run (and is consequently not available
	    in the log file system).
</item>
	    <tag><c>no_nl</c></tag>
	    <item>
<c>Common Test</c> does not add a newline character <c>(\n)</c>
	    to the end of an output string that it receives from a call to, for example,
	    <c>io:format/2</c>, and which it prints to the test case log.
</item>
	    </taglist>

For example, if a test is started with:

<c>$ ct_run -suite my_SUITE -logopts no_src</c>

then printouts during the test made by successive calls to <c>io:format("x")</c>,
	  appears in the test case log as:

<c>xxx</c>

instead of each <c>x</c> printed on a new line, which is the default behavior.

	  <marker id="table_sorting"></marker>
	  <title>Sorting HTML Table Columns</title>

By clicking the name in the column header of any table
	    (for example, "Ok", "Case", "Time", and so on), the table rows are sorted
	    in whatever order makes sense for the type of value (for example,
	    numerical for "Ok" or "Time", and alphabetical for "Case"). The sorting is
	    performed through JavaScript code, automatically inserted into the HTML
	    log files. <c>Common Test</c> uses the <url href="http://jquery.com">jQuery</url>
	    library and the
	    <url href="http://tablesorter.com">tablesorter</url> plugin,
	    with customized sorting functions, for this implementation.

	  <title>The Unexpected I/O Log</title>

The test suites overview page includes a link to the Unexpected I/O Log.
	  In this log, <c>Common Test</c> saves printouts made with
	  <seealso marker="ct#log-2"><c>ct:log/2</c></seealso> and
	  <seealso marker="ct#pal-2"><c>ct:pal/2</c></seealso>, as well as captured system
	  error- and progress reports, which cannot be associated with particular test cases and
	  therefore cannot be written to individual test case log files. This occurs,
	  for example, if a log printout is made from an external process (not a test
	  case process), or if an error- or progress report comes in, during a short
	  interval while <c>Common Test</c> is not executing a test case or configuration
	  function, or while <c>Common Test</c> is currently executing a parallel
	  test case group.

	  <marker id="pre_post_test_io_log"></marker>
	  <title>The Pre- and Post Test I/O Log</title>

The <c>Common Test</c> Framework Log page includes links to the
	  Pre- and Post Test I/O Log. In this log, <c>Common Test</c> saves printouts made
	  with <c>ct:log/2</c> and <c>ct:pal/2</c>, as well as captured system error-
	  and progress reports, which take place before, and after, the test run.
	  Examples of this are printouts from a CT hook init- or terminate function, or
	  progress reports generated when an OTP application is started from a CT hook
	  init function. Another example is an error report generated because of
	  a failure when an external application is stopped from a CT hook terminate function.
	  All information in these examples ends up in the Pre- and Post Test I/O Log.
	  For more information on how to synchronize test runs with external user
	  applications, see section
	  <seealso marker="ct_hooks_chapter#synchronizing">Synchronizing</seealso>
	  in section Common Test Hooks.

	  <note>
Logging to file with <c>ct:log/2</c> or <c>ct:pal/2</c>
	  only works when <c>Common Test</c> is running. Printouts with <c>ct:pal/2</c>
	  are however always displayed on screen.
</note>

	<marker id="html_stylesheet"></marker>
	<title>HTML Style Sheets</title>

<c>Common Test</c> uses an HTML Style Sheet (CSS file) to control the look of
	  the HTML log files generated during test runs. If the log files are not
	  displayed correctly in the browser of your choice, or you prefer a more
	  primitive ("pre <c>Common Test</c> v1.6") look of the logs, use the start
	  flag/option:

 basic_html

This disables the use of style sheets and JavaScripts (see
	  <seealso marker="#table_sorting">Sorting HTML Table Columns</seealso>).

<c>Common Test</c> includes an optional feature to allow
	  user HTML style sheets for customizing printouts. The
	  functions in <c>ct</c> that print to a test case HTML log
	  file (<c>log/3</c> and <c>pal/3</c>) accept <c>Category</c>
	  as first argument. With this argument a category can be specified
	  that can be mapped to a selector in a CSS
	  definition. This is useful, especially for coloring text
	  differently depending on the type of (or reason for) the
	  printout. Say you want one color for test system
	  configuration information, a different one for test system
	  state information, and finally one for errors detected by the
	  test case functions. The corresponding style sheet can
	  look as follows:

 div.sys_config  { background:blue; color:white }
 div.sys_state   { background:yellow; color:black }
 div.error       { background:red; color:white }

To install the CSS file (<c>Common Test</c> inlines the definition in the
	  HTML code), the name can be provided when executing <c>ct_run</c>.

Example:

 $ ct_run -dir $TEST/prog -stylesheet $TEST/styles/test_categories.css

Categories in a CSS file installed with flag <c>-stylesheet</c>
	    are on a global test level in the sense that they can be used in any
	    suite that is part of the test run.

Style sheets can also be installed on a per suite and
	  per test case basis.

Example:

 -module(my_SUITE).
 ...
 suite() -> [..., {stylesheet,"suite_categories.css"}, ...].
 ...
 my_testcase(_) ->
     ...
     ct:log(sys_config, "Test node version: ~p", [VersionInfo]),
     ...
     ct:log(sys_state, "Connections: ~p", [ConnectionInfo]),
     ...
     ct:pal(error, "Error ~p detected! Info: ~p", [SomeFault,ErrorInfo]),
     ct:fail(SomeFault).

If the style sheet is installed as in this example, the categories are
	  private to the suite in question. They can be used by all test cases in the
	  suite, but cannot be used by other suites. A suite private style sheet,
	  if specified, is used in favor of a global style sheet (one specified
	  with flag <c>-stylesheet</c>). A stylesheet tuple (as returned by <c>suite/0</c>
	  above) can also be returned from a test case information function. In this case the
	  categories specified in the style sheet can only be used in that particular
	  test case. A test case private style sheet is used in favor of a suite or
	  global level style sheet.

In a tuple <c>{stylesheet,CSSFile}</c>, if <c>CSSFile</c> is specified
	  with a path, for example, <c>"$TEST/styles/categories.css"</c>, this full
	  name is used to locate the file. However, if only the file name is specified,
	  for example, <c>categories.css</c>, the CSS file is assumed to be located
	  in the data directory, <c>data_dir</c>, of the suite. The latter use is
	  recommended, as it is portable compared to hard coding path names in the
	  suite.

Argument <c>Category</c> in the previous example can have the
	  value (atom) <c>sys_config</c> (white on blue), <c>sys_state</c>
	  (black on yellow), or <c>error</c> (white on red).

    <marker id="repeating_tests"></marker>
    <title>Repeating Tests</title>

You can order <c>Common Test</c> to repeat the tests you specify. You can choose
       to repeat tests a number of times, repeat tests for a specific period of time,
       or repeat tests until a particular stop time is reached. If repetition is controlled by
       time, an action for <c>Common Test</c> to take upon time-out can be specified.
       Either <c>Common Test</c> performs all tests in the current run
       before stopping, or it stops when the current test job is finished. Repetition
       can be activated by <c>ct_run</c> start flags, or tuples in the <c>ct:run:test/1</c>
       option list argument. The flags (options in parentheses) are the following:

       <list type="bulleted">
       <item><c>-repeat N ({repeat,N})</c>, where <c>N</c> is a positive integer</item>
       <item><c>-duration DurTime ({duration,DurTime})</c>, where <c>DurTime</c> is the duration</item>
       <item><c>-until StopTime ({until,StopTime})</c>, where <c>StopTime</c> is finish time</item>
       <item><c>-force_stop ({force_stop,true})</c></item>
       <item><c>-force_stop skip_rest ({force_stop,skip_rest})</c></item>
       </list>
	  <taglist>
	    <tag><c>DurTime</c></tag>
	    <item>
The duration time is specified as <c>HHMMSS</c>, for example, <c>-duration 012030</c>
	    or <c>{duration,"012030"}</c>
, which means that the tests are executed and
	    (if time allows) repeated until time-out occurs after 1 hour, 20 minutes, and 30 seconds.
	    </item>
	    <tag><c>StopTime</c></tag>
	    <item>
The finish time can be specified as <c>HHMMSS</c> and is then interpreted as a
	    time today (or possibly tomorrow), but can also be specified as <c>YYMoMoDDHHMMSS</c>,
	    for example, <c>-until 071001120000</c> or <c>{until,"071001120000"}</c>. This means
	    that the tests are executed and (if time allows) repeated, until 12 o'clock on the 1st
	    of October 2007.

	    </item>
	  </taglist>

When time-out occurs, <c>Common Test</c> never aborts the ongoing test case,
          as this can leave the SUT in an undefined, and possibly bad, state.
	  Instead <c>Common Test</c>, by default, finishes the current test
	  run before stopping. If flag <c>force_stop</c> is
	  specified, <c>Common Test</c> stops when the current test job
	  is finished. If flag <c>force_stop</c> is specified with
	  <c>skip_rest</c>, <c>Common Test</c> only completes the current
	  test case and skips the remaining tests in the test job.

	  <note>
As <c>Common Test</c> always finishes at least the current test case,
	  the time specified with <c>duration</c> or <c>until</c> is never definitive.
</note>

Log files from every repeated test run is saved in normal <c>Common Test</c>
       fashion (described earlier).

<c>Common Test</c> might later support an optional feature to only store the last (and possibly
       the first) set of logs of repeated test runs, but for now the user must be careful not
       to run out of disk space if tests are repeated during long periods of time.

For each test run that is part of a repeated session, information about the
          particular test run is printed in the <c>Common Test</c> Framework Log. The information
	  includes the repetition number, remaining time, and so on.

Example 1:

 $ ct_run -dir $TEST_ROOT/to1 $TEST_ROOT/to2 -duration 001000 -force_stop

Here, the suites in test directory <c>to1</c>, followed by the suites in <c>to2</c>, are
          executed in one test run. A time-out event occurs after 10 minutes. As long as there is
	  time left, <c>Common Test</c> repeats the test run (that is, starting over with test <c>to1</c>).
	  After time-out, <c>Common Test</c> stops when the current job is finished
	  (because of flag <c>force_stop</c>). As a result, the specified test run can be
	  aborted after test <c>to1</c> and before test <c>to2</c>.

Example 2:

 $ ct_run -dir $TEST_ROOT/to1 $TEST_ROOT/to2 -duration 001000 -forces_stop skip_rest

Here, the same tests as in Example 1 are run, but with flag <c>force_stop</c> set to
       <c>skip_rest</c>. If time-out occurs while executing tests in directory <c>to1</c>,
          the remaining test cases in <c>to1</c> are skipped and the test is aborted without
	  running the tests in <c>to2</c> another time. If time-out occurs while executing
	  tests in directory <c>to2</c>, the remaining test cases in <c>to2</c> are skipped and
	  the test is aborted.

Example 3:

 $ date
 Fri Sep 28 15:00:00 MEST 2007

 $ ct_run -dir $TEST_ROOT/to1 $TEST_ROOT/to2 -until 160000

Here, the same test run as in the previous examples are executed (and possibly repeated).
          However, when the time-out occurs, after 1 hour, <c>Common Test</c> finishes the entire
	  test run before stopping (that is, both <c>to1</c> and <c>to2</c> are always executed in
          the same test run).

Example 4:

 $ ct_run -dir $TEST_ROOT/to1 $TEST_ROOT/to2 -repeat 5

Here, the test run, including both the <c>to1</c> and the <c>to2</c> test, is repeated
          five times.

       <note>
Do not confuse this feature with the <c>repeat</c> property of a test
          case group. The options described here are used to repeat execution of entire test runs,
	  while the <c>repeat</c> property of a test case group makes it possible to repeat
	  execution of sets of test cases within a suite. For more information about the latter,
	  see section <seealso marker="write_test_chapter#test_case_groups">Test Case Groups </seealso>
	  in section Writing Test Suites.
</note>

    <marker id="silent_connections"></marker>
      <title>Silent Connections</title>

The protocol handling processes in <c>Common Test</c>, implemented by <c>ct_telnet</c>,
      <c>ct_ssh</c>, <c>ct_ftp</c>, and so on, do verbose printing to the test case logs.
      This can be switched off with flag <c>-silent_connections</c>:

 ct_run -silent_connections [conn_types]

Here, <c>conn_types</c> specifies SSH, Telnet, FTP, RPC, and/or SNMP.

Example 1:

 ct_run ... -silent_connections ssh telnet

This switches off logging for SSH and Telnet connections.

Example 2:

 ct_run ... -silent_connections

This switches off logging for all connection types.

Fatal communication error and reconnection attempts are always printed, even if
         logging has been suppressed for the connection type in question. However, operations
         such as sending and receiving data are performed silently.

<c>silent_connections</c> can also be specified in a test suite. This is
	accomplished by returning a tuple, <c>{silent_connections,ConnTypes}</c>, in the
	<c>suite/0</c> or test case information list. If <c>ConnTypes</c> is a list of atoms
	(SSH, Telnet, FTP, RPC and/or SNMP), output for any corresponding connections
	are suppressed. Full logging is by default enabled for any connection of type not
	specified in <c>ConnTypes</c>. Hence, if <c>ConnTypes</c> is the empty list, logging
	is enabled for all connections.

Example 3:

 -module(my_SUITE).

 suite() -> [..., {silent_connections,[telnet,ssh]}, ...].

 ...

 my_testcase1() ->
     [{silent_connections,[ssh]}].

 my_testcase1(_) ->
     ...

 my_testcase2(_) ->
     ...

In this example, <c>suite/0</c> tells <c>Common Test</c> to suppress
	printouts from Telnet and SSH connections. This is valid for
	all test cases. However, <c>my_testcase1/0</c> specifies that
	for this test case, only SSH is to be silent. The result is
	that <c>my_testcase1</c> gets Telnet information (if any) printed
	in the log, but not SSH information. <c>my_testcase2</c> gets no
	information from either connection printed.

<c>silent_connections</c> can also be specified with a term
	in a test specification
	(see section <seealso marker="run_test_chapter#test_specifications">Test
	Specifications</seealso> in section Running Tests and Analyzing Results).
	Connections provided with start	flag/option <c>silent_connections</c>
	are merged with any connections listed in the test specification.

Start flag/option <c>silent_connections</c> and the test
	specification term override any settings made by the information functions
	inside the test suite.

      <note>
In the current <c>Common Test</c> version, the
	<c>silent_connections</c> feature only works for Telnet
	and SSH connections. Support for other connection types can be added
	in future <c>Common Test</c> versions.
</note>

</chapter>

redpajama_set_name: RedPajamaGithub


Kim was lounging in bed the following morning when she got the inevitable call from Kris.
"I know!" Kim said as she put the phone to her ear. "I'm on my way to the Hamptons!"
"Are you lying down? It sounds like you're still in bed," Kris said skeptically.
"I am literally dressed and walking out the door," Kim said. "I'll probably be there before you."
"OK good, see you there," Kris said, hanging up.
Kim dropped her phone and burrowed her face into Tiny Monkey, who'd been dozing next to her pillow. "Tiny Monkeyyyy can you kill a certain person for me please?"
Tiny Monkey lifted his head all alert and got a very serious look on his face like I'm ready are we doing this?
"No, no, I'm kidding. Kiiind of," Kim said, patting Tiny Monkey's head and settling him back down. "You go back to...whatever it is you do."
Tiny Monkey closed his eyes and pulled his tiny banana up close and snuggled back down, sighing under Kim's petting. Tiny Monkey wasn't always around every time she came home, but she generally found him sleeping in her bed when she woke up each morning. She wasn't totally sure what he did with the rest of his time. "You're the laziest ghost demon I ever met, I swear," Kim said, kissing him on the head.
"OK LET'S MOVE IT KEEKS!" Kim shouted to herself, clapping her hands and trying to psych herself up for the day.
A short while later she was dressed and riding the Metro to The Hamptons. She checked her social media, reviewing the memories and emotions from the casino opening at the Miraggio, both in her head and on her phone. Like what even had happened. She'd had this really intense connection with Willow in the hall. All this time Kim had been thinking Willow didn't remember her, or did but totally hated her, but it turned out Willow thought she was somehow protecting Kim? Or something? What was that about? All she could think about was the touch of Willow's fingers, caressing her hand, stroking her fingers. How Willow's dress had hugged her (OK, admittedly minimal) curves. How they'd been standing so close that a stray lock of Willow's blonde hair had delicately brushed against Kim's cheek, sending bursting heart emojis all through her body.
Willow had insisted that Kim stay away from her, but whatever. It was clear that Willow still had feelings for Kim, even if she was married to Cassio. Married, ugh. Kim's mind immediately circled back to Kanye. She was married too, let's not forget that. Why did she have these feelings for Willow? She loved Kanye so much, she couldn't even believe that her mind was so preoccupied with Willow. She felt so far away from him and every day away was going to make it more impossible to return. But she couldn't just leave, this world needed her. For just a little while longer. Now that she was a powerful celebrity again, everything would fall back into place. The world would get healthy again, probably any day now, and she could return back to Kanye and North.
But just that idea gave her a pang of regret, a tug in her chest about Willow. Could Kim leave Willow behind a second time? Why did she feel so stuck, like she belonged in two places and nowhere, all at once? But she couldn't help it, the feelings were not her own. Just because you're married do you suddenly stop being attracted to other people? Kim was rapidly became overwhelmed with guilt and decided to stop thinking about it altogether. Just in time because the Metro was pulling into The Hamptons.
Kim walked up to the front of the store to find...literally no one waiting for her. Maybe they got here early and went inside already?
"Hello?" Kim called, stepping through the door. "Who's here? Who we got?"
Her heels clicked through the foyer and into the open space of the store. Somehow it was even dirtier and more decrepit than it had been the last time she'd been here. The spider webs that hung from the rafters seemed to have multiplied and it was like an ancient, forgotten crypt in there now.


text:
https://img1.od-cdn.com/ImageType-100/11052-1/%7BD568A14D-AE38-4CCB-B2C2-920C7F2D878A%7DImg100.jpg
PRIVATE GAME | WILDLIFE RANCHING With its magnificent and diverse wildlife heritage, Southern Africa plays a vital role in conserving the world's biological diversity. The region boasts an extensive network of public parks, including international icons such as the Kruger, Hluhluwe-iMfolozi, Kgalagadi, Etosha, Chobe and Hwange, several of which also form part of larger transfrontier conservation areas. The region is known for its excellent track record of conserving threatened species such as elephant, rhino, Cape mountain zebra, bontebok, black wildebeest, cheetah and lion. An important aspect is the unique and vital role the private sector and market-based approaches play in supporting both wildlife conservation and socio-economic development in the region. Southern Africa's wildlife industry has become a contemporary world leader in conservation innovation, providing considerable ecological, biodiversity and economic benefits to the region." Wildlife ranchers love nature and are conservationists at heart - that is why they choose this lifestyle. Conceptualised by the executive editorial team of the popular publication Wildlife Ranching magazine, PRIVATE GAME will build on the successes achieved by Wildlife Ranching, whilst providing an engaging voice for the private wildlife sector.
PRIVATE GAME | WILDLIFE RANCHING.
Travel & Outdoor.

redpajama_set_name: RedPajamaCommonCrawl


DASH is a day-long walking puzzle solving event. If you choose to participate, you'll get to see some of the sights of Jamaica Plain, all while working together as a team, wracking your brains solving puzzles involving wordplay, spatial reasoning, and pop trivia.
The details are still being worked out, but we expect a walking distance of about 2-3 miles throughout the day. The starting and ending points should be in Jamaica Plain near the MBTA (either the Orange Line or the Green Line). There are places to eat lunch along the route.
I've never done one of these before... is it hard?
New Players: If you have never attended a DASH, BAPHL ("Boston Area Puzzle Hunt League") hunt, or the MIT Mystery Hunt, and you've never solved puzzles more complex than a Sudoku, American Crossword, or Paint by Numbers, this is the level for you. This may also be a good level for smaller teams of experienced players.
Experienced Players: If you have a lot of experience with past DASHes, the MIT Mystery Hunt, any BAPHL hunts, or solving a variety of other types of non-traditional puzzles, this is the level for you.
DASH Jr.: This year we've added a new tier for younger solvers (aged 10-16). Junior teams still need at least one adult chaperone. The chaperone will register the team and will be responsible for the team's safety and well-being thoughout the event. While it is expected (though not required) that some chaperones will assist with navigation and logistics, chaperones are not allowed to assist the Junior teams in any of the actual puzzle-solving. If Junior teams need hints, DASH Game Control will be available to assist. Contact [email protected] for questions about DASH, Jr.
DASH charges a $40 entrance fee per team. This money will go towards permits, puzzle production, and other incidentals.
Payment details are forthcoming. Watch this space.
We recommend a team of 3-4 people. Too large a team and it becomes harder to collaborate on the puzzles; too small and having so few solvers may slow you. Also, since we charge a flat fee per team, it becomes more expensive per person.
All right, we're sold. How do we register?
Registration opens on Friday, February 28, at 10am. Go to the DASH registration page to sign up.
We'll play in any weather. If it looks particularly bad, we'll update this site with latest info on the status of Boston DASH.
Please email [email protected] for further questions.
Interested, but can't come out on the 26th?
We will need at least one team of people to playtest the entire puzzle prior to the hunt. Please email [email protected] if you are interested in volunteering or would like to be a part of early playtests.


The County Attorney and I have reviewed the title information for the above-noted property. It is the County Attorney's advisory opinion and my official determination that the referenced parcels have the development rights that are indicated below.
The basis for this determination follows.
Our records indicate Tax Map 122, Parcel 24 contains 11.63 acres and 1 dwelling. The property is not in an Agricultural and Forestal District. The most recent recorded instrument for this property is recorded in Deed Book 2697, page 150.
1975. On the basis of this deed, the 11.763-acre parcel is determined to be a separate parcel of record with five (5) development rights.
Deed Book 2697, page 150, dated January 23, 2004, conveyed 11.763 acres from Kimberly Clements Powell, formerly known as Kimberly L. Clements, Joan D. Clements Colpo, and Rodney Clements to Murcielago, LLC. The property is described as being the same that was conveyed by the deed of record in Deed Book 585, page 05. This transaction had no effect on the development rights of Tax Map 122, Parcel 24.
Our records indicate Tax Map 122, Parcel 28 contains 3.549 acres and 1 dwelling. The property is not in an Agricultural and Forestal District. The most recent recorded instrument for this property is recorded in Deed Book 3017, page 99.
The most recent instrument for this parcel recorded prior to the adoption of the Zoning Ordinance, December 10, 1980, is recorded in Deed Book 615, page 314, and is dated February 24, 1977. This deed conveyed a life estate from Charlie Wingfield to Arthur S. Smith and Noraline Hudson. The life estate is recorded in Will Book 49, page 322. The parcel is described as containing 3 acres. On the basis of this deed, the 3-acre parcel is determined to be a separate parcel of record with one (1) development right.
Deed Book 1312, page 467 contains an affidavit and plat by Robert L. Lum, dated April 6, 1993. The affidavit describes the land as that of Arthur Smith and Noraline Hudson acquired by the will of Ella F. Wingfield. The plat shows the property contains 3.549 acres and describes it by reference to Deed Book 615, page 314. This transaction had no effect on the development right of Tax Map 122, Parcel 28.
Deed Book 1313, page 165, contains a certificate of plat. The plat by Kirk Hughes, dated March 1, 1993 corrects the boundary between Tax Map 123, Parcels 2 and 59, owned by Liva, Inc. and Tax Map 122, Parcel 28 owned by Arthur S. Smith and Noraline Hudson. The area affected by this plat includes the �School House Lot.� The plat carries a note stating that the purpose of the survey is to correct the boundary line as shown. This transaction had no effect on the development rights of Tax Map 122, Parcel 28.
Deed Book 2068, page 651, dated August 6, 2001, conveyed 3.549 acres from Arthur Smith and Noraline Hudson to James T. Marshall and Linda A. Marshall. The property is described by reference to the plat by Robert L. Lum that is recorded in Deed Book 1312, page 468. This transaction had no effect on the development rights of Tax Map 122, Parcel 28.
Deed Book 3017, page 99, dated June 23, 2005, conveyed 3.549 acres from James T. Marshall and Linda A. Marshall to Murcielago, LLC. The property is described as being the same as that which was conveyed by Deed Book 2068, page 651. This transaction had no effect on the development rights of Tax Map 122, Parcel 28.
Our records indicate Tax Map 123, Parcel 33 contains 10.93 acres and no dwellings. The property is not in an Agricultural and Forestal District. The most recent recorded instrument for this property is recorded in Deed Book 2818, page 296.
This analysis begins with the deed that is recorded in Deed Book 117, page 452 and dated November 11, 1896. This deed conveyed 11 acres, more or less, from John B. Moon and Marion D. Moon to Lucy Johnson. The property is described by metes and bounds. This deed established this lot as a parcel of record with five (5) development rights.
452. This transaction had no effect on the development rights of Tax Map 123, Parcel 33.
This transaction had no effect on the development rights of Tax Map 123, Parcel 33.
Deed Book 1806, page 626, dated April 13, 1999, conveyed 5 parcels from Mount Pleasant Farm, Inc. to Castle Hill Properties II, LLC. The property is described as being the same as that conveyed by the deed of record in Deed Book 1670, page 444. This transaction had no effect on the development rights of Tax Map 123, Parcel 33.
Deed Book 2218, page 296, dated June 7, 2002, conveyed five parcels from Castle Hill Properties II, LLC to Murcielago, LLC. The property, set forth in Schedule A is described as being the same as that conveyed by the deed of record in Deed Book 1806, page 626. This transaction had no effect on the development rights of Tax Map 123, Parcel 33.
Deed Book 2479, page 465 contains a plat by Trueline II Surveying. The plat shows Tax Map 123, Parcel 34, containing 1,061.58 acres and Tax Map 123, Parcel 33, containing 10.93 acres. This had no effect on the development rights of Tax Map 123, Parcel 33.
Our records indicate Tax Map 123, Parcel 34 contains 1,061.580 acres and 2 dwellings. The property is not in an Agricultural and Forestal District. The most recent recorded instrument for this property is recorded in Deed Book 2218, page 296.
A tract containing 912 acres as shown on a plat by Hugh F. Simms, C.L.S., dated May 1942, of record in Deed Book 254, page 523.
Two tracts adjoining the above described 912 acres on its westerly boundary, containing respectively, 125.7 acres and 26.6 acres, shown on a plat by Hugh F. Simms, C.L.S., dated May 1946, of record in Deed Book 268, page 576.
On the basis of this deed, the 1,064.3-acre tract is determined to be comprised of three (3) separate parcels of record containing respectively, 912 acres, 125.7 acres and 26.6 acres. Each of these separate parcels contains five (5) development rights. Copies of these plats are enclosed.
Deed Book 1670, page 444, Deed Book 1806, page 626 and Deed Book 2218, page 296, described in detail above, document the conveyance of Parcel 34 to Murcielago, LLC. These transactions had no effect on the development rights of the three parcels that comprise Tax Map 123, Parcel 34.
Plat dated January 24, 2003 showing Tax Map 123, Parcel 59 a containing 767.33 acres and Tax Map 123, Parcel 2 with no specified acreage.
These four plats had no effect on the development rights of Tax Map 123, Parcel 34.
The parcels are entitled to the noted development rights if all other applicable regulations can be met. These development rights may only be utilized within the bounds of the original parcel with which they are associated. These development rights are theoretical in nature but do represent the maximum number of lots containing less than twenty one acres allowed to be created by right. In addition to the development right lots, the parcel may create as many smaller parcels containing a minimum of twenty-one acres as it has land to make.
If you are aggrieved by this determination, you have a right to appeal it within thirty days of the date notice of this determination is given, in accordance with Section 15.2-2311 of the Code of Virginia. If you do not file a timely appeal, this determination shall be final and unappealable. An appeal shall be taken only by filing with the Zoning Administrator and the Board of Zoning Appeals a notice of appeal which specifies the grounds for the appeal. An appeal application must be completed and filed along with the fee of $120. The date notice of this determination was given is the same as the date of this letter.


text:
Lords back Ai Director's critique on Localism Bill
On 28th June, Lords from all political sides joined together to criticize the government's proposals in Part 2 of the Localism Bill, quoting Ai Director Jeremy Smith's criticism and critique first made in February 2011, in an article in Municipal Journal, "Fog over Parliament" .
Under the government's proposals, ministers would decide whether and how much to require local authorities to pay to central government, in the event of a fine from the European Court of Justice, which the minister decides they are responsible for. In his article, Jeremy had explained (a) how the government had misunderstood the relevant EU Treaty provisions, and (b) in particular, how the proposed clawback proposals were in breach of the principles of natural justice, with ministers being at once prosecutor, judge and co-defendant!
Baroness Gardner of Parkes cited this article in the recent Lords' debate.
"Understandably, the main area of concern has focused on the ability of a Minister to pass on a fine without any form of judicial or independent oversight. The need for independent oversight is particularly vital when one considers the complexity of the factors leading up to any infraction, not least in the area of air quality-I must here declare an interest in that where my home is in London is the most polluted air in the whole of the UK-and the fact that it is more than likely that one of the parties responsible for any breach will be the Government themselves. This concern was voiced eloquently by Jeremy Smith, barrister and former Secretary-General of the Council of European Municipalities and Regions, in the Municipal Journal in February. He said:
'There is, however, a wider point of concern about Part 2 of the Bill. There is no independent decision-maker. The minister takes the decision to make the local authority pay-even though central government may be partly or largely responsible for the infraction in the first place, for example, through delayed action, poor drafting, or for myriad other reasons. This means the minister may be simultaneously prosecutor, judge, jury-and co-defendant. This is surely not a healthy legal precedent … Therefore, Part 2 of the Localism Bill needs fundamental rethinking. If there is to be a claw-back provision at all, it should not be ministers who decide, since central government is almost certainly an interested party. The process should be for the minister to refer the matter to the High Court, or independent arbitrator, to determine any fair apportionment of the Article 260 fine imposed by the ECJ. The independent decision-maker can then take into account every party's share of responsibility'."
Her argument was supported by other peers, including ex-ministers such as Lord Jenkin and Newton, as well as Liberal Democrat peerLord Tope, and Labour peer Lord Beecham. The minister, Earl Attlee, indicated that while the government were not willing to remove the offending clauses from the Bill, the government was open to possible compromise on wording… and referred to a draft policy statement of the Greater London Authority being discussed with government, and which includes proposals for an external advisory body.
Jeremy Smith's original article had made other criticisms of the drafting of the Bill, several of which have in fact been taken into account in the latest version o0f the Bill. however, Earl Attlee's response in the debate indicate that the government's spokespeople still misunderstand important aspects of the legal position under the EU Treaties.
Other articles by Jeremy Smith
Moderating Cologne meetings for Palestine / Israel cooperation
Local partnerships for international development
Local governments creating their future together in Sarajevo
Helping create the City of 2030
Of Paris, the Council of Europe, local self-government, and just a touch of football
Cities having a go
International Women's Day – European Commission announces its Equality Charter
The crisis – time to defend Europe's local governments


I am creating this profile on behalf of my sister. She is currently working in the private sector as an accounts/finance professional, after having completed her bachelor's degree. We come from a middle class family with moderate family values. We belong to nuclear family currently living in Navi Mumbai.


text:
Deaths in Tipperary - Saturday, January 11, 2020
The late Mary Angela Forde
The death has occurred of Mary Angela Forde (née Horan), Pollanorman, Ballinaclough, Nenagh and formerly of Prospect Hill, Galway, (January 9th 2020), peacefully, in the wonderful care of the staff of Ashlawn Nursing Home, Nenagh, predeceased by her brothers Padraic and Bryan and sister Patricia. Sadly missed by her heartbroken husband Liam, children Marina, John, Brian and Liam and their partners Niall, Samantha, Ann and Denise, her sisters Rita, Lil and Frances, her dearly loved 12 grandsons, granddaughter and great-granddaughter, sisters-in-law, brothers-in-law, nieces, nephews, relatives, neighbours and friends.Reposing on Sunday 12th at Ryan's Funeral Home, Nenagh (E45 KN93) from 6pm until 8pm. Funeral arriving on Monday to Our Lady of the Wayside Church, Ballinaclough for Funeral Mass at 12 o'c followed by burial in Kilmore Cemetery. Family flowers only, donations, if desired, to Parkinsons Association of Ireland.
The late Cillian Russell
The death has occurred of Cillian Russell, 7 Manner Close, Carrickbeg, Carrick-on-Suir, Co. Tipperary. Reposing at his home on Sunday from 4pm until 8pm. Funeral arriving on Monday morning to St. Molleran's Church, Carrickbeg for Funeral Mass at 11am, burial afterwards in St. Mary's Cemetery. Family flowers only please. Donations to Little Blue Heroes and Make A Wish.
The late John Ryan
The death has occurred of John Ryan, Lower Green, Cashel, Co. Tipperary, January 8th 2020, peacefully in the loving care of the Staff at St. Benedict's Ward, St. Patrick's Hospital, Cashel. John, deeply regretted by his loving wife Helen, daughter Lisa, son-in-law Phil, grandchildren Jack and Evie, sisters Eleanor, Noleen, Nora and Mary, brothers-in-law, sisters-in-law, nephews, nieces, relatives, neighbours and friends. Reposing at Devitt's Funeral Parlour this Sunday evening from 5.30pm with Removal at 7.30pm to St. John the Baptist Church, Cashel. Requiem Mass on Monday at 12 noon followed by Burial in Cormac's Cemetery.
The late Imelda Stanley
The death has occurred of Imelda Stanley (née O'Reilly), Ballinacourty, Aherlow, Co. Tipperary and formerly of Dundrum, Dublin on the 10/1/20. Peacefully at home in the loving care of her family. Imelda. Predeceased by her twin sister Geraldine (Gerry). Deeply regretted by her loving husband Chris, son Ronan, daughters Ciara, Orlaith & Treasa, sons-in-law, daughter-in-law, brothers-in-law, sisters-in-law grandchildren, nephews, nieces, relatives, neighbours & friends. Funeral arriving at Lisvernane Church, Glen of Aherlow, Co.Tipperary on Sunday morning at 11.15am for 11.30am Mass. Cremation afterwards at The Shannon Crematorium, Illaunmanagh, Shannon, Co. Clare at 2pm. House Private Please. Family flowers only please. Donations if desired to Cluain Arann, Tipperary.
The late Catherine (Kitty) Withero
The death has occurred of Catherine (Kitty) Withero (née O'Connor), Blind Street, Tipperary Town, 10th Jan. 2020 - Catherine (Kitty) - in her 100th year - predeceased by her husband Tommy, sons Matthew & Thomas, daughters -in-law Ann & Pauline; deeply regretted by her loving family, John, Rosemary, Pat, Margaret & Connie, sons-in-law, daughter-in-law, brothers-in-law, sisters-in-law, grand-children, great grand-children, nephews, nieces, relatives, extended family, neighbours and friends.Reposing at Fogarty's Funeral Home, Bank Place, Tipperary Town this Sunday (Jan. 12th) from 5.00pm, removal at 7.00pm to St. Michael's Church, Tipperary Town. Funeral Mass Monday at 10.30am. Burial immediately afterwards in St. Michael's Cemetery, Tipperary Town.


Thread in 'Enforcer' started by Marxak, Mar 26, 2019.
A pretty decent, pretty standart Enforcer build. You can swap out some of the ML for a LL to make into a sniper fit. I didn't as i already had a Jagermech for that role so i made it into a finisher mech instead.


text:
Dieser Artikel zeigt die Ergebnisse der Qualifikationsrunden für die UNICEF Open 2010 der Damen. Insgesamt nahmen 32 Spielerinnen an der Qualifikation teil.

Einzel

Setzliste

Ergebnisse

Weblinks

WTA Tour 2010
Tennisturnier in 's-Hertogenbosch

redpajama_set_name: RedPajamaWikipedia