Which statement is true about TCPs across levels?

• A. TCP can only be defined at one level
• B. TCP can be defined at multiple levels with precedence rules
• C. TCPs at higher levels override lower levels by default
• D. TCPs cannot coexist across levels

Answer: (B)

TCPs across levels are designed to be defined and reused at different levels, with precedence rules to resolve conflicts. This means you can create a Test Case Pattern at a general level and also tailor or extend patterns at more specific levels. When a test case uses a TCP that exists at multiple levels, the system applies the definition from the most specific level (the one closest to the test context), using the precedence rules to decide which version takes effect. This setup lets you customize behavior for particular areas while keeping a common foundation in higher levels, rather than being limited to a single level or being unable to coexist. For example, a generic login TCP at the global level can be specialized at a module level to add extra steps, and the module-level TCP will apply in that module while the global TCP remains for other parts of the project. The other options don’t fit because TCPs aren’t restricted to one level, they can coexist across levels, and there is a defined precedence mechanism rather than an automatic override by higher levels.