Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Porting Custom Test Exec Demo to TPTP 4.0
Porting Custom Test Exec Demo to TPTP 4.0 [message #12609] Wed, 30 March 2005 05:30 Go to next message
Eclipse User
Originally posted by: ext.per.johansson.tietoenator.com

I am trying to port the demo "Building a Custom Test Execution
Environment" from the Eclipse Con. 2005 to TPTP 4.0
(tptp.runtime-TPTP-4.0-200503211143.zip). Has anyone tried this?
For example the extension point org.eclipse.hyades.test.ui.launchableType
is removed in TPTP 4.0. Does anyone know what to use instead?
Is there a description of differences between TPTP 4.0 and earlier
releases somewhere?
/Per
Re: Porting Custom Test Exec Demo to TPTP 4.0 [message #12822 is a reply to message #12609] Fri, 01 April 2005 12:11 Go to previous message
Joe Toomey is currently offline Joe Toomey
Messages: 79
Registered: July 2009
Member
This is a multipart message in MIME format.
--=_alternative 005E3FA685256FD6_=
Content-Type: text/plain; charset="US-ASCII"

The difficulty you have experienced with TPTP 4.0 is unsurprising, as it
is an API breaking release in which we repackaged many of our plugins, and
we have yet to produce a migration guide. We plan to assemble a migration
guide during our iteration 3 (of 4), which begins next week and ends
somewhere around May 6th. Technical documentation for Hyades/TPTP has
been somewhat lacking since the project's inception, but we are slowly
working to address that problem.

To your specific questions, I believe that the launchableType extension
point was renamed to launchconfigLaunchableType, and now lives in the
o.e.hyades.test.core plugin. At a high level, the repackaging that has
been done in 4.0 has essentially collapsed all of the test related plugins
from 3.3 into 4 plugins in 4.0. The 4 plugins are:

o.e.hyades.test.core Core TPTP Test framework (non-UI)
o.e.hyades.test.tools.core Core TPTP Tool support (non-UI code
supporting JUnit, URL and Manual test types)
o.e.hyades.test.ui TPTP UI framework code (generic editors
and viewers, UI extension points, etc.)
o.e.hyades.test.tools.ui TPTP Tool UI code (test type
specific editors, viewers, etc.)

The two "tools" plugins contain the code to support the three built in
test types, while the other two plugins contain the TPTP test framework.
The goal is that you should be able to add support for your own test type
using only test.core and test.ui. If you can validate this sooner than we
can, it would be valuable to get your feedback.

In writing the EclipseCon tutorial, in many places I worked backward from
the existing tool implementations. This technique may prove useful to you
as you move forward on your project. If you have not done so already, you
may want to subscribe to the tptp-testing-tools-dev@eclipse.org mailing
list. It is useful for developers -- often there will be postings about
known defects and their workarounds, for example.

Thanks,
--Joe

--=_alternative 005E3FA685256FD6_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">The difficulty you have experienced
with TPTP 4.0 is unsurprising, as it is an API breaking release in which
we repackaged many of our plugins, and we have yet to produce a migration
guide. &nbsp;We plan to assemble a migration guide during our iteration
3 (of 4), which begins next week and ends somewhere around May 6th. &nbsp;Technical
documentation for Hyades/TPTP has been somewhat lacking since the project's
inception, but we are slowly working to address that problem.</font>
<br>
<br><font size=2 face="sans-serif">To your specific questions, I believe
that the launchableType extension point was renamed to </font><font size=2 color=#008000 face="Courier New">launchconfigLaunchableType</font><font size=2 face="sans-serif">,
and now lives in the o.e.hyades.test.core plugin. &nbsp;At a high level,
the repackaging that has been done in 4.0 has essentially collapsed all
of the test related plugins from 3.3 into 4 plugins in 4.0. &nbsp;The 4
plugins are:</font>
<br>
<br><font size=2 face="sans-serif">o.e.hyades.test.core &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Core TPTP Test framework
(non-UI)</font>
<br><font size=2 face="sans-serif">o.e.hyades.test.tools.core &nbsp; &nbsp;
&nbsp; &nbsp;Core TPTP Tool support (non-UI code supporting JUnit,
URL and Manual test types)</font>
<br><font size=2 face="sans-serif">o.e.hyades.test.ui &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;TPTP UI framework code
(generic editors and viewers, UI extension points, etc.)</font>
<br><font size=2 face="sans-serif">o.e.hyades.test.tools.ui &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;TPTP Tool UI code
(test type specific editors, viewers, etc.)</font>
<br>
<br><font size=2 face="sans-serif">The two &quot;tools&quot; plugins contain
the code to support the three built in test types, while the other two
plugins contain the TPTP test framework. &nbsp;The goal is that you should
be able to add support for your own test type using only test.core and
test.ui. &nbsp;If you can validate this sooner than we can, it would be
valuable to get your feedback.</font>
<br>
<br><font size=2 face="sans-serif">In writing the EclipseCon tutorial,
in many places I worked backward from the existing tool implementations.
&nbsp;This technique may prove useful to you as you move forward on your
project. &nbsp;If you have not done so already, you may want to subscribe
to the tptp-testing-tools-dev@eclipse.org mailing list. &nbsp;It is useful
for developers -- often there will be postings about known defects and
their workarounds, for example.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">--Joe</font>
<br>
--=_alternative 005E3FA685256FD6_=--
Previous Topic:piAgent don't scale
Next Topic:gla adapter
Goto Forum:
  


Current Time: Thu Aug 21 00:32:08 EDT 2014

Powered by FUDForum. Page generated in 0.01582 seconds