question

tlawall avatar image
tlawall asked tlawall posted

SDK example code and guides

 

I'm currently dissecting the Network Tool application session plugin, and there's several questions I have relating to it's structure.  Unfortunately, I do not have eclipse plugin development experience, nor do I have any experience developing iTest plugins, so I'm only able to reverse engineer it so far before hitting brick walls.

 

  • what are the minimum set of files I need for a plugin?  Would you be able to provide those with an explanation of why each file is needed?
  • Would you be able to provide a guide as to what the minimal structure of a plugin needs to be?
  • Would you be able to describe what parts of the plugin provide iTest with output it can capture in the responses?

What I'm looking for in some ways is a guide, some simple explanations of things that are taken for granted if you're already familiar with plugin development.

 

Currently, I need to create what I call a "tool shell", where I have libraries that I want to leverage from within iTest, but currently am doing so via a command line session, which is taking forever for some of my datasets, due to the 100ms step delay required for proper syncronization between iTest and an external shell.  My code base is built out using these commands, and fortunately, if I could build a shell analog (even the simplest shell) application session plugin, it would allow me to use all of my test case code as is, and only swap out one proc and one session profile.

iTestsdk
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

AdamB avatar image
AdamB answered AdamB posted

Have you been able to get access to the walkthough guides for SDK development?

10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

YujieL avatar image
YujieL answered YujieL posted

For fundamental eclipse plugin questions, it would be best to google around on eclipse plugin development. You will find thorough answers to your questions.

 

Each plugin has a manifest.mf file which contains the plugin name, required dependencies and exported packages. 
One really important plugin file is the plugin.xml file.. This file only exists when you you define an extension point or if you're using an existing extension point.  You need to understand how to use an extension point because your application will need to use the SDK extension point in order to contribute itself as an application that iTest understands.  The easiest way to see what all the plugin files are is to create a plugin project in your Eclipse IDE.

10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.