Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
dick1 Absent Member.
Absent Member.
3615 views

Performance issue between tests

Jump to solution

Hello,

I'm usually using visual tests as driver scripts which call other visual tests and .net scripts in SilkTest Workbench 13 (Hotfix1).

SilkTest runs those tests pretty fast besides between two scripts or visual tests. Many seconds pass without action after one script finished and the next one is to be executed. Might it be that SilkTest is compiling the scripts at runtime one by one? Is there a possibility to speed up the whole thing?

Regards

Peter ***

0 Likes
1 Solution

Accepted Solutions
JohnLy Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi All

I wanted to provide an update on the outcome of support incident

The performance differences between running a “Visual Test which called a child Visual Test” and a “Visual Test which called a VB.NET script) was caused by the fact that every time a child VB.NET script is ran from a  Visual Test it is loaded from the database and then compiled.

With the release of SilkTest 13.5  (which is due in the next few weeks); the SilkTest Workbench will now only load the VB.NET script once per session – internal tests and tests by the customer has resulted in significant improvement in the execution times; especially if the database in question is under load.

Additionally a change request has been logged for SilkTest to compile the VB.NET scripts only once per playback session, the official RPI number is: 1085827 and this will be implemented in future versions of the SilkTest Workbench.

Thanks

John

0 Likes
6 Replies
Wolfgang G_ Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi Peter,

a possible cause of performance delays might be caused by the database you use for your Workbench. Depending on how you use Workbench the database grows in size by time and this can of course impact the overall performance.

So make sure that you do some database maintenance regularly and/or configure Workbench to generate less amout of data (like enumerations/screenshotting). The purge tool shipped with ST can assist you with database maintenance. If you need more you'd better raise a support ticket.

Cheers

0 Likes
dick1 Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi Grueli,

Thanks for your hints. In the maintenance application i could not find anything useful that might make the database work faster. The integrity check fixed 5 assets. Additionally i used the purge assistent to remove assets (keep only last 5) and the assistent removed over 6000 assets. But it doesn't seem to improve the delays between the scripts.

I guess i will have to raise an incident then.

Regards

0 Likes
HGrube Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi Grueli,

we started some "benchmark"-tests testing how long calls from one Visual Test to Test Scripts or Visual Test last.

We found out that a call of a Visual Test needs about one second to execute the called Visual Test and 6 (!) seconds to call an Test Script.

That is an awful difference. We use Visual Test driver scripts and some functionality which is not yet implemented in the Test Scripts. But need some Test Script calls for special functionality (system tasks, .NET calls etc.). So we have several calls.

The scripts (themselves) are working very fast but not the TS calls (they are wasting about 60-80% of the runtime of our Testcases).

Is there any posibility to reduce the delay? Is there an architectural problem?

Kind regards

Holger

 

 

0 Likes
Wolfgang G_ Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi Holger,

meanwhile this has been raised by Peter as a support incident. As a result of our investigations we were already able to improve performance significantly here. The improvement will be available with our next release.

Cheers

0 Likes
Highlighted
HGrube Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Yes, the TS calls are now 2 times faster than before. ;-)

Thanks.

Holger

0 Likes
JohnLy Absent Member.
Absent Member.

RE: Performance issue between tests

Jump to solution

Hi All

I wanted to provide an update on the outcome of support incident

The performance differences between running a “Visual Test which called a child Visual Test” and a “Visual Test which called a VB.NET script) was caused by the fact that every time a child VB.NET script is ran from a  Visual Test it is loaded from the database and then compiled.

With the release of SilkTest 13.5  (which is due in the next few weeks); the SilkTest Workbench will now only load the VB.NET script once per session – internal tests and tests by the customer has resulted in significant improvement in the execution times; especially if the database in question is under load.

Additionally a change request has been logged for SilkTest to compile the VB.NET scripts only once per playback session, the official RPI number is: 1085827 and this will be implemented in future versions of the SilkTest Workbench.

Thanks

John

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.