root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

adding pub_and_close_test in network_client_SUITE

This commit is contained in:
Vlad Ionescu 2009-07-10 13:44:32 +01:00
parent 0b0f413656
commit ebf1351cfb
2 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
deps/amqp_client/test/network_client_SUITE.erl vendored
View File

@ -65,6 +65,12 @@ teardown_test() ->
rpc_test() -> rpc_test() ->
test_util:rpc_test(new_connection()). test_util:rpc_test(new_connection()).
pub_and_close_test() ->
{timeout, 60,
fun() ->
test_util:pub_and_close_test(new_connection(), new_connection())
end}.
%%--------------------------------------------------------------------------- %%---------------------------------------------------------------------------
%% Negative Tests %% Negative Tests

9
deps/amqp_client/test/test_util.erl vendored
View File

@ -307,15 +307,6 @@ basic_reject_test(Connection) ->
%% So, in the end, if we set up a consumer, we should get all the important %% So, in the end, if we set up a consumer, we should get all the important
%% messages, but not all spam (we waited for all messages in buffer to be sent, %% messages, but not all spam (we waited for all messages in buffer to be sent,
%% but didn't allow further adding to the buffer). %% but didn't allow further adding to the buffer).
%% This test sometimes fails due to other causes - if a message leaves the
%% socket doesn't mean it will be delivered; or maybe all spam messages have
%% actually been buffered before the connection closed, thus all of them will
%% be delivered.
%% ... and sometimes succeedes (when it shouldn't) - the messages might be
%% buffered and delivered very quickly (but not the spam), before the
%% connection gets to close.
%% ... though in the end, per a larger number of tests, the greater of the
%% success and failure rates reflects the real results.
%% First connection is used for sending messages, second connection is used to %% First connection is used for sending messages, second connection is used to
%% get the messages. %% get the messages.
pub_and_close_test(Connection1, Connection2) -> pub_and_close_test(Connection1, Connection2) ->