<?xml-stylesheethref="../../nbbuild/javadoctools/apichanges.xsl"type="text/xsl"?>
<!DOCTYPE apichanges PUBLIC"-//NetBeans//DTD API changes list 1.0//EN""../../nbbuild/javadoctools/apichanges.dtd">
<apichanges>
<!-- First, a list of API names you may use: -->
<apidefs>
<apidef name="junit-plugin">JUnit Plugin SPI</apidef>
</apidefs>
<!-- ACTUAL CHANGES BEGIN HERE: -->
<changes>
<change id="issue-74160">
<api name="junit-plugin"/>
<summary>Added SPI for JUnit plugins</summary>
<version major="2" minor="21"/>
<date day="7" month="4" year="2006"/>
<author login="mpetras"/>
<compatibility addition="yes"/>
<description>
<p>
Introduced new SPI - abstract class <code>JUnitPlugin</code> (with a nested
enum <code>CreateTestParam</code> and a nested final class <code>Location</code>).
Introduced to allow non-J2SE projects to plug in their own implementation
of JUnit support, i.e.:
</p>
<ul>
<li>jumping to a test for the current class/method and back</li>
<li>generating of test skeletons</li>
</ul>
</description>
<class package="org.netbeans.modules.junit.plugin" name="JUnitPlugin"/>
<issue number="74160"/>
<issue number="42349"/>
</change>
<change id="issue-72819">
<api name="junit-plugin"/>
<summary>Added enum members
INC_CLASS_SETUP and INC_CLASS_TEARDOWN</summary>
<version major="2" minor="23"/>
<date day="16" month="3" year="2007"/>
<author login="mpetras"/>
<compatibility addition="yes"/>
<description>
<p>
Added members <code>INC_CLASS_SETUP</code> and
<code>INC_CLASS_TEARDOWN</code>
to enum <code>JUnitPlugin.CreateTestParam</code>.
Added method
<code>createTestActionCalled(FileObject[])</code>
to class <code>JUnitPlugin</code>.
</p>
</description>
<class package="org.netbeans.modules.junit.plugin" name="JUnitPlugin"/>
<issue number="72819"/>
</change>
</changes>
<!-- Now the surrounding HTML text and document structure: -->
<p>This document lists changes made to the JUnit APIs. Please ask on the
<code>dev@junit.netbeans.org</code> or <code>nbdev@netbeans.org</code>
mailing list if you have any questions about the details of a
change, or are wondering how to convert existing code to be compatible.</p>
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.