From e91ba727f534553a34c05ad54247a0485e2429ff Mon Sep 17 00:00:00 2001 From: Peter Andersson Date: Mon, 5 Sep 2011 19:51:59 +0200 Subject: Implement support for running suites with test case groups through the debugger OTP-9518 --- lib/common_test/doc/src/run_test_chapter.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'lib/common_test/doc/src/run_test_chapter.xml') diff --git a/lib/common_test/doc/src/run_test_chapter.xml b/lib/common_test/doc/src/run_test_chapter.xml index e668568795..e944f215f6 100644 --- a/lib/common_test/doc/src/run_test_chapter.xml +++ b/lib/common_test/doc/src/run_test_chapter.xml @@ -322,8 +322,9 @@ are to be executed by Common Test, and those functions only. If the step option config is specified, breakpoints will also be initially set on the configuration functions in the suite, i.e. - init_per_suite/1, end_per_suite/1, init_per_testcase/2 - and end_per_testcase/2.

+ init_per_suite/1, end_per_suite/1, + init_per_group/2, end_per_group/2, + init_per_testcase/2 and end_per_testcase/2.

Common Test enables the Debugger auto attach feature, which means that for every new interpreted test case function that starts to execute, a new trace window will automatically pop up. (This is because each test -- cgit v1.2.3 From 09fbbccd5a8638601e44c605cd887f90b85d7d60 Mon Sep 17 00:00:00 2001 From: Peter Andersson Date: Fri, 30 Sep 2011 13:26:59 +0200 Subject: Update documentation OTP-9396 OTP-9372 OTP-9155 --- lib/common_test/doc/src/run_test_chapter.xml | 35 ++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) (limited to 'lib/common_test/doc/src/run_test_chapter.xml') diff --git a/lib/common_test/doc/src/run_test_chapter.xml b/lib/common_test/doc/src/run_test_chapter.xml index e944f215f6..d3c6847d85 100644 --- a/lib/common_test/doc/src/run_test_chapter.xml +++ b/lib/common_test/doc/src/run_test_chapter.xml @@ -128,6 +128,15 @@

$ ct_run -suite $SYS1_TEST/setup_SUITE -case start stop

$ ct_run -suite $SYS1_TEST/setup_SUITE -group installation -case start stop

+

It is also possible to combine the dir, suite and group/case flags. E.g, to run + x_SUITE and y_SUITE in directory testdir:

+ +

$ ct_run -dir ./testdir -suite x_SUITE y_SUITE

+ +

This has the same effect as calling:

+ +

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

+

Other flags that may be used with ct_run:

]]>, specifies where the HTML log files are to be written. @@ -165,6 +174,8 @@ ]]>, points out a file containing a decryption key for encrypted configuration files. , switches off html enhancements that might not be compatible with older browsers. + ]]>, makes it possible to modify aspects of the logging behaviour, see + Log options below.

Directories passed to Common Test may have either relative or absolute paths.

@@ -645,6 +656,30 @@ to follow test progress simply by refreshing pages in the HTML browser. Statistics totals are not presented until a test is complete however.

+
+ + Log options +

With the logopts start flag, it's possible to specify + options that modify some aspects of the logging behaviour. + Currently, the following options are available:

+ + no_src + no_nl + +

With no_src, the html version of the test suite source + code will not be generated during the test run (and consequently + not be available in the log file system).

+

With no_nl, Common Test will not add a newline character + (\n) to the end of an output string that it receives from a call to e.g. + io:format/2, and which it prints to the test case log.

+

For example, if a test is started with:

+

$ ct_run -suite my_SUITE -logopts no_src

+

then printouts during the test made by successive calls to io:format("x"), + will appear in the test case log as:

+

xxx

+

instead of each x printed on a new line, which is the default behaviour.

+
+
-- cgit v1.2.3