Overview (NB JUnit)

NB JUnit
Package	Description
org.netbeans.junit
org.netbeans.junit.diff

Module contains NetBeans extension to JUnit. It provides classes and methods which allow one to verify performance, memory consumption, file output and other aspects of the IDE or applications built on the NetBeans Platform.

What is New (see all changes)?

Dec 1 '11 System property branding.token

System.getProperty("branding.token") recognized and influences branding used during the test.
Nov 11 '11 NbModuleSuite.Configuration.hideExtraModules()

Now there is a way to disable not explicitly enabled modules.
May 19 '11 NbModuleSuite.Configuration.suite()

You may now call suite() directly on a Configuration object.
May 5 '11 NbTestCase.logRoot to collect messages from just some code

Overridable method to avoid excessive logging of uninteresting components.
Apr 8 '11 NbModuleSuite.Configuration.addStartupArgument

NbModuleSuite.Configuration now has a addStartupArgument method which allows one to append one or more command line arguments which will be used to start the application. Arguments which must be passed directly to the JVM should still be specified in the test.run.args property.

Use Cases

Tests typically extends NbTestCase.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

Group of java interfaces

Interface Name

In/Out

Stability

Specified in What Document?

Group of systemproperty interfaces

Interface Name	In/Out	Stability	Specified in What Document?
nbjunit.diff.impl.CmdLine	Exported	Under Development	used only when nbjunit.diff.impl is set to org.netbeans.junit.diff.NativeDiff class. This property contain command line, which is called from NativeDiff class to perform comparision. This property use also '%TESTFILE%' and '%PASSFILE%' variables understood by NbJUnit, which are replaced with real file names when running tests.
nbjunit.workdir	Exported	Under Development	path to a directory, which is used as a root for tests' working directories (for details see JavaDoc for NbTestCase.getWorkDir()).
NbTestCase.order	Exported	Friend	This property tries to influence the order of `NbTestCase` methods so it is more predicatable (see Order of elements for description of the problem). The acceptable values of the property are: "natural" - use the methods as provided by JDK (e.g. quite random on JDK7) "a-z" - sort the tests in ascending alphabetical order "z-a" - sort the tests in descending alphabetical order "shuffle" - randomize the order of the tests. If a test fails in this mode a seed is attached to the failure message, use it in the seed mode seed mode "12234390434" - one can specify any long value as a seed to shuffle the methods. Use this to reproduce random failures The default order is natural right now, but this may change in future to mitigate the randomness caused by JDK7.
branding.token	Exported	Under Development	NbModuleSuite can now be influenced by system property `branding.token`. If it is provided (by Ant harness for example), it is used to call NbBundle.setBranding.

Implementation Details

Where are the sources for the module?

The sources for the module are in the NetBeans Mercurial repositories.

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

Nothing.

Read more about the implementation in the answers to architecture questions.

NB JUnitFriend, Private or Third Party