Forum Discussion

m_essaid's avatar
m_essaid
Valued Contributor
9 years ago
Solved

another name mapping issue (alt-O shortcut)

Hi,   Maybe Colin could advise me, it's I bet a Delphi issue,   I have 2 project with shared scripts, and shared name mapping (one projects tests a beta version, the other the alpha version of th...
  • NisHera's avatar
    NisHera
    9 years ago

    I have shared namemapping for several projects testing Delphi applications.

    on and off encountered with same problem but found it's refering to two namemapping files.

     

    in your case it could be either mapping propertied are different in alpha and beta or two files are used. 

    also check TestedApps are correct in two projects (upper and lower cases)

     

    please go through name mappings in two projects carefully(in TC).

    and go through file structure (in windows explore) and see whether there are two mapping files.

    if you see two files, re-name which you think not the original and see.

     

NisHera's avatar
NisHera
Valued Contributor

I have shared namemapping for several projects testing Delphi applications.

on and off encountered with same problem but found it's refering to two namemapping files.

 

in your case it could be either mapping propertied are different in alpha and beta or two files are used. 

also check TestedApps are correct in two projects (upper and lower cases)

 

please go through name mappings in two projects carefully(in TC).

and go through file structure (in windows explore) and see whether there are two mapping files.

if you see two files, re-name which you think not the original and see.

 

m_essaid's avatar
m_essaid
Valued Contributor
9 years ago

Hi guys,

 

very very interesting !

 

I was using a different name for the tested apps (for example, "MyAppALPHA" was pointing MyApp.exe and "MyAppBETA" was pointing another MyApp.exe). I named the two TestedApp that were in two different project the same and it works... So thank you very much :)

 

I faced another problem in relation and I want to report it, it might interest someone :

 

As the support team told me, the problem could also came from another thing (in addition to the tested apps naming) : the use of the MSAA Open Application. So I need to put off the wildcard "*" in the list of accepted windows.

So the problem moved to this one : a popup menu that where accessible with this wildcard "*" in MSAA where no longer visible in playback... When I tried to use the object spy it showed a non managed windows class code : #32768.

 

To resolve it I just had to redo the mapping without msaa wildcard checked.