|
Tutorials -
Swing Testing
|
The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been used. |
|
Tutorials -
Swing Testing
|
The name() Test
Like the wasCancelled()method, the name() method is not thread-safe, so our test class needs another boilerplate helper method: |
|
Tutorials -
Swing Testing
|
The wasCancelled() Test
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we will enter a name, cancel the dialog, and then call wasCancelled(). |
|
Tutorials -
Swing Testing
|
The Constructor Test
A freshly constructed SaveAsDialog should be in a known state, and we need to check the things we listed at the start of this chapter. |
|
Tutorials -
Swing Testing
|
The init() Method
The job of the init() method is to create and show the SaveAsDialog instance so that it can be tested: |
|
|
Tutorials -
Swing Testing
|
The ShowerThread Class
Since SaveAsDialog.show() blocks, we cannot call this from our main thread; instead we spawn a new thread. This thread could just be an anonymous inner class in the init()method: |
|
|
Tutorials -
Swing Testing
|
Unit Test Infrastructure
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. We'll start with the UI Wrapper class and the init() and cleanup()methods. |
|
|
Tutorials -
Swing Testing
|
Getting the Text of a Text Field
The method is getText(), and there is a variant to retrieve just the selected text: |
|
|
Tutorials -
Swing Testing
|
Outline of the Unit Test
The things we want to test are:
- Initial settings:
- The text field is empty.
- The text field is a sensible size.
- The Ok button is disabled.
- The Cancel button is enabled.
- The dialog is a sensible size.
|
|
|
Tutorials -
Swing Testing
|
Swing Extreme Testing by Tim Lavers, Lindsay Peters
This book is a practical guide to automated software testing for extreme Java programming using Swing GUIs, with lots of ready-to-use real-life examples and source code for automated testing of the software components usually regarded as too hard to test automatically. |
|
|
Reviews -
Books
|
Swing Extreme Testing Book Review
Swing used to be a simple component offered as an add-on for Java. This plug-in can be used as a GUI (graphical user interface) to develop as an add-on for the Java application. It has the ability to emulate certain platforms eventually building a powerful application. With this plug-in, users will experience the full potential of Java as it uses its native capability and with the help of Swing, different web development languages are added to the application. Swing’s ability to emulate eventually made this plug-in one of the most popular and important tools in Java development that it eventually became part of Java development package. |
|
|
|
