Forum Discussion

lmorawski's avatar
15 years ago

Objects.Save - very slow with .Net apps

I posted this message on QAForums (http://www.sqaforums.com/showflat.php?Cat=0&Number=619266&an=0&page=1#Post619266) but didn't get any response so I post it also here:



I need to save
state of objects of my tested application. So I decided to use
Objects.Save(), but I found it useless due to performance issues. It
takes 30 (thirty) minutes to save my tested application objects tree. I
must say that there is about 30 objects in my tested app, so I think
it's very slow. Application is written i C#.

I decided to check this method on Test Complete "Orders" sample.

Command
"Objects.Save(Sys.Process("Orders"), "Orders", "", "", true)" took 3
minutes to complete. I used the same command for my tested app.



Yes, I understand that I use recursive search in child objects.



I
know that there is an alternative way with
"aqObject.SaveObjectSnapshotToFile()", but it's not a cheetah neither.
It took 10 minutes for my application and 25 seconds for "Orders
sample". I used:
"aqObject.SaveObjectSnapshotToFile(Sys.Process("Orders"),
"c:\\orders.txt", true, false, "", false, false)".



Is there any way to improve performance of Objects.Save() and aqObject.SaveObjectSnapshotToFile() ?

Maybe there is a "magic option" in Test Complete to do this ?



As I said, my tested application in written i .Net.



I
also noticed that Objects.Save() does strange things with popups. I
mean that I got a lot of "Cannot obtain pop up menu" errors in test log
with remarks "Possible reason: There was no click that invokes the
popup menu.".