Make window disposal optional

[GoogleCodeExporter]

From J. Simmons:

Using FEST-Swing to run partial tests.

One of our products uses an embedded jre to allow third parties to add
new dialogs and behaviors to the program.  We also use this
architecture internally to develop PlugIns for the product.  We have
been experimenting with using FEST-Swing to build tests for these Java
elements and ran into a small problem with the cleanup process.

Almost all of our tests require interacting with both the core
product's interface and the Java interfaces.  So we need to use FEST
to perform only some of the steps for the actual test, namely those
that require interacting with the Java UI.  This works pretty well
until we run cleanUp(), and FEST destroys all of our Java UI elements,
in turn breaking the larger context of our tests.

We found that if we add an option to cleanUp() to not call
disposeWindows() everything appears to work fine.  So, we wanted to
check and see if there were any reasons we should not use this
approach.  And if there are not, we wanted to see if we could
contribute a patch that implements this feature.

Original issue reported on code.google.com by Alex.Rui...@gmail.com on 19 May 2008 at 2:40

Attachments:

• fest_run_partial.diff

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Added method 'cleanUpWithoutDisposingWindows' to Robot and RobotFixture in 
package
'org.fest.swing.core'.

Original comment by Alex.Rui...@gmail.com on 1 Jun 2008 at 6:57

• Changed state: Fixed

[GoogleCodeExporter]

Set the module as a label, instead of being part of the title.

Original comment by Alex.Rui...@gmail.com on 1 Dec 2008 at 1:58

• Changed title: Make window disposal optional
• Added labels: Module-fest-swing