Contributions
Re: At What Frequency Does WaitProperty Checks For Property
What you're saying makes sense, but thing is my code is still working. It does actually wait until my window exists and once it exists, it goes through the code (or of course, until it times out). I guess I could do as below, and check if the performance is different, but I highly doubt it will change something, since it seems to be doing the same work behind the scenes (I might be completely wrong) var ResultsDialog = Aliases.Sys.TxpApplication; ResultsDialog.WaitAliasChild("TCCHPDFCreatedList", DefaultTimeout); if (!ResultsDialog.TCCHPDFCreatedList.Exists) { Log.Error("Results dialog is not visible after timeout"); } // Continue2.4KViews0likes1CommentRe: At What Frequency Does WaitProperty Checks For Property
The object was mapped before hand, so I'm assuming that it knows of it. By waiting for exists, I know that once it's property is set to true, it will be visible. You may ask why not check for visible, and it is because it fails, since the object does not exists and thus, does not contain a proprerty visible yet. For you answer about the frequency, I assumed it was quick, but that is the problem. This operation takes around 1 to 2 hours. Imagine querying that property, let's say, 3 times per second. That will surely slow down the whole system, and thus, explain why my results are over what I obtain in manual testing. Edit: about WaitChild and others, will it do the same as WaitProperty but for an object ? By reading the documentation, I have a feeling that yes it does, therefore, my question still applies; at what frequency and how do I change it ? Thanks for showing interest in my question!2.5KViews0likes4CommentsAt What Frequency Does WaitProperty Checks For Property
I'm currently doing performance tests on a desktop application and I realised that times are not the same when I do the test manually versus when I use TestComplete. Let's say I'm looking at the time it takes to send results to server after clicking a button. What I do in my code is once the button to trigger the operation is clicked, wait for the result window to appear in order to stop the stopwatch. I'm getting higher execution time with Test Complete than manually testing (I record the screen, capture the time where I click the button and the time where the window appears to be as precise as possible). Note that the difference of time is significant; around 30 to 40% depending on the amount of data transfered. var ResultsDialog = Aliases.Sys.TxpApplication.TCCHPDFCreatedList; ResultsDialog.WaitProperty("Exists", true, 100000); if (!ResultsDialog.Exists) { Log.Error("Results dialog is not visible after timeout"); } ResultsDialog.ButtonPanel.ButtonCancel.Click(); My question is how often does Test Complete tries to check the "exists" property ? I have a feeling that it does it at a high frequency, which results in the environnement being overcharged and thus performing it's current operation slowly. I read the documentation, with no succes, I couldn't not find a parameter to set a frequency. I know I could use a loop and add manual delay to it, but I would like to avoid that. Thanks!Solved2.5KViews0likes8CommentsRe: Focus on window not visible on screen
The window is not visible and not accessible even by hand. It is some sort of weird bug, where the buffer of the number of form object in the application is capped and the window that I use to navigate is not accessible anymore. The solution would be to change it's z index in order to be higher than the actual application, and thus, it would be visible. It's quite hard to explain, I am probably doing it wrong, but hear this example. Open up Excel, and then go to File -> Open -> Browse. A dialog will pop out, prompting you to choose a file to open. If you go into the opened applications icon in your taskbar, you can see Excel Icon. Hover your mouse on it and you should see a preview of Excel (not the Open file window). That is the correct behaviour. In my case, our application has the contrary effect. We do not see the dialog once we try to open a file and when hovering in the application icon, we see the dialog only and not the application... That's why I'm looking for a way in TestComplete to change the z order of the application displayed. It seems Windows has some API to do so, and that is where I'm currently investigating. I hope this makes the question clearer. Thanks for your concern !2.7KViews0likes5CommentsFocus on window not visible on screen
Hello, I'm testing an application (delphi) and every time I press F12, I get a new window which helps me navigate in the application (note that both the application and the window are part of the same process, which is why minimizing does not show the window). My issue is that when it is done enough times, the window appears behind the application. From what the devs told me, I have to change the window Z order to make it visible on screen. I have tried multiple things, but the object always says visible = true, while visibleOnScreen = false. Any idea how can I change the z order of application windows or even better, make my window visible again ?Solved2.7KViews0likes9CommentsKeys Method - Holding [ALT] while pressing twice the same key
Hi guys, I have an issue when holding a certain key and pressing another key multiple times, during the same combination. At the moment, I have an object and I try to hold [ALT] while pressing [F7] twice, in order to change section in my desktop application. Here is the code in javascript : var myObject =Aliases.Sys.MyObject; myObject.Keys("[Hold]~[F7][ReleaseLast][F7]"); As you can see, it shoul press and hold [ALT], the [F7], release [F7] and re-press it. The real behavior is that it hold [ALT], presses [F7] and keeps holding [ALT] until I have an error due to unexpected window opened (while [ALT] is hold, there is a window opened). I used debugging, and the code seems to be stuck in the Keys method. Not sure what to do, any ideas ?Solved1.3KViews0likes2Comments