Forum Discussion

sachinjadhav_12's avatar
sachinjadhav_12
Occasional Contributor
15 years ago

Custom Plug-ins

Hi



I'm working on few automation projects and we have custom components which are huge roadblocks while performing automation. I would like to know steps to create Custom Plug-in for any custom components. I'm aware that it is difficult and programming knowledge of Delphi/VC++ is must. I appreciate if you could share some tips / document that would help me to start with building plug-ins.



Regards

Sachin

3 Replies

  • ArtemS's avatar
    ArtemS
    Icon for Alumni rankAlumni
    15 years ago
    Hi Sachin,



    TestComplete can be extended in two ways: via creating custom plug-ins and via script-extensions. See TestComplete Extensions and SDK and  Creating Custom Plug-Ins.




    1. Plug-ins are compiled as DLLs or .NET assemblies and created with full-fledged programming languages like Visual C++, C# or Delphi. To create plug-ins, you need to download TestComplete SDK. It contains the modules required to create your own plug-ins,  documentation and sample projects.





    2. Script extensions are more "light-weight" and simple, while being still powerful. They are created in VBScript or JScript. See the Script Extensions online topic and the Creating and Deploying Script Extensions screencast.




    I'd recommend that you attempt creating script extensions for your custom components. Probably, in the from of run-time objects (similar to pre-installed WMI Object) which are added to TestComplete’s object model and displayed in the Code Completion window.
  • sachinjadhav_12's avatar
    sachinjadhav_12
    Occasional Contributor
    15 years ago
    Thanks for the tips.



    As you suggested, creating script extensions for custom components. btw, its not a open application, we have a grid (ComponentOne) which is absolutely not recognized by TestComplete.



    I have tried script extensions, but I think, it's useful only if you have some properties recognized by TestComplete. In my case it was not working, So,  I guess option1 (Plug-ins) would better choice ?



    Regards

    Sachin
  • ArtemS's avatar
    ArtemS
    Icon for Alumni rankAlumni
    15 years ago
    Actually, script extensions can handle non-open applications in the same degree as TestComplete does.



    However, I'm not concerned about all the aspects of your automation projects.  So, it's up to you to decide which of the extension approaches to choose.

    In general, the SDK plug-ins provide greater abilities to organize the interaction between TestComplete and the tested application.