Eclipse Community Forums: Jubula » How to make sure "Move to External Project" does not break Test Cases?

Home » Archived » Jubula » How to make sure "Move to External Project" does not break Test Cases?

How to make sure "Move to External Project" does not break Test Cases? [message #1066664]

Wed, 03 July 2013 11:29

Eclipse User

Hi,

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?

Thanks,
ERIC

Re: How to make sure "Move to External Project" does not break Test Cases? [message #1067265 is a reply to message #1066664]

Mon, 08 July 2013 03:18

Eclipse User

Hi,

Cross-link: As mentioned in this message, there is no current way of doing this.

Best regards,
Alex

Re: How to make sure "Move to External Project" does not break Test Cases? [message #1067531 is a reply to message #1067265]

Tue, 09 July 2013 04:57

Eclipse User

Hi,

thanks for cross-linking; I wasn't sure if the refactoring query is actually technically based on the Search scope, so I decided to put it in two separate posts.

Best regards,
ERIC

Previous Topic:	Date Widget and others not supported as GRC?
Next Topic:	Close tab with the new release

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 02:26:17 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter