Forum Discussion

Louis's avatar
Louis
Contributor
15 years ago

Type mismatch when using dat adriven testing.

I am using a data driven keyword script to label peaks on a graph. I am having problems when the values within a column of my driving data switches from a numerical value to a letter value or vice versa. For example test complete will label (using the wtext command) a peak as 12 on the first loop then 13 on second loop but when it attempts to label the peak as R the script stops and the log shows a type mismatch error.  have tried using the data in csv format and excel format when using the excel data to drive the test i formatted all cells in the work sheet as text and that didn't help. Seems like testcomplete is judging what sort of data should be entered for each peak (integer or letter) then refuses to change. I thought it would just blindly enter the data I provided it with.
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    15 years ago

    Hi Louis,


    I suppose that the problem can be caused by the control itself - it is possible that the native property/method used by TestComplete can accept only numeric values, not strings. Could you please provide us with the problematic code line so we can see how the text is assigned? Also, let us know the name and version of the problematic control.


    BTW, you can use the aqConvert object to convert variable types explicitly when needed.

  • Louis's avatar
    Louis
    Contributor
    15 years ago
    Hi, the command I'm using is wtext with a code expression (DDT.CurrentDriver.Value("myvalue"). I,ve tried using a schema.ini file to accompany the data source csv file but it didn't work. The actual on screen component of the tested app isn't a problem as i can manually enter what I please with no problems at all.
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    15 years ago

    Hi Louis,


    Provide us with the following information:


    1. Please zip your entire project suite folder along with the log of the failed test execution and send us the archive. Make sure that messages in your log correspond to the latest version of your tests. Also, provide us with the file you read in your script.


    2. Let us know the problematic control's WndClass. If the control is a .NET control, let us know the value of its ClrFullClassName property. This will help us find out what control you are using.

  • Louis's avatar
    Louis
    Contributor
    15 years ago
    Hello for security reasons I'm unable to export out my work. The control in question is "ComponentFactory.Krypton.Toolkit.KryptonTextBox+a" The test script is constructed in the same manner as detailed in the falafel software demo video for datadriven testing that is linked on the testcomplete support page. the driving data consists of 22 columns of data each column contains a mixture of integers and letter values.
  • AlexanderM's avatar
    AlexanderM
    Staff
    15 years ago

    Hi Louis,


    TestComplete does not provide special support for this control, so it is quite possible that the wText property (which is a TestComplete wrapper property) may not function properly in this case. Try using the control's native properties or methods to set the text. Also, as a workaround, you can use the Keys method instead of assigning the text directly - this method should work regardless of the control's type (unless the control handles keystrokes incorrectly).

  • Louis's avatar
    Louis
    Contributor
    15 years ago
    Yep I tried the keys method as  thought that  might just simply replicate a user pressing keys, but it too generated a type mismatch. If after the script stops due to the type mismatch error I go to the tested apps desired control left open by testcomplete. I am able to enter the desired value manually using my keyboard. This is what I just don't understand I can manually enter what I please but testcomplete can't. I also tried using an If..then command linked to an integer  within the driving data e.g if the driving data value = 99 enter R using the keys command. This didn't work either.
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    15 years ago

    Hi Louis,


    The fact that the Keys method does not work for you is really strange - the method is supposed to send keystrokes in the same way as user keystrokes are sent. We will try to find a sample application with this control and reproduce the problem on our side. In the meantime, the only workaround left is to use the control's native methods and properties which should be exposed to TestComplete.


    When we have some results with reproducing the problem, I will let you know. BTW, it would help us a lot if you provided us with an application with which the problem can be reproduced.

  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    15 years ago

    Hi Louis,


    A few more things to check - this can be important. There is a possibility that the problem is actually caused by your data source or the code you use to read the data or both and is not actually related to the control. Please check the following and let me know your results:

    1. Check whether the problem can be reproduced with Notepad.

    2. Check whether the problem can be reproduced with your application if you pass the same data as a string value explicitly in the Keys method instead of passing the "DDT.CurrentDriver..." value.

  • Louis's avatar
    Louis
    Contributor
    15 years ago
    Hi Thanks for your reply. If i use either the set text or keys command without data driving i am able to enter the desired values.

    If I use data driving with a simple note pad file containing a single column of data  I am able to enter the desired values.

    The problem occurs as soon as I attempt data driving using either excel or csv

    It seems like testcomplete decides each column of data is either string or integer and throws the mismatch if it encounters the unexpected.

    I guess that the use of the notepad file is ok for a little test as you requested but not really all that practical for the volume of data i need to work with.
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    15 years ago

    Hi Louis,


    OK, now we know that the problem is actually caused by the file. What happens if you try to use the same script with the same file (which contains multiple columns), but enter the values in Windows Notepad window instead of the problematic control? If the problem also persists in this case, it means that it is not related to the control in question at all. In this case we'll need a sample project suite along with a file which can be used to reproduce the problem with Windows Notepad instead of your tested application.