diff options
author | Björn Gustavsson <[email protected]> | 2012-10-17 16:47:29 +0200 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2012-10-26 11:30:37 +0200 |
commit | dafa6a1a7d478a61b220db811bc62f4b9b6d7de3 (patch) | |
tree | 15fdda8d131721cc806f9314a4cf75d5790b1b4b /lib/reltool/doc/man3 | |
parent | 5778da0c036cb6707af98612f98e22663eb35092 (diff) | |
download | otp-dafa6a1a7d478a61b220db811bc62f4b9b6d7de3.tar.gz otp-dafa6a1a7d478a61b220db811bc62f4b9b6d7de3.tar.bz2 otp-dafa6a1a7d478a61b220db811bc62f4b9b6d7de3.zip |
Keep the information about the current test case consistent
Three pieces of information could be out of sync in testcase
supervisor process at the time when a timetrap occurred:
* test_server_loc (process dictionary) - may indicate that a
framework function is executing
* test_server_init_or_end_conf (process dictionary) - indicates whether
init_per_testcase or end_per_testcase is executing
* The current configuration (#st.config) - set using a synchronous
call
There could be in a crash in spawn_fw_call/7 because the current
configuration was not defined when it was expected to.
To avoid the problem, introduce set_tc_state/2 (and a corresponding
message) to allow setting both an indication what the testcase is
executing (e.g. init_per_testcase, framework call, and so on), and
the current configuration. Use only that information to handle
a timetrap timeout (and aborted testcase and the other reasons
for the testcase process to terminate). Completely remove
test_server_init_or_end_conf.
Diffstat (limited to 'lib/reltool/doc/man3')
0 files changed, 0 insertions, 0 deletions