Forum Discussion
AlexKaras
10 years agoChampion Level 3
Hi Minh,
a) Obsolete methods exist in TestComplete for years, so I don't consider this as a real risk;
b) Why not to call ScriptB.FindMyProcessdirectly? I.e.:
eval('var x=1;ScriptB.FindMyProcess;ShowMessage(x+5);');
P.S. I would be second to Phil that it is extremely difficult to figure-out what went wrong if some problem occurs in the code called via eval(). Such code is not shown in the call stack and the error will be reported by TestComplete as occurred on the eval() line of code (unless you implement your own error handling in the code called using eval(). So you will have to either add additional logging to help you to diagnose where the problem occurred or to guess where to put the debug breakpoint.
a) Obsolete methods exist in TestComplete for years, so I don't consider this as a real risk;
b) Why not to call ScriptB.FindMyProcessdirectly? I.e.:
eval('var x=1;ScriptB.FindMyProcess;ShowMessage(x+5);');
P.S. I would be second to Phil that it is extremely difficult to figure-out what went wrong if some problem occurs in the code called via eval(). Such code is not shown in the call stack and the error will be reported by TestComplete as occurred on the eval() line of code (unless you implement your own error handling in the code called using eval(). So you will have to either add additional logging to help you to diagnose where the problem occurred or to guess where to put the debug breakpoint.
Related Content
Recent Discussions
- 2 days agoMW_Didata