Difference between revisions of "Driving Node"
(Creation) |
(→See Also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
The Driving Node is always the first node defined in a [[Test Run]] in the [[tunit.xml]] file. Any other node taking place in a test run is known as a [[Supporting Node]]. | The Driving Node is always the first node defined in a [[Test Run]] in the [[tunit.xml]] file. Any other node taking place in a test run is known as a [[Supporting Node]]. | ||
| + | |||
| + | = See Also = | ||
| + | |||
| + | * [[Supporting Node]] | ||
| + | * [[TUnit Test Flow]] | ||
| + | * [[tunit.xml]] | ||
Latest revision as of 08:42, 10 January 2008
The Driving Node is the node that is responsible for running the test.
A Driving Node is the node that gets the command to run() each test. It is notified by the computer to begin testing.
The Driving Node is always ID 0, and is the only node that executes SetUp.run(), TestCase.run(), and TearDown.run().
The Driving Node is always the first node defined in a Test Run in the tunit.xml file. Any other node taking place in a test run is known as a Supporting Node.
