Age | Commit message (Collapse) | Author |
|
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.
|
|
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.
|
|
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.
|
|
When we fail to start a (slave) node with reason timeout,
its possible that it actually succeeded, which will cause
the following test case(s) init to fail (with 'already started',
since it which also try to start this node).
But since we don't know if we get this because for this reason
or because the previous test case failed to clean up after
itself, we cannot assume that the state of the node is ok
(and therefor use it). So, we attempt to stop it, and try
start it again (*one* time).
This has been observed on one (slooow) VM host.
|
|
Improve the checks for if/when we shall run the IPv6
test cases.
OTP-15764
|
|
Add an "os test" to the IPv6 group init.
On "old" version of darwin (9.8.0) its
simply to messy to figure out our IPv6
address, so its better to simply skip the
IPv6 tests on those machines.
OTP-15764
|
|
|
|
For the notify_started02 test case we (now) try estimate how
long we should wait for completion (based on the time of the
first iteration). On slow machines, it takes longer to start and
stop the manager, so adjust the total timeout accordingly.
|
|
Try to handle "failures" during init_per_testcase such that
if they are either throw or exit, then they are transformed
into a skip.
|
|
On some linux platforms "they" add a 127.0.1.1
in the hosts file, wich can cause problems for
some (manager) test cases. So, just to be on
the safe side, make sure we bind to the configured
address.
Note that this has nothing to do with the current
issue.
|
|
|
|
|
|
|
|
The test for ipv6 could return false positives which resulted in failing
test cases due lack of full ipv6 support.It could be nice with a working
run-time check but this will do for now.
|
|
|
|
As a first step to removing the test_server application as
as its own separate application, change the inclusion of
test_server.hrl to an inclusion of ct.hrl and remove the
inclusion of test_server_line.hrl.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add some more error handling (a try catch block) when starting
both manager and agent.
|
|
When starting and stopping apps verify success. If failure
to start or stop app force failure of test case or init/fin
of test case. Also, be more verbose regarding stop results
during test case finish.
|
|
Improved handling of unexpected return values from snmpm_user
callback functions. Violations of the documented API (crashes or
invalid return values) will now result in an error message.
Updated doc for snmpm_user bahaviour and some other stuff.
Add more (common) type defs.
Update manager example.
Fixed manager test(s).
Fixed unused vars in (manager) test suite.
Make test user follow defined behaviour.
|
|
Updated manager test suite to use only the api. The test cases
that tested the old api (01), are now skipped.
OTP-10027
|
|
Updated manager test suite with groups that
tests the new net-if module, snmpm_net_if_mt.
Also fixed the suite, group and test-case init
functions for a number of sub-suites.
OTP-9876
|
|
Made the inform_request table public (to allow
the worker processes to insert data). Also added
test cases (this was done by adding "mt" groups).
OTP-9876
|
|
OTP-9851
|
|
|
|
assumed to be IPv4.
This has now been changed so that it can also be IPv6. To facilitate this,
the transportDomain is now a (new) valid option.
This also mean that the transport behaviour has changed.
OTP-9305
[agent] A temporary fix for transport domain, specifically regarding
trap sending. This is done in order to make testing possible,
pending merge from topic branch.
OTP-9400
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|