Error: The window size is (0, 0);

Hi Suzanne,



>  it does generate a new button every time. :(

Then I would do the following:

-- Put a breakpoint on the MyControl.Click() line within the loop and run the test;

-- When TestComplete stops on the breakpoint, open the Evaluate window (Ctrl-F12 or Ctrl-F7 shortcut, depending on the keyboard scheme you are using), enter 'MyControl' into the expression field and press the Evaluate button;

-- After the expression is evaluated to [object], press the Inspect button and examine .Width and .Height properties. Continue test execution if both of them greater than zero;

-- If one or both properties are equal to zero, then copy the value of the FullName property and paste it into some editor (e.g. Notepad) for future reference;

-- Close Evaluate window and, using the Object Spy one, highlight the button that you think the code should work with and check the value of its FullName property;

-- Compare this value with the one from the editor. I bet they should be different;

-- If this is the case, then click the Highlight Object in the Object Tree button in the Object Spy to navigate to the highlighted button in the object tree;

-- Not far from there, there should be one more button with the full name equal to the one from the editor. Try to find this button and either analyze why test code found it or show this to the developer and ask him/her why one more button has appeared and why the previous one was hidden.





> So I guess I'll try this FindAllChildren() method.

Just in case, the untested sample VBScript pseudo-code:

Do

  arr = ParentObject.FindAllChildren(...)

  For i = BuiltIn.VarArrayLowBound(arr, 1) To BuiltIn.VarArrayHighBound(arr, 1)

    Set bMyControl= arr(i)

    If ((MyControl.Height > 0) And (MyControl.Width > 0)) Then

      Exit For

    End If

  Next



  If ((0 = bMyControlHeight) Or (0 = bMyControlWidth)) Then

    Call Log.Error("Visible button was not found")

  Else

    MyControl.Click

  End If

  ...

Loop While ...

Thanks for the reply Alex!



I tried using conditiona mapping, but this time round the error came up as "object does not exist."



I'm working on modifiying my code but if I'm honest, I'm not really sure how to try your second suggestion. My ability.... to deal with arrays is somewhat bad :P 



I'll  speak to the developers! 

Hi Alex, 



So I've spoken to the developer and he says that it does generate a new button every time. :(



So I guess I'll try this FindAllChildren() method. Would you be able to talk me through it? (I'm very new to this!)

Hi Alex,



Thanks ever so much for helping me out! I'm looking at it now, and hopefully it will work! I appreciate the time you took to reply to me.



Thanks again!

Oh...



> he says that it does generate a new button every time. :(

Only now I noted that developer confirmed that the new button is generated every time.

In this case, Suzanne, you should stick to the second approach that uses FindAllChildren() as the first approach was a description of the debugging technique when the test works with the object other than expected.



One more possible approach in case you are using NameMapping for this button is to specify exact Width and Height as the additional recognition parameters. Note, that this will work only if the values of Width and Height are always the same.

If the values may be different (e.g. for different screen resolutions), than you may switch NameMapping recognition for this button to the Conditional mode where it will be possible to specify that Width and Height  must be greater than some (minimal) value.



P.S. All the above are a kind of workarounds to make your test code not failing. However, personally I would first talk to developers and ask for the real reason to generate the new button every time. From your description this sounds like waste of computer resources when, actually, the memory leak occurs for every iteration.

It's because they use the bootbox modal. :)