[platform-ui-dev] Testing the Text/Java editor

[Kai-Uwe_Maetzel@xxxxxxx]

The components Text Editor and Java Editor will be tested regarding
functionality, appearance, and accessibility. The tests focus on:

Functional testing
      - test whether functionality works at all
      - try to find reproducible cases in which the function fails
Appearance testing
      - test the look (colors, action feedback)
      - try to reproducibly create screen cheese
Accessibility testing
      - test mnemonics
      - test short cuts
      - test combination of color, form, text, and sound feedback
      - test adjustability (Is it possible to adjust colors, font, size,
etc. to go together with several window schemes.)
      - test status line information


The following areas should be tested in the Text Editor, Class File Editor,
Compilation Unit Editor if available.

- error indication
      - compile time problems
      - temporary problems
      - combination of both
      - fixed problems
      - "quick fix"-able problems
- go to next/previous problem
- encoding
- handling of read- only files
      - try to find cases in which read only files can be modified
- bracket matching
- print margin indication
- current line highlighting
- overview ruler
- vertical ruler
      - floating annotations
      - update of annotations
      - collaboration with revert
- line numbers
- preferences
      - enable/disable all preferences defined for the editors
      - test the template preference page (define/enable/edit templates)
      - test collaboration between platform and JDT preferences
- code assist and parameter hints
      - proposal ordering
      - template proposal ordering
      - filtering
      - life cycle
      - templates
- syntax highlighting
- structure reconciling
- hover help (mouse hover, F2)
- segmented view
- action retargeting between editor and outliner
- editor interaction with the task list
      - go to editor from the task list
- editor context menu
- vertical ruler context menu
      - action enabling/disabling
      - action target/result
      - accessibility
- text actions
      - mark
      - delete line
      - shift
      - line delimiter conversion
      - comment/uncomment
      - go to line
      - standard text actions such as cut/copy/paste/select
all/save/revert/undo/....
- find/replace
      - find/replace
      - find next
      - find previous
      - incremental find
- class file editor
      - test read only state
      - with source attachment
      - without source attachment
      - test attaching of source by using the property page and the editor
form

Assignments for the above  will be made within the Text and the JDT UI team
only. If somebody likes to join us, this would simply be great.
Kai