From 4d658008be5a08ddadbe75ebadb9ef124436b76e Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Tue, 14 Mar 2017 15:59:23 +0100 Subject: Prepare release --- lib/common_test/doc/src/notes.xml | 117 ++++++++++++++++++++++++++++++++++++++ lib/common_test/vsn.mk | 2 +- 2 files changed, 118 insertions(+), 1 deletion(-) (limited to 'lib/common_test') diff --git a/lib/common_test/doc/src/notes.xml b/lib/common_test/doc/src/notes.xml index 83e6511c04..efeacd4a72 100644 --- a/lib/common_test/doc/src/notes.xml +++ b/lib/common_test/doc/src/notes.xml @@ -33,6 +33,123 @@ notes.xml +
Common_Test 1.14 + +
Fixed Bugs and Malfunctions + + +

The following corrections and improvements are done in + the common_test hook handling:

An + extra argument, Suite, is added as the first + argument to each of the following hook callback + functions:

+ pre_init_per_group + post_init_per_group + pre_end_per_group + post_end_per_group + pre_init_per_testcase + post_init_per_testcase + pre_end_per_testcase + post_end_per_testcase + on_tc_fail + on_tc_skip

For backwards + compatibility, if the new function is not exported from a + hook callback module, common_test will fall back + to the old interface and call the function without the + Suite argument.

If either + init_per_suite or end_per_suite exists, but + not the other, then the non-existing function will be + reported as failed with reason undef in the test + log. The same goes for init/end_per_group. This + has always been a requirement according to the user's + guide, but now common_test is more explicit in the + report.

If init_per_suite + was exported from a test suite, but not + end_per_suite, then pre/post_end_per_suite + was called with Suite=ct_framework instead of the + correct suite name. This is now corrected.

 +

If end_per_group was exported from a + suite, but not init_per_group, then + end_per_group was never called. This is now + corrected.

Tests that were skipped + before calling pre_init_per_* got faulty calls to + the corresponding post_init_per_*. E.g. if a test + was skipped because suite/0 failed, then + post_init_per_suite would be called even though + pre_init_per_suite and init_per_suite were + not called. This is now corrected so a post_* + callback will never be called unless the corresponding + pre_* callback has been called first.

 +

Tests that were skipped before or in + init_per_testcase got faulty calls to + pre_end_per_testcase and + post_end_per_testcase. This is now corrected so + pre/post_end_per_testcase are not called when + end_per_testcase is not called.

 +

If an exit signal causes the test case process to die + while running init_per_testcase, the case was + earlier reported as failed with reason {skip,...}. + This is now corrected so the case will be marked as + skipped.

If an exist signal causes + the test case process to die while running + end_per_testcase, the case was earlier marked as + failed. This is now corrected so the status of the test + case is not changed - there is only a warning added to + the comment field.

If a test case + was skipped because of option + {force_stop,skip_rest} or because of a failed + sequence, then no tc_start event would be sent, + only tc_done. This is now corrected so both events + are sent.

When skipping or failing + in a configuration function, the configuration function + itself would get {auto_skipped,Reason}, + {skipped,Reason} or {failed,Reason} in the + hook callbacks on_tc_skip or on_tc_fail. + The other test cases that were skipped as a result of + this would only get Reason in on_tc_skip. + This is now corrected so even the configuration function + that caused the skip/fail will only get Reason in + the hook callback.

 +

+ Own Id: OTP-10599 Aux Id: kunagi-344 [255]

+ + +

+ When a test case was skipped by a skip_cases + statement in a test spec, then cth_surefire would + erroneously mark the previous test case as skipped in the + xml report. The actually skipped test case would not be + present in the xml report at all. This is now corrected.

+

+ Own Id: OTP-14129 Aux Id: seq13244

+ + +

The multiply_timetraps and + scale_timetraps options did not work with test + specifications, which has been corrected.

+

+ Own Id: OTP-14210

+ + +
+ + +
Improvements and New Features + + +

+ ct_testspec:get_tests/1 is added. This is used by rebar3 + to get all directories that must be compiled when running + tests from testspec - instead of implementing testspec + parsing in rebar3.

+

+ Own Id: OTP-14132

+ + +
+ +
+
Common_Test 1.13
Fixed Bugs and Malfunctions diff --git a/lib/common_test/vsn.mk b/lib/common_test/vsn.mk index 2fab4d3883..e6ae8b2e7a 100644 --- a/lib/common_test/vsn.mk +++ b/lib/common_test/vsn.mk @@ -1 +1 @@ -COMMON_TEST_VSN = 1.13 +COMMON_TEST_VSN = 1.14 -- cgit v1.2.3