The preceeding sections on 1 Hacking Guidelines,Eclipse House Rules and 2 User Interface Guidelines may be a little bit abstract. Here is the results of apply those guidelines into an actual Quality Assurance Checklist for the UDIGImportPage.
Check |
Load Data |
|
listed in the "Add Layer" and "Data Import" wizards |
|
banner and a title |
|
starts with a prompt (not an error message) |
|
tab order as fields are filled in |
|
test if data is loaded correctly |
|
test that new content is selected (in layer or catalog view) |
Check |
Context and Error |
|
starts with fields based on workspace context (ie the data we just loaded) |
|
restart page and check that history is remembered |
|
fill out the fields incorrectly and check reporting of error messages |
Check |
DnD |
|
DnD with appropriate URL (check of canProcess method) |
Check |
Help and Internationalization |
|
Check for presense of online reference page for this wizard |
|
Press F1 and (or click on the ?) for context sensitive help |
|
Restart and run tests with French |
- Workspace context is based on IDataWizard.getSelection().
- History is maintained in Dialog settings and is remembered across runs (See 3 Adding History to Dialogs and Wizards)
- Steal an existing wizban image and modify
- jdbc urls are not "valid" urls, see the jdbc trail and are not usual done using DND
- Turn on all warnings as in enironment setup
- Classes have at minimum a javadoc comment
- Strings should be externalized for internationalization
|