You can ensure that your testing effort adequately covers
the necessary requirements by linking requirement collections to your
test plans. Later, you can assign each requirement to a test case
and link to the test case from the test plan to ensure that the requirements
have complete testing coverage.
About this task
You must configure the integration between the test project
area and the requirements project area before you can create the link
to the requirements collection. See
Running the setup wizard for details.
Limitation: When you
create a link to external artifacts in a CLM workbench source application,
a link is automatically created back to the source artifact in the
target application, which is called a back link. However, a state
of synchronization between bidirectional links and the traceability
between source and target artifacts are not guaranteed.
When a source artifact and target artifact
link to each other, this is known as bidirectional linking. The source
and target applications store their links in separate databases, and
the source application does not have access to the database in the
target application. Certain transactional operations, such as when
artifacts are copied or deleted, can occur in the source application
server. In these cases, corresponding back links in artifacts in the
target application are not automatically added or removed. There can
also be instances where back links are intentionally removed in the
target application without removing the corresponding link in the
source application. As a result, if bidirectional links are not in
a state of synchronization, traceability between the source and target
artifacts can appear differently based upon your starting view point.