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

[Kai-Uwe_Maetzel@xxxxxxx]

The F2 test plan puts more emphasis on performance and the segmented view
compared to the F1 test plan.  This means that tester should pay special
attention to performance for whatever editor function they are testing.
Also, all tests should be executed in the segmented as well as the
unsegmented mode of the Class File and the Compilation Unit Editor.  Below
you find the complete F1 list with the necessary modifications for F2.

As in test pass F1, editor test assignments will be made within the Text
and the JDT UI team only. Everybody else is of course also invited.
Kai

--------------------

The components Text Editor and Java Editors will be tested regarding
functionality, appearance, accessibility, and performance. 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
Performance testing
      - test whether the functionality works exceptably fast for medium
size files.
      - test whether the functionality works in large files
      - test whether the performance penalty paid for the size increase is
exceptable compared to medium size files.


The following areas should be tested in the Text Editor, Class File Editor,
Compilation Unit Editor if available. Each of the listed areas should be
tested in each of the mentioned editors. For the Class File Editor and the
Compilation Unit Editor they should be tested in the unsegmented as well as
in the segmented view.

- 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 whether tab/space conversion works
      - 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)
- 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