Java Doc for ComponentTestFixture.java in  » Testing » abbot-1.0.1 » junit » extensions » abbot » Java Source Code / Java DocumentationJava Source Code and Java Documentation

Use ComponentTestFixture.showFrame(Component) when testing individual components, or ComponentTestFixture.showWindow(Window) when testing a Frame , Dialog , or Window .

Any member fields you define which are classes derived from any of the classes in ComponentTestFixture.DISPOSE_CLASSES will be automatically set to null after the test is run.

WARNING: Any tests which use significant or scarce resources and reference them in member fields should explicitly null those fields in the tearDown method if those classes are not included or derived from those in ComponentTestFixture.DISPOSE_CLASSES . Otherwise the resources will not be subject to GC until the TestCase itself and any containing junit.framework.TestSuite is disposed (which, in the case of the standard JUnit test runners, is never).

If any exceptions are thrown on the event dispatch thread, they count as errors.

If any exceptions are thrown on the event dispatch thread, they count as errors. They will not, however supersede any failures/errors thrown by the test itself unless thrown prior to the main test failure.

The given Runnable should contain the code which will show the modal Dialog (and thus block); it will be run on the event dispatch thread.

This method will return when a Dialog becomes visible which contains the given component (which may be any component which will appear on the Dialog ), or the standard timeout (10s) is reached, at which point a RuntimeException will be thrown.

For example,

 final Frame parent = ...;
 Dialog d = showModalDialog(new Runnable) {
 public void run() {
 JOptionPane.showInputDialog(parent, "Hit me");
 }
 });
 

ComponentTestFixture.showModalDialog(Runnable)

Modal dialogs may be shown with this method without blocking.