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.