aboutsummaryrefslogtreecommitdiffstats
path: root/lib/diameter/test/diameter_event_SUITE.erl
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2014-11-03 09:36:09 +0100
committerAnders Svensson <[email protected]>2014-11-03 12:12:36 +0100
commit3b51661f1f9f70cf820026cb345523c05aad2dfa (patch)
tree4950d9fd3e54af739f849f170296571972a1e8bc /lib/diameter/test/diameter_event_SUITE.erl
parentc3b9ebc6cf9619c220b75601b8f02737052901b3 (diff)
downloadotp-3b51661f1f9f70cf820026cb345523c05aad2dfa.tar.gz
otp-3b51661f1f9f70cf820026cb345523c05aad2dfa.tar.bz2
otp-3b51661f1f9f70cf820026cb345523c05aad2dfa.zip
Check {connect,watchdog}_timer distinction in event testcases
The connect timer is currently ignored by a connecting transport, so the check causes one testcase to fail.
Diffstat (limited to 'lib/diameter/test/diameter_event_SUITE.erl')
-rw-r--r--lib/diameter/test/diameter_event_SUITE.erl26
1 files changed, 21 insertions, 5 deletions
diff --git a/lib/diameter/test/diameter_event_SUITE.erl b/lib/diameter/test/diameter_event_SUITE.erl
index 64199895be..f43f111d20 100644
--- a/lib/diameter/test/diameter_event_SUITE.erl
+++ b/lib/diameter/test/diameter_event_SUITE.erl
@@ -107,10 +107,18 @@ start_server(Config) ->
%% Connect with matching capabilities and expect the connection to
%% come up.
up(Config) ->
- {Svc, Ref} = connect(Config, []),
+ {Svc, Ref} = connect(Config, [{connect_timer, 5000},
+ {watchdog_timer, 15000}]),
start = event(Svc),
- {up, Ref, {_,_Caps}, _Config, #diameter_packet{}} = event(Svc),
- {watchdog, Ref, _, {initial, okay}, _} = event(Svc).
+ {up, Ref, {TPid, Caps}, Cfg, #diameter_packet{}} = event(Svc),
+ {watchdog, Ref, _, {initial, okay}, _} = event(Svc),
+ %% Kill the transport process and see that the connection is
+ %% reestablished after a watchdog timeout, not after connect_timer
+ %% expiry.
+ exit(TPid, kill),
+ {down, Ref, {TPid, Caps}, Cfg} = event(Svc),
+ {watchdog, Ref, _, {okay, down}, _} = event(Svc),
+ {reconnect, Ref, _} = event(Svc, 10000, 20000).
%% Connect with non-matching capabilities and expect CEA from the peer
%% to indicate as much and then for the transport to be restarted
@@ -119,11 +127,12 @@ down(Config) ->
{Svc, Ref} = connect(Config, [{capabilities, [{'Acct-Application-Id',
[?DICT_ACCT:id()]}]},
{applications, [?DICT_ACCT]},
- {connect_timer, 5000}]),
+ {connect_timer, 5000},
+ {watchdog_timer, 20000}]),
start = event(Svc),
{closed, Ref, {'CEA', ?NO_COMMON_APP, _, #diameter_packet{}}, _}
= event(Svc),
- {reconnect, Ref, _} = event(Svc).
+ {reconnect, Ref, _} = event(Svc, 4000, 10000).
%% Connect with matching capabilities but have the server delay its
%% CEA and cause the client to timeout.
@@ -165,6 +174,13 @@ uniq() ->
event(Name) ->
receive #diameter_event{service = Name, info = T} -> T end.
+event(Name, TL, TH) ->
+ T0 = now(),
+ Event = event(Name),
+ DT = timer:now_diff(now(), T0) div 1000,
+ {true, true, DT, Event} = {TL < DT, DT < TH, DT, Event},
+ Event.
+
start_service(Name, Opts) ->
diameter:start_service(Name, [{monitor, self()} | Opts]).