I have an XML file that is executing a Change Password scenario in an application. User has to navigate 4 screens in order to reach the Change Password screen.
1. Screen 1 (Home Page) Contains approximately 20 objects
2. Screen 2 (Login Page) Contains approximately 40 objects
3. Screen 3 Contains approximately 154 objects
4. Screen 4 Contains approximately 70 objects
5. Change Password Page Contains approximately 100 objects.
I am using SilkTest to dynamically read from the XML & execute the scenario of changing the password. I am not using the standard approach of recording the window declarations and then writing the test cases.
I am recognizing the required objects at run-time using GetChildren() function. Since GetChildren function captures all the objects on the page, it takes considerably long time in order to locate the required object on the page. Each of the pages has many html objects & they are embedded within htmlforms or htmltables. Hence the performance is getting hit.
Please suggest a better way by which the performance may be improved.
Thats odd. Using GetChildren is much faster for me than using other approaches (namely making separate DOM queries for each item you seek.) Are you having to call GetChildren recursively or has silktest flattened your DOM?
Chris R Mead
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
You can instruct to Silktest, don't take invisible objects and some marquee objects.
If you are using silktest version6.0 and above, Please have a look on Help tophic: HtmlText class: new layer recorded
Why is a new layer of HtmlText being recorded by SilkTest 6.0?
Some recognition seems to be slightly different with SilkTest 6.x compared to previous SilkTest versions when recording against Internet Explorer using the DOM extension. Some HtmlText objects have children, for example:
.../[HtmlText]AliasDoing Business AsLegalPrimary/[HtmlPopupList]#1
Elements with overflow style are now being recognized in SilkTest 6.x. This may cause a backward compatibility issue with scripts recorded against previous releases. A new SilkTest option for elements with overflow style has been added to SilkTest 6.x.
The default for this option is TRUE. If you want to ignore these elements, you need to set the option "ShowOverflow" to FALSE in the "domex.ini" file stored in the folder ..\SilkTest\Extend.