Forum Discussion
jimsmith_1
13 years agoContributor
I notice that I am running my project in legacy mode. That means I still need LCIE disabled, I think.
However, I'm concerned about continuing to use legacy mode. It sounds like the sort of feature that might be dropped one day.
Is there any way I can convert my existing process object based name mapping to the new browser object based name mapping? If I can't convert, how do I run (and update) my old tests in legacy mode while creating new ones in non-legacy mode? Or am I stuck with legacy mode for ever?
If I have a test suite containing some legacy name mapping based tests and some non-legacy name mapping based tests is there a way to dynamically switch legacy mode on and off during the test run? Or does TestComplete, knowing that both types of name mapping may co-exist, search for web objects in process based and browser based nodes?
Thanks, Jim
However, I'm concerned about continuing to use legacy mode. It sounds like the sort of feature that might be dropped one day.
Is there any way I can convert my existing process object based name mapping to the new browser object based name mapping? If I can't convert, how do I run (and update) my old tests in legacy mode while creating new ones in non-legacy mode? Or am I stuck with legacy mode for ever?
If I have a test suite containing some legacy name mapping based tests and some non-legacy name mapping based tests is there a way to dynamically switch legacy mode on and off during the test run? Or does TestComplete, knowing that both types of name mapping may co-exist, search for web objects in process based and browser based nodes?
Thanks, Jim