diff options
| -rw-r--r-- | CIAO/ChangeLog | 6 | ||||
| -rw-r--r-- | CIAO/connectors/dds4ccm/tests/Getter/README | 14 | ||||
| -rw-r--r-- | CIAO/connectors/dds4ccm/tests/Reader/README | 21 |
3 files changed, 39 insertions, 2 deletions
diff --git a/CIAO/ChangeLog b/CIAO/ChangeLog index 67af82945f9..9bd6ff0c63c 100644 --- a/CIAO/ChangeLog +++ b/CIAO/ChangeLog @@ -1,3 +1,9 @@ +Thu Dec 10 08:37:49 UTC 2009 Marcel Smit <msmit@remedy.nl> + + * connectors/dds4ccm/tests/Getter/README: + * connectors/dds4ccm/tests/Reader/README: + Described the tests. + Thu Dec 10 08:21:16 UTC 2009 Johnny Willemsen <jwillemsen@remedy.nl> * connectors/dds4ccm/impl/ndds/Updater_T.cpp: diff --git a/CIAO/connectors/dds4ccm/tests/Getter/README b/CIAO/connectors/dds4ccm/tests/Getter/README index 50794f6a1eb..00bcdbee833 100644 --- a/CIAO/connectors/dds4ccm/tests/Getter/README +++ b/CIAO/connectors/dds4ccm/tests/Getter/README @@ -1,3 +1,15 @@ # $Id$ -This test tests the reader.
\ No newline at end of file +This test tests the Getter. + +Before the Sender starts writing samples to DDS, he informs the +Receiver (via a 'normal' CCM interface) about how many keys and +iterations to get from DDS. The receiver starts waiting on those +samples by calling get_one or get_many, using a timeout. +In the meantime the Sender will sleep for half a second before actual +writing the samples to DDS. +Once the DDS connector on the receiver side receives the written samples, +he should wake up and should return the samples to the user code. + +To prevent deadlocks, both getting and writing takes place on the +ORB reactor thread.
\ No newline at end of file diff --git a/CIAO/connectors/dds4ccm/tests/Reader/README b/CIAO/connectors/dds4ccm/tests/Reader/README index 50794f6a1eb..ec69fbb989d 100644 --- a/CIAO/connectors/dds4ccm/tests/Reader/README +++ b/CIAO/connectors/dds4ccm/tests/Reader/README @@ -1,3 +1,22 @@ # $Id$ -This test tests the reader.
\ No newline at end of file +This test tests the reader. + +The following methods of the reader are tested: + +* read_one +* read_all +* read_one_last +* read_one_all + +First of all, the Sender writes a known number of samples to DDS. +After that the Sender informs the Receiver which test is about +to run and how many samples should be read from DDS. Before the +Receiver starts reading, he must find out that all samples resides +in DDS on the receiving side. He does that by calling read_last every +time a DATA_ON_READERS_STATUS comes in on the ConnectorStatusListener. +Once the very last sample is in DDS on the receiving side, the Receiver +starts to read the samples. Afterwards he checks wether all samples are +avaiable (thus are read correctly from DDS). + +The Receiver also test whether the correct exceptions are thrown. |