Test duration

Individual tests can take around three minutes to run. The following conditions affect the length of time to run the tests:

• Cluster complexity

  Testing in complex environments takes considerably longer.

• Latency on the network

  Cluster testing relies on network communication between the nodes. Any degradation in network performance slows the performance of the Cluster Test Tool.

• Use of verbose logging for the tool

  If you customize verbose logging to run additional commands from which to capture output, testing takes longer to complete. In general, the more commands you add for verbose logging, the longer a test procedure takes to complete.

• Manual intervention on the control node

  At some points in the test, you may need to intervene. See Recovering the control node after cluster manager stops for ways to avoid this situation.

• Running custom tests

  If you run a custom test plan, the number of tests run also affects the time required to run the test procedure. If you run a long list of tests, or if any of the tests require a substantial amount of time to complete, then the time to process the test plan increases.