| java.lang.Object
 org.netbeans.junit.NbModuleSuite
| NbModuleSuite | | final public class NbModuleSuite extends Object (Code) | | Wraps a test class with proper NetBeans Runtime Container environment.
This allows to execute tests in a very similar environment to the
actual invocation in the NetBeans IDE. To use write your test as
you are used to and add suite static method:
public class YourTest extends NbTestCase {
public YourTest(String s) { super(s); }
public static Test suite() {
return NbModuleSuite.create(YourTest.class);
}
public void testXYZ() { ... }
public void testABC() { ... }
}
since:
1.46
author:
Jaroslav Tulach |
| Method Summary | |
| public static Test | create(Class<? extends Test> clazz, String clustersRegExp, String moduleRegExp)
Factory method to create wrapper test that knows how to setup proper
NetBeans Runtime Container environment. |
| create | | public static Test create(Class<? extends Test> clazz, String clustersRegExp, String moduleRegExp)(Code) | | Factory method to create wrapper test that knows how to setup proper
NetBeans Runtime Container environment.
Wraps the provided class into a test that set ups properly the
testing environment. The set of enabled modules is going to be
determined from the actual classpath of a module, which is common
when in all NetBeans tests. All other modules are kept disabled.
In addition,it allows one limit the clusters that shall be made available.
For example ide.*|java.* will start the container just
with platform, ide and java clusters.
Parameters:
clazz - the class with bunch of testXYZ methods
Parameters:
clustersRegExp - regexp to apply to name of cluster to find out if it is supposed to be includedin the runtime container setup or not
Parameters:
moduleRegExp - by default all modules on classpath are turned on,however this regular expression can specify additional ones. If notnull, the specified cluster will be searched for modules with suchcodenamebase and those will be turned on runtime container ready test |
|
|