Forum Discussion

tvklovesu's avatar
tvklovesu
Frequent Contributor
3 years ago

Warning messages in the test run log for improve performance

Hello,

Recently I have updated all my nameMapping to use unique identifiers in the XPath and deleted all others that TC saved when recorded. So tipically I have only one selector for each object or element. When I ran the test it gave me the following warning almost for all the objects. 

 

You can improve the performance of the object search in the test.

The NameMapping.​Sys.​browser.​pageAuth.​login_SignIn_Btn object

can be found faster if you make //input[@type="submit"] the first selector in its selector list.

 

And in the nameMapping for this object I see only one selector as I mentioned above. Still not sure why its throwing warning messages. Even when I click on Improve performance button in the log it just added an Empty selector, and even with that when I rerun the test it gave same message. One another thing is that the Extended Find column doesn't have any checkboxes.

 

Is there something I missed in the settings or somewhere else

 

TIA

3 Replies

  • Hello sasarode123 

     

    I have never had good outcomes by following documentation to add external jar files to:

      {smartbear install location}/bin/ext folder

     

    As long as there are no conflicting jar versions, I just go straight to including external jar files to:

      {smartbear install location}/lib folder

     

    If you only have a few (1 to 15 maybe) external jar files, this should not be a problem.  It gets a lot riskier (meaning, you have the potential to no longer make the application operate) if you have a lot of external jar files or conflicts with existing jar files.  You might have to trial and error a little bit however.  I use the date/time stamp as a quide to see what external jar files I might have added because those are usually different than the similarly dated files for the original install.  If you make the application (ReadyAPI or TestEngine) no longer operate, then remove the jars you added to /lib folder.  I have used that folder for years with success.

     

    Regards,

    Todd