Hi,
The way QC is structured at my workplace is that there is one central project
that QA logs into. Within this project, there are subject folders for each project release. So we have something like
v10
v11
v12
Each of these project release folders has a library of called tests in a folder called Shared Library.
Within each main project release version, we have maintenance releases so we could
have under the v11 folder:
V11MR1
V11MR2
V11MR3
When a new maintenance release is created, the Shared Library and current set of test scripts are copied from the previous maintenance release to the new one. So for instance, the V11MR2 contents would be copied to the V11MR3 folder. When the test scripts are copied at the same time as the Shared Library of called tests, QC seems to know to use the relative path of the Shared Library so that a test script in the V11MR3 folder will know to look for the called test in the Shared Library of the V11MR3 folder.
However, the problem arises when there is a project release in between V11MR2 and V11MR3, say V11MR2.1, and a new test script is created and includes calls to tests in the Shared Library. When this test script is subsequently copied to the V11MR3 folder, the called tests are no longer relative in this test script as they still point back to the V11MR2.1 called test Shared Library instead of the V11MR3 Shared Library which could have changes made to it's called tests based on new development.
So it seems that QC only knows to use the relative path if the test script and Shared Library are copied at the same time. If they are not, it seems to be using the absolute path which is obviously not desired.
Is there any way to get around this issue?
Thanks!
Chris