For all extension points, to learn more about that extension point you need to
generate the document that describes it.
Navigate to the plug-in that contains the extension point. (The name of the
plug-in is part of the qualified name of the extension point unless stated
otherwise. Remove the last
word of the extension point name and what you have left is the name of the
plug-in. For example, the org.eclipse.hyades.ui.analyzerExtensions extension
point is part of the org.eclipse.hyades.ui plug-in.)
Open the plugin.xml file with the Plug-in Manifest editor:
highlight the file, right click, Open with... > Plug-in Manifest editor.
Turn to the Extension Points tab.
Select the extension point from the All Extension Points list and
click the Open extension point description link to generate the
document for that extension point.
Use the extension points described in this section to extend the symptom catalog function.
This extension point registers an execution component (local or remote) for use in the
test launch sequence and associates it with one or more supported test types.
Run a single test on a node and send control events
(this link opens a file on the external TPTP web site).
This extension point is used to describe a editor form that is used to create a org.eclipse.hyades.models.common.configuration.CFGPropertyGroup contained by a org.eclipse.hyades.models.common.configuration.CFGConfigurableObject.
This extension point allows to define special type provider proxy node for a
given kind of test assets (such as datapool or location for instance). It is
only used in the logical mode of the test navigator.
This extension point allows to define proxy node elements in the test navigator
to replace specified type elements such as test suite or execution elements.
This extension point is used for both test navigator modes (resource or
This extension point is used to describe an existing type. It is important to note that a type
is a string value that is stored in the model. This extension point does not create a new
type but allow implementors to define, for example, a name and a description that could to be
presented in the UI.