![]() |
JSwat ProjectTesting |
This document describes a series of tests that validate the proper operation of JSwat. When major releases of JSwat are made this checklist should be performed to confirm JSwat's quality. It is highly recommended that the tester print these tests onto paper and check off each test as it is performed. Otherwise it is very easy to miss test cases.
Each of the series of tests below should be run on the following platforms at a minimum, though more would be preferred. In each case, use the most recent released version of the product. Do not test using beta software as that may give false test responses. That point is more important for the JDK releases than the operating system releases. There is little difference from the perspective of the JVM between Linux 2.2 and Linux 2.4 or Windows NT 4.0 and Windows 2000, for example.
OS | Blackdown JDK | IBM JDK | Sun JDK |
---|---|---|---|
Linux |
|
|
|
Solaris | N/A |
|
|
Windows | N/A |
|
The Actions in JSwat are simply those features that are activated by either a menu item or a toolbar button. JSwat distinquishes them from the commands which have similar functionality but are invoked by typing commands into a text field. Use this checklist to test the actions.
Breakpoints in JSwat are one of the most important features and require some of the most rigorous testing. Use this checklist to test the breakpoints.
The Commands in JSwat are similar to the actions except that they are invoked by typing the commands at the command input prompt. This is most useful when running JSwat in console mode or when a similar action does not exist. Use this checklist to test the commands.
The console interface of JSwat is vastly different from the default, graphical interface, primarily because the panels and other status indicators are not available. This makes it especially important that the JSwat commands are verbose and that the program status is clearly indicated whenever it changes. Use this checklist to test the console interface.
The panels in JSwat display information about the debuggee VM being debugged. Use this checklist to test the panels.
The preferences in JSwat allow the user to configure how the program looks and behaves. Use this checklist to test the preferences.
Keyboard shortcuts are key combinations used to invoke certain actions in JSwat. These key combinations are often defined in the Preferences dialog of JSwat, in the "Shortcuts" category. Use this checklist to test the keyboard shortcuts.
Starting JSwat is a category of its own due to the options available when launching the program. Use this checklist to test launching the program.
The source view feature of JSwat is what makes single-stepping as productive as it is. Seeing the code while stepping through it is extremely valuable, and this feature needs as much attention to testing as any other. Use this checklist to test the source view.