summaryrefslogtreecommitdiff
path: root/TAO/orbsvcs/tests/Miop/McastHello/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/orbsvcs/tests/Miop/McastHello/README')
-rw-r--r--TAO/orbsvcs/tests/Miop/McastHello/README29
1 files changed, 8 insertions, 21 deletions
diff --git a/TAO/orbsvcs/tests/Miop/McastHello/README b/TAO/orbsvcs/tests/Miop/McastHello/README
index b9b1c26edfb..d96228dc866 100644
--- a/TAO/orbsvcs/tests/Miop/McastHello/README
+++ b/TAO/orbsvcs/tests/Miop/McastHello/README
@@ -1,28 +1,15 @@
/**
-@page Hello Test README File
+@page McastHello Test README File
- The simplest possible test for TAO. This is a very simple
-test for TAO, it can be argued that it is in fact too simple to do
-anything useful, i.e. chances are that this test will always pass.
+This test verifies basic functionality of the MIOP support in TAO.
+It creates two servers that listen on the same group id for requests.
+A client then sends a few requests using MIOP. If both servers
+receive the multicast requests as expected, the test is successful.
+The most likely failure of the test is if the servers don't receive
+the requests and subsequently time out.
- The goals of writing this test are:
-
-- Provide a very simple, very fast 'smoke test' for ORB developers.
- If Hello does not pass then something is extremely broken and you
- should go back to the drawing board.
-- Provide a code base to write more complex tests
-- Rule out basic infrastructure problems: if this test does not work
- for a user then the infrastructure (network, DNS, host
- configuration) are more likely to be at fault than the ORB.
-- External users are often asked to send us a 'simple test' for their
- use case, we can now point them to this test to explain what do we
- mean by "simple".
-
- Please refrain from "improving", extending or expanding this
-test, if you need to change
-
- To run the test use the run_test.pl script:
+ To run the test, use the run_test.pl script:
$ ./run_test.pl