Forum Discussion

kcurteman's avatar
kcurteman
Occasional Contributor
10 years ago

Could not convert variant of type (OleStr) into type (Double)

I am using TestComplete 11, and have mapped a Stores Object to test a UI form that loads on the page. Mostly It is mapped just ot check all cells and tables are visible, with a few lables checking for the correct contentText.

 

When I first ran an object checkpoint against it, it worked smoothly with only minor issues with values being slightly different or some cells being hidden.

 

However, now when I try to use it (still in the same keyword test with no modifications made to it) I keep getting an Exeption thrown saying: 

Could not convert variant of type (OleStr) into type (Double)
 
I have dug through everywhere I can think to look, but cannot find exactly where it is trying to perform this conversion.
 
Any Ideas?

5 Replies

    • kcurteman's avatar
      kcurteman
      Occasional Contributor

      I believe that it is a TC error, but i'm not 100% sure. It doesn't really give me enough info.

       

      Here is a screen shot of the exception:

       

      And no, I have not used devexpress. Is that a free tool that would help here?

       

  • Hi,

     

    > I have dug through everywhere I can think to look, but cannot find exactly where it is trying to perform this conversion.

    Double-click on the error line in the log. This should navigate you to the operation / line of code that errored-out.

    • kcurteman's avatar
      kcurteman
      Occasional Contributor

      Double-clicking the exception takes me to the Operation of the Object Checkpoint, but it does not help me locate what part of the Object is causing the error. It is a large object, with a lot of tables, panels, and cells that it is using as reference to check against, but that is all condensed into the one object checkpoint.

      • I'd say that you're running into a TestComplete bug.  You should continue this in a support case.

         

        To isolate this you'll probably have to perform a search . . . removing properties from the stored baseline object in an effort to pinpoint which property is causing the problem.  Because of the error message (string to double), I'd start with any tables containing numbers.