Forum Discussion

JeffSm's avatar
JeffSm
Contributor
14 years ago

TestExecute in some Asian Windows XP not working

Running script with TestExecute (8.0.290.11) in Korean, Simplified Chinese or Traditional Chinese Windows XP SP3 is not working. The script starts, but can't find anything (nothing but "object does not exist" messages in the script log). This same setup works fine in Win7. If I install TestComplete (8.0.290.7) on a Korean Win XP SP3 PC, and run the exact same script, it works fine. Any ideas what the problem might be?

4 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    Question:



    The TestExecute box, are you running it overnight or through and RDP to remote machine?  The reason I ask is that windows lockouts, RDP "This machine is locked" and other similar things could be preventing the scripts from running.  Have you tried manually triggering the TestExecute task while you sit and "watch the paint dry"?



    Other question:  The current version of TestComplete/TestExecute is 8.50.  Have you tried an upgrade to see if that corrects the problem?
  • Hi Robert,



    Thanks for the quick reply. I am running TE directly on the Korean XP PC. When I've run TE remotely, I frequently see unexplained script errors and it runs really slow, so I've pretty much given up on running my scripts remotely. As I said, I installed TestComplete, and ran my script and it worked perfectly. I'm also doing exactly the same thing on several of the Scandinavian language XP environments, with no issues. I'm only seeing this on XP for Korean, Simplified Chinese and Traditional Chinese. Win 7 32/64-bit environments work perfectly.



    As to upgrading, I'm currently stuck using 8.0. I work in a medical software environment, and we have to validate TestComplete (and TestExecute) for it's "intended use". I have done this for 8.0, but not 8.5. It's pretty involved, so I can't really do this in the middle of my testing cycle.



    I just downloaded TE 8.5 to try it. It worked.



    Thanks,

    Jeff
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    I work in the pharma industry myself... I feel your pain.  We haven't officially rolled out TC for use in our formal testing processes because it has not been validated yet (on the schedule to do so).



    So... it looks like, then, TC 8.5 fixes the problem... I seem to have remembered such was the case with the early version of TC 8.