| Age | Commit message (Collapse) | Author |
|---|
|
To provide more info when analyzing failed test cases
an "event" queue (of max size 10) is added to both the
test MG and MGC. This event queue is printed when the
process exist.
Also, the multi_ack_timeout is wonky, so add anther
platform (sunos) to the skip list...
|
|
|
|
Adjusted some timeouts...
Also, add time stamp to the 'delivery' printouts.
|
|
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*).
|
|
|
|
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).
|
|
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.
|
|
Removed the "compile all" compiler directive for the mreq
megaco test suite.
This is not actually used in the "top" suite (for some reason).
We leave it like that, but still fix the various issues so that
it at least work.
|
|
Removed the "compile all" compiler directive for the load
megaco test suite.
|
|
Removed the "compile all" compiler directive for the examples
megaco test suite.
|
|
Removed the "compile all" compiler directive for the digit map
megaco test suite.
|
|
Removed the "compile all" compiler directive for the config
megaco test suite.
|
|
Removed the "compile all" compiler directive for the codec
megaco test suite.
|
|
Removed the "compile all" compiler directive for the call flow
megaco test suite.
|
|
Removed the "compile all" compiler directive for the actions
megaco test suite.
|
|
Removed the "compile all" compiler directive for the appup
megaco test suite.
|
|
Removed the "compile all" compiler directive for the app
megaco test suite.
|
|
Removed the "compile all" compiler directive for the top
megaco test suite.
|
|
Reworked the megaco test generator (megaco_test_generator) behaviour
to remove compiler warnings.
|
|
Removed all use of erlang:now() and the deprecated random module
from the test suite.
|
|
Make the mib (sub-) test suite more verbose and also
do some printout when starting slave nodes (to see
just how long time it takes).
The connect test case failed on one (possibly) slow
host during what looked lite mgc start (timeout). But
since there where no printouts during that phase, there
is no way to know what was going on.
|
|
|
|
Make the test suite log more readable.
Normal io and the debug printouts from megaco does not mix well.
Its difficult to know the proper timeline. So add some "sleeps"
so that its easier to read.
|
|
The actual "improvement" has to do with io. That is, making
sure we get any. A test case failed (on a OpenIndiana VM),
which basically only pointed to which line in the test code.
But it was impossible to figure out from that what actually
had gone wrong.
Also removed the 'export all' compiler flag, which caused a
whole bunch of unused function to become visible. Commented
out those...
|
|
The simple test case was faulty in that the simple example
(which it is testing) require that the MGC and MG run on different
erlang nodes. But the test case did not do this. Instead, it ran
both the MGC and the MG on the test server node, which caused
the test case to fail 1 time of 10.
|
|
We did not check the actual result of the timer cancel
operation before continuing, which seems to cause
problems on some platforms (where the timer may actually
expire even though we have 100 ms to cancel).
So now we check the cancel result, and if we did not
succeed, we instead skip the test case.
|
|
|
|
The examples test suite was hard to debug just based
on its output (both plain debug printouts and printouts
generated via dbg). Some timeouts has been added between
the various actions so that it will be easier to understand
the output.
|
|
|
|
Make the test suite log more readable.
Normal io and the debug printouts from megaco does not mix well.
Its difficult to know the proper timeline. So add some "sleeps"
so that its easier to read.
|
|
The simple test case was faulty in that the simple example
(which it is testing) require that the MGC and MG run on different
erlang nodes. But the test case did not do this. Instead, it ran
both the MGC and the MG on the test server node, which caused
the test case to fail 1 time of 10.
|
|
We did not check the actual result of the timer cancel
operation before continuing, which seems to cause
problems on some platforms (where the timer may actually
expire even though we have 100 ms to cancel).
So now we check the cancel result, and if we did not
succeed, we instead skip the test case.
|
|
|
|
The examples test suite was hard to debug just based
on its output (both plain debug printouts and printouts
generated via dbg). Some timeouts has been added between
the various actions so that it will be easier to understand
the output.
|
|
|
|
|
|
Since no test suites includede test_server.hrl, there is no need
to have test_server in the include path or code path.
|
|
|
|
'bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r15' into bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r16
Conflicts:
lib/megaco/doc/src/notes.xml
lib/megaco/src/flex/megaco_flex_scanner_drv.flex.src
lib/megaco/test/megaco_codec_prev3a_test.erl
lib/megaco/test/megaco_codec_prev3b_test.erl
lib/megaco/test/megaco_codec_prev3c_test.erl
lib/megaco/test/megaco_codec_v1_test.erl
lib/megaco/test/megaco_codec_v2_test.erl
lib/megaco/test/megaco_codec_v3_test.erl
lib/megaco/vsn.mk
|
|
|
|
|
|
|
|
'bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r14' into bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r15
Conflicts:
lib/megaco/.gitignore
lib/megaco/doc/src/notes.xml
lib/megaco/src/app/megaco.appup.src
lib/megaco/src/flex/megaco_flex_scanner_drv.flex.src
lib/megaco/test/megaco_codec_v2_test.erl
lib/megaco/vsn.mk
|
|
|
|
|
|
'bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r13' into bmk/megaco/flex_buffer_overrun_while_scanning_prop_parms/OTP-10998/r14
Conflicts:
lib/megaco/doc/src/notes.xml
lib/megaco/src/app/megaco.appup.src
lib/megaco/test/megaco_codec_flex_lib.erl
lib/megaco/test/megaco_codec_v2_test.erl
lib/megaco/test/megaco_test_lib.erl
lib/megaco/vsn.mk
|
|
|
