Shared between all test types. Currituck subsystem something ... Describes the test. This is shown in the properties window. At the moment only one owner is allowed, but in the future we might extend to multiple owner support. For example REDMOND\user1 Files to deploy before executing this test. Categories applied to the test References to workitems (bugs, issues) related to this test on the team server. Coded web test in TRX file Declarative web test in TRX file This is in addition to the timeout to distinguish between a failed command and a test that timed out. If this element does not exist it's the same as if it was not enabled. But if it's not enabled, we still allow the user to change the file location and persist the file location for later use. TODO: leave up to NC: this type is a duplicate of LoadTestRunCOnfigurationType. The differentces are results of WebTestSuiteSerializer (upper case for attributes and enums are strings vs ints) This one can be used by any other test type as they all can internally call another set of tests and produce results, which are later merged into this aggregation for unified presentation to the caller. Only one instance is allowed but no check is done due to xsd limitations. Only one instance is allowed but no check is done due to xsd limitations. New in Orcas Only one instance is allowed but no check is done due to xsd limitations. Only one instance is allowed but no check is done due to xsd limitations. Deprecated. Use WebTestRunConfiguration instead. // Deprecated. Use UnitTest instead Only one instance is allowed but no check is done due to xsd limitations. Only one instance is allowed but no check is done due to xsd limitations. New in Orcas Only one instance is allowed but no check is done due to xsd limitations. Only one instance is allowed but no check is done due to xsd limitations. Deprecated. Use WebTestRunConfiguration instead. Only one instance is allowed but no check is done due to xsd limitations.