|How to make sure "Move to External Project" does not break Test Cases? [message #1066664]
||Wed, 03 July 2013 11:29
| Eric Schellhammer
Registered: July 2013
the refactoring "Move to External Project" is prone to break test cases without issuing a warning.
Even in those cases where the situation can be fixed later, this may lead to loss of Data Sets.
E.g. consider three projects A, B and C where A uses both B and C, but the latter two are unrelated.
Have a test case a in project A reference a test case b of project B.
After moving the test case a to project C, which is possible without warning, it cannot find test case b any more and at this point all Data Sets of this call are lost.
Is there an easy way to check for such references in a significantly more complex setting of interrelated projects?
Powered by FUDForum
. Page generated in 0.01735 seconds