Forum Discussion

manuel_buelow's avatar
manuel_buelow
New Contributor
13 years ago

TestComplete 9.20 - Need for Installation of DevExpress?

Hello there,



i have a problem by recording a software, which uses DevExpress-components in there masks. I think everytime, when a component couldn't be identified in the mask, it would be classified as "TextBoxMaskBox" in the teststeps.

That is a problem, when I have a ComboBox on the Mask:

I want to record a click to open the "DropDown" of the ComboBox and after that I want to choose an item in the DropDown. But when I finished the recording, I only found a "SetText"-Operation in my teststeps, as you can see in the attached file. Otherwise the founded item in the teststep is a "TextBoxMaskBox" and not a ComboBox.

What I have to do now: I have to find the position of the DropDown-button in the ComboBox. Then I have to insert a new teststep with a "Click"-operation and the founded position (the marked teststep in the attached file).



My question is:

Is there a possibility to install the DevExpress-libraries in TestComplete, that the mask-components always been identified right by recording? So I am not have to fill in the teststeps for clicking the DropDown-Button by hand after recording.

1 Reply

  • AlexeyKolosov's avatar
    AlexeyKolosov
    Icon for Staff rankStaff
    13 years ago


    Hi Manuel,


     


    The fact that TestComplete records interactions with a control named TextBoxMaskBox is caused by DevExpress controls' internal implementation - this internal control is created for every control with masked input, as far as I know. However, I'm not sure I understand what problem you currently face. A recorded test should be played back successfully regardless of the way the controls are implemented. If the test cannot be played back successfully, please zip your entire project suite folder along with the log of the failed test execution and send me the archive. Make sure that messages in your log correspond to the latest version of your tests. You can do this via replying in the support case you created (M0111343) to make sure your message gets the appropriate priority.