Forum Discussion

pkroon's avatar
pkroon
Occasional Contributor
14 years ago

IEXPLORE Alias Name Mapping Issues

In migrating to a new server, we have found issues with how Internet Explorer is named in TC.  While recording test cases, it appeared as Aliases.IEXPLORE4 most of the time (although we found some with different numbers at the end even before the migration).  After moving to a new server, however, TC appears to now see IE as Aliases.IEXPLORE2.  Because of this, none of the keyword tests work properly.  We could go through each step of every case, but that can't be the only way around this, especially since it appears as though this value could change again in the future.



Is there any way to set up this alias with a wildcard so that the test case will run correctly no matter what the object is for that step (Aliases.IEXPLORE*, for example)?  Is there any better way to fix this?  Also, is there any setting to help ensure IE doesn't keep changing its name on us?  We have applied the TabProcGrowth registry fix, but this doesn't seem to make a difference.
  • YMinaev's avatar
    YMinaev
    Staff
    14 years ago
    Hi,



    There's no way to use wildcards in alias names, but you can prevent this from happening. Most probably, the IE process is mapped by index which changes its value. Open IE in aliases, remove the Index property from its recognition parameters (actually, the only needed property here is ProcessName) and specify the page you're working with as a required child. This will make TC always address the IE instance in which this page is loaded ignoring other ones. See the Specifying Child Objects Required for Mapped Object Identification help topic for details.