| Age | Commit message (Collapse) | Author |
|---|
|
https://bugs.erlang.org/browse/ERL-1013
|
|
|
|
|
|
|
|
Make even deprecated test cases use the tc_try function (so that
all test cases look the same). Also make the skip reason for those
test cases be slightly more readable.
|
|
Make use of the tc_try function(s) in all "active" test cases.
|
|
Add a utility function, tc_try/2,3, for running test cases
in a uniform way.
|
|
Adjusted some timeouts...
Also, add time stamp to the 'delivery' printouts.
|
|
OpenSSL does note seem to support NPN for DTLS so
we will have to skip those test
|
|
|
|
* peterdmv/ssl/psk:
ssl: Reorder testcases in ssl_api_SUITE
ssl: Fix handshake pause in TLS 1.3
ssl: Implement option honor_cipher_order in TLS 1.3
ssl: Add test for option supported_groups
ssl: Document option supported_groups
ssl: Fix ssl_api_SUITE:connection_information
ssl: Fix property tests for SSLv3
ssl: Update property tests with pre_shared_key
ssl: Implement pre_shared_key extension
ssl: Update property tests with psk_key_exchange_modes
ssl: Implement psk_key_exchange_modes extension
|
|
|
|
When one test in ssl_bench_SUITE is run as a
smoke test in the ordinary test runs it might get
problems on windows as time measurement is to coarse
|
|
```erl
1> mnesia:system_info(dump_log_time_threshold).
1000
```
Looks like a missing `0`!
|
|
When cancel'ing a timer, the ok return is either:
ok
or
{ok, Remaining}
The test case did not handle this (expected 'ok').
|
|
|
|
When waiting for the server command handler to start
listening, wait only for so long (5 seconds) and if
it has not managed to start listening before then,
we *skip* (because something is wrong with the *system*).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit fixes the connection_information testcase with TLS 1.3
connections.
|
|
Remove unsupported conversions from the old protocols.
This means mnesia on OTP-R18 nodes is no longer able to connect to
OTP-22 mnesia nodes.
Add protocol conversion for old nodes and sync_asym_trans transactions.
|
|
|
|
|
|
Implement encode/decode of pre_shared_key.
|
|
|
|
Implement encode/decode of psk_key_exchange_modes.
|
|
|
|
Transactions with sticky locks could with async_asym transactions be
committed in the wrong order, since asym transaction are spawned on
the remote nodes.
See ERL-768.
|
|
|
|
The suite was renamed tls_1_3_versions_SUITE but
apparently not via git, so the old file remained.
|
|
|
|
|
|
Do not test TLS 1.0 with these old versions as we do send hello extensions
for those implementations that will use them, and trailing unknown data
should be ignored by RFC complient implementations.
|
|
The (second) notify test case had a faulty "condition" test
(which skipped the case in all cases except when it was
supposed to be skipped :)
Also, the test start and stop of the manager during the
test case has been adjusted. We try to keep track of how
long time each start and stop takes. And also, if they takes
to long, we skip the case.
|
|
Make stopping the manager (the entire manager sup tree)
more easy. The function(s) for starting and stopping the
manager that exist in the snmpm module is (mostly) intended
for testing, making the stop function more "potent" is no
real problem (now any process not just the parent) can stop
the manager process tree.
|
|
We have seen one case when it takes unreasonably long time
to start the manager, which causes the test case (notify_started01)
to fail. We try to monitor the start, and if it takes to long
a time, we instead skip.
|
|
Also clean up code after previous test moves
|
|
Also refactor Rizzo tests to minimize them to only test
what actually can be tested. In practice this was already
done but a lot of legacy code remained. In the past timing
happened to make it look like it was possible to test
Rizzo-Dungeon mitigation in more detail, but it was based on
false assumptions that can not be applied to streams.
|
|
It looked like two messages was received in the "wrong" order,
cuasing the request_and_reply_plain test case tro fail (on
a windows machine).
On closer inspection, the reason was that an "unconditional"
receive was made when waiting for a (disconnect) callback.
But instead we received a secondary message. So, remove
the unconditional receive and instead introduce a timeout
(10 seconds).
|
|
It seems that the megaco_config process did not start (for
an unknown reason) and that resulted in a failed test case.
But starting the config process was not what the test case
was for, so it should have resulted in a skip.
Also, since we did not check the result of the config start,
we don't know why it failed.
So, move the start and stop of the megaco_config process
to the [init|end]_per_testcase function(s). If we fail to
start, then we skip (with a useful reason).
|
|
|
|
* peterdmv/ssl/fix-tls13-alpn:
ssl: Fix handling of ALPN in TLS 1.3
|
|
* ingela/ssl/restructure-tests:
ssl: Add API suites
ssl: Covered by property tests
ssl: Correct RSP/PSK and ALPN handling
ssl: Better grouping of test
|
|
This is also an effort to group test cases better.
More such commits will follow.
|
|
The load test suite did not properly handle attempts to
skip test cases. If we failed to start one of the slave
nodes for whatever reason (in this case we got a timeout),
this should not result in a failed test case as this is
out of the control of the test case. As it was, we *did*
try to issue a skip, but the "load controller" did not
detect it. It instead transformed it into a regular error.
|
|
|
