The answer of the question is that test coverage can be used in any level of the testing. Test coverage can be measured based on a number of different structural elements in a system or component. 

Coverage can be measured at component testing level, integration-testing level or at system- or acceptance-testing levels. For example, at system or acceptance level, the coverage items may be requirements, menu options, screens, or typical business transactions. At integration level, we could measure coverage of interfaces or specific interactions that have been tested.

We can also measure coverage for each of the specification-based techniques or black-box testing:

• Equivalence partitioning: percentage of equivalence partitions exercised (we could measure valid and invalid partition coverage separately if this makes sense);
• Boundary Value Analysis: percentage of boundaries exercised (we could also separate valid and invalid boundaries if we wished);
• Decision tables: percentage of business rules or decision table columns tested;
• State transition testing: there are a number of possible coverage measures:

— Percentage of states visited
— Percentage of (valid) transitions exercised (this is known as Chow’s 0- switch coverage)
— Percentage of pairs of valid transitions exercised (‘transition pairs’ or
Chow’s 1-switch coverage) – and longer series of transitions, such as transition triples, quadruples, etc.
— Percentage of invalid transitions exercised (from the state table).

The coverage measures for specification-based techniques would apply at whichever test level the technique has been used (e.g. system or component level).

Other popular articles:

• What are the types of coverage?
• What is test coverage in software testing? It’s advantages and disadvantages
• What is State transition testing in software testing?
• What is black-box, Specification-based, also known as behavioral testing techniques?
• What is Coverage measurement tools in software testing?