Forum Discussion

ThomasK's avatar
ThomasK
New Contributor
5 years ago
Solved

Self-healing on item or version number

Hi,   I am using TestComplete to automate tests in a home-made desktop application. But I have a problem that occurs in every Keywordtest I run.   Some objects on my application seems to change o...
self-healing
  • mbeckham's avatar
    mbeckham
    4 years ago

    Hi Everyone,

    Alex, you've stolen my thunder 🙂   I was just about to report our success with tscon.  We ran the command manually on the RDP machine which 'shut' it down while the Agent was 'listening' for work.  Our next step will be to create the batch file to run the tscon command and include it in the nightly pipeline.

    So, to run this command (as Alex says, run as an administrator )  within the RDP window, from the Command Line. 

    >query user          (this will return the sessionname eg rdp-tcp#xx)

    >tscon.exe  rdp-tcp#xx  /dest:console

    respond "yes" to to close your session

    ...all done

     

ThomasK's avatar
ThomasK
New Contributor
5 years ago
Copy LinkReport

Hello,

 

Thank you for your kind response.

 

I can't see how to implement your solution:

1. With keywordtests, I can't find something like this Client [QA] (5.9.0.20200707-1112-b697) - CAT (5.9.0.6cbbca7) QAC-200707-0053 - Inspection* - Chief F. (CAE1). My view is this one and I don't see where wildcards can be used without converting to Script.

2. I have about 100 to 200 steps for one test, and I expect 500 testcases in the future. Assuming that I have the warning one step out of 5 on average, added to the maintenance work, it's a huge labor to achieve this whenever the problem occurs.

 

Do you have another idea? Or I don't understand?

 

Thanks!

Marsha_R's avatar
Marsha_R
Icon for Champion Level 3 rankChampion Level 3
5 years ago
Copy LinkReport

1) Use the wildcards in your name mapping.  That will let all the similar objects be found in one place in the mapping.

2) If the app changes, the test has to change.  In this case we can probably help you fix it easily.  In other cases it might not be so easy.  You might want to look over your tests and see if you can parameterize them or break them into smaller modules to keep those large numbers of tests and steps from biting you in the future.