At what levels can a Test Configuration Parameter (TCP) be defined?

• A. TestCases
• B. TestCase Folders
• C. ExecutionLists
• D. All of the above

Answer: (D)

Test Configuration Parameters are values used to customize how tests run, and you can apply them at different scopes to fit the level of control you need. Defining a TCP on an individual test case lets that test run with a specific setting. Placing a TCP on a TestCaseFolder allows you to enforce the same parameter across all test cases inside that folder, ensuring consistency for related tests. You can also define TCPs within ExecutionLists, which control how the tests are executed—affecting which test cases run, in what order, and with what data or environment assumptions.

Because you can set these parameters at all three levels, TCPs are supported across TestCases, TestCaseFolders, and ExecutionLists. This flexibility is what makes the best choice “All of the above.” Keep in mind that when the same parameter exists at multiple levels, the more specific scope (closer to the execution) typically takes precedence, allowing overrides where needed.