-
Notifications
You must be signed in to change notification settings - Fork 0
Proposed Changes from Testing
NB: This document is a work in progress...
Right now a large portion of the code is coupled with Swing way too tightly. Classes (especially those listed in com.jbrickx.swing.actions) need to be abstracted away from the GUI, such that they can be tested and run without the swing interface. Possible offenders:
- com.jbricx.swing.actions
There is obvious Lava flow in many of the classes. This includes code that is commented out that is no longer being used, code that is commented as never occurring, but has no details on why, or code that simply has no comments. Classes should combed over and code should be marked for review. Possible offenders:
- com.jbricx.help/CustomTree
- com.jbricx.help/HelpBrowser
- com.jbricx.pjo/ActionControlClass
-
The "MyTest" folder under tests
Right now the AutomationTests provide a fairly comprehensive implementation of most of the tests described in the google docs testing sheet. There are however some tests which we can not complete, including many which involve pop-ups, or audio validation. Grabbing some elements (such as the directories listed in the file viewer) or private elements in the software classes is seemingly impossible. If these automated tests are to become fully comprehensive, it might be worth looking into a framework or tool which is made to do this kind of testing....