[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] r14912 - gnunet/src/testing
From: |
gnunet |
Subject: |
[GNUnet-SVN] r14912 - gnunet/src/testing |
Date: |
Thu, 7 Apr 2011 12:18:14 +0200 |
Author: nevans
Date: 2011-04-07 12:18:14 +0200 (Thu, 07 Apr 2011)
New Revision: 14912
Modified:
gnunet/src/testing/test_testing_peergroup.c
Log:
add comment about extending this basic testcase
Modified: gnunet/src/testing/test_testing_peergroup.c
===================================================================
--- gnunet/src/testing/test_testing_peergroup.c 2011-04-07 10:10:52 UTC (rev
14911)
+++ gnunet/src/testing/test_testing_peergroup.c 2011-04-07 10:18:14 UTC (rev
14912)
@@ -80,6 +80,22 @@
GNUNET_log (GNUNET_ERROR_TYPE_DEBUG,
"Peer Group started successfully, ending test!\n");
+ /**
+ * If something is to actually be DONE with the testcase, it should
+ * be put in here. Usually there will be a struct declared (or global
+ * variables can be used) to keep track of the state, statistics,
+ * handles to peers, etc. The example here is the opaque "TestCaseData"
+ * struct that could be passed into a function "additional_code_for_testing"
+ * which can be used to perform actions on the peers in the peergroup.
+ * Also, the GNUNET_TESTING_daemons_stop call would need to be removed,
+ * and only called once all of the testing is complete.
+ */
+
+ /**
+ * struct TestcaseData *state_closure;
+ * GNUNET_SCHEDULER_add_now(&additional_code_for_testing, state_closure);
+ */
+
GNUNET_TESTING_daemons_stop (pg, TIMEOUT, &shutdown_callback, NULL);
}
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] r14912 - gnunet/src/testing,
gnunet <=