[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [jdt-ui-dev] Testing the Text/Java editor
|
Martin,
I've posted the test plan for first test pass last night.
The overall process is outlined at
http://www.eclipse.org/eclipse/freeze_plan_2_0.html
The lockdown testing is done manually based on a test plan with focus
areas. The areas
are assigned to team members. Ideally the same area is covered
by more than one member (excluding the owner of the code).
So if you want to particpate (which would be great!) then pls sign-up for a
focus area
and let me know and start file bugs in bugzilla.
If you have some spare time, then you could also help us verify
bugs that are marked as fixed but not yet verified. Bugs often have
interesting
scenarios in them that are worthwhile to redo and verify again.
--erich
Martin Mobius
<m.moebius@xxxxxx To: <jdt-ui-dev@xxxxxxxxxxx>
> cc:
Sent by: Subject: RE: [jdt-ui-dev] Testing the Text/Java editor
jdt-ui-dev-admin@
eclipse.org
05/23/2002 12:54
AM
Please respond to
jdt-ui-dev
Please add this and Adams message to the jdt-ui-dev site (if its not
already
there). I can not help with F1, but hopefully with F2.
Could someone describe the test process?
How are the test realized (manual, scripts, junit)?
How should the communication happen (here in the mailing list, bugzilla)?
martin
> 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
>
> _______________________________________________
> jdt-ui-dev mailing list
> jdt-ui-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
>
_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
