Forum Discussion

ssv's avatar
ssv
Occasional Contributor
6 years ago
Solved

Test Complete Object Mapping different with different executions

I have a weird problem, where the object i am trying to access changes between the following two.   I have sys.process("msiexec") and sys.process("msiexec", 2), which heaviliy interchanges, when i ...
  • tristaanogre's avatar
    tristaanogre
    6 years ago

    This is a common problem.  The problem can be summed up as such:

     

    You cannot check the value of the "Exists" property of an object if it doesn't exist.  If you think about it, it makes sense... how can you check ANY property of a non-existant object?

     

    For your situation, I'd look into using "WaitChild" for your check for existance. (https://support.smartbear.com/testcomplete/docs/reference/test-objects/members/common-for-all/waitchild-method.html)

     

    Also, review this topic as it covers this problem in more general terms.

    https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/checking-existence.html

  • liquidphantom's avatar
    liquidphantom
    6 years ago

    You'll need to use an If Not for the first statement

     

    i.e.

    If Not Sys.Process("msiexec", 2).Form("product*").Exists Then
      Set qvProcess = Sys.Process("msiexec").Form("product*")
ElseIf Sys.Process("msiexec", 2).Form("product*").Exists Then
      Set qvProcess = Sys.Process("msiexec", 2).Form("product*")
    End If

     

    Might have to tweak it a little but the If Not is important so it doesn't get caught in the error.

AlexKaras's avatar
AlexKaras
Champion Level 3
6 years ago

Hi,

 

Can you describe your use case with more details? msiexec is Windows installer process and indeed there are 2+ msiexec processes in the system when some piece of software is been installed.

The actual concern is: do you *really* need to interact with the installer's UI? Is it your actual task to go through the UI while installing the software? If you need just to install the software, this can be done unattended from the command line and without the necessity to interact with installer's UI. (And the latter is the recommended and more preferable approach when you do not do verification of the installer's UI.)

  • ssv's avatar
    ssv
    Occasional Contributor
    6 years ago

    Hi Alex,

     

    Sorry for the very late reply. Have been busy with a lot of stuffs lately.

     

    so answering your questions, yes i need to interact with the installer's UI. There are settings on installer UI that I particularly need to automate. 

     

    We already have a base version, say version v1, which is installed through the command line parameters. And then we try to install the latest version say, version v2. 

     

    This needs to automated, mainly because we want to automate the way the normal user would do.