Difference between revisions of "Supporting Node"
(→See Also) |
|||
| Line 1: | Line 1: | ||
| + | [[Image:tunit_nodes.jpg|frame|Supporting nodes typically sit nearby, aiding in producing test results.]] | ||
| + | |||
A Supporting Node is any node in a test run that is not the [[Driving Node]]. These nodes are only allowed to run the optional '''SetUpOneTime.run()''' and '''TearDownOneTime.run()''' interfaces, which are typically responsible for turning the radio on before the test begins, and turning the radio off when the test is complete to avoid interference with future tests. | A Supporting Node is any node in a test run that is not the [[Driving Node]]. These nodes are only allowed to run the optional '''SetUpOneTime.run()''' and '''TearDownOneTime.run()''' interfaces, which are typically responsible for turning the radio on before the test begins, and turning the radio off when the test is complete to avoid interference with future tests. | ||
Although the Driving Node is the only node that gets the command to run() a test, Supporting Nodes may make assertions, supply statistics, and end tests by calling done() on the current test that is being executed. | Although the Driving Node is the only node that gets the command to run() a test, Supporting Nodes may make assertions, supply statistics, and end tests by calling done() on the current test that is being executed. | ||
| + | |||
| + | To prevent RF and physical issues from interfering with software tests, Supporting Nodes are always placed withing RF vicinity of each other when performing unit tests. Although there are many cases where a Supporting Node makes sense for a test, these nodes are typically used for radio integration and stack performance testing. | ||
== See Also == | == See Also == | ||
* [[Driving Node]] | * [[Driving Node]] | ||
Revision as of 09:40, 10 January 2008
A Supporting Node is any node in a test run that is not the Driving Node. These nodes are only allowed to run the optional SetUpOneTime.run() and TearDownOneTime.run() interfaces, which are typically responsible for turning the radio on before the test begins, and turning the radio off when the test is complete to avoid interference with future tests.
Although the Driving Node is the only node that gets the command to run() a test, Supporting Nodes may make assertions, supply statistics, and end tests by calling done() on the current test that is being executed.
To prevent RF and physical issues from interfering with software tests, Supporting Nodes are always placed withing RF vicinity of each other when performing unit tests. Although there are many cases where a Supporting Node makes sense for a test, these nodes are typically used for radio integration and stack performance testing.
