Forum Discussion

EkremMese1's avatar
EkremMese1
Contributor
2 years ago
Solved

Performance Comparison NameMapping vs FindElement

Hello everyone,  I have came across with a Test Case where I locate the WebElement with 2 different ways.  One is with NameMapping:  OCR.Recognize(NameMapping.Sys.browser.pagePersonCreate...
  • AlexKaras's avatar
    AlexKaras
    2 years ago

    Hi,

     

    EkremMese1 wrote:

    I am curious about the opinions and experiences of yourself

    Generally speaking, properly crafted Aliases (that must be used instead of NameMapping) are way more preferable and flexible approach in TestComplete world. The only exception is when one needs to create web tests that must be executed on web farm like BitBar.

    But in real life, ineffective NameMapping (for example, that heavily relies on Extended Find which is turned on by default) may result in worse performance when compared to XPath.

     

AlexKaras's avatar
AlexKaras
Icon for Champion Level 1 rankChampion Level 1
2 years ago

Hi,

 

EkremMese1 wrote:

I am curious about the opinions and experiences of yourself

Generally speaking, properly crafted Aliases (that must be used instead of NameMapping) are way more preferable and flexible approach in TestComplete world. The only exception is when one needs to create web tests that must be executed on web farm like BitBar.

But in real life, ineffective NameMapping (for example, that heavily relies on Extended Find which is turned on by default) may result in worse performance when compared to XPath.

 

EkremMese1's avatar
EkremMese1
Contributor
2 years ago

Do you think using NameMapping.... for the WebElements instead of Aliases slows down the testing? 
Because Aliases is more complicated for me, than NameMapping...