We do this the other way around, in our product we start Costello, and indeed run Abbot test scripts from a menu that gets added to the product when built in debug mode. There is a special interface for invoking Costello that tells it is running inside another product. The code looks like this:
EditorContext ec = new EditorContext();
TestHierarchy th = new TestHierarchy();
// Make sure that we don't ignore the exisitng main window
You can also do useful stuff like overriding the default template used for new scripts, which can be useful. This way the startup will be as per your normal application which gives better fidelity. We use a system property to read a file that causes tests to be loaded an run.
Hope this is of some help,
The JNLP file needs to add the Abbot jars (I think this list is out of
<!-- The following jar elements are required to launch Abbot.
The abbot jar
must be first since it contains the main class. -->
And the JNLP file needs to switch its main class:
The thing to be clear about this approach is....you are not launching a
Java Web Start application from Costello. Your application is coming
along with Costello, which is now the Java Web Start application
specified by your JNLP file. Costello is merely executing your
application's main method to initialize it and cause it to display its
frames and windows. To literally launch a Java Web Start application
using its JNLP file from Costello, Costello would have to create a new
JVM process running the Java Web Start main program, and I don't know
how Costello would do that or whether it would be able to do anything
with the new separate JVM process.
vikas jain wrote:
I am looking from QA point of view. I can have all the jar files on my
machine. But how do I launch my http://
application from Costello. If you can provide some steps or sample of
how you have done it, it would be great .
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
abbot-users mailing list