**installing something like EGit that should cause the welcome to re-appear

+

−

+

−

* Accessibility. There have been numerous changes through the SDK in all components that could severely hamper accessibility.

+

−

** High contrast

+

−

** Screen reader

+

−

+

−

* New problems, markers, bookmarks and tasks view. The problems view has been replaced and is ready for general testing. Concentrate on

+

−

** All markers view

+

−

** sorting and filtering

+

−

** command enablement

+

−

+

−

* Commands.

+

−

+

−

* Contributions

+

−

** The new Customize Perspective Dialog

+

−

+

−

* Decorators

+

−

** there have been a series of optimizations to decorator creation.

+

−

***Look out for disposed widgets as a result of opening and closing views

+

−

***confirm all decorations occur as expected

+

−

** files should decorate with icons for the appropriate content type. This often will show itself with XML files. Try defining XML files of various types and ensure that they have the correct icon. Note any performance hits for this operation

+

−

+

−

* RCP - the ide now has several optional plug-ins. Try making RCP apps with the ide and no optional plug-ins.

+

−

+

−

* IDE - ensure that external modification followed by a refresh (F5) works as expected

+

−

+

−

* Progress

+

−

** check for multiple instances of the same job

+

−

** confirm canceling works

+

−

** confirm correct sort order

+

−

** run in background preference should be tied to the Always Run In Background in the Progress Dialog

+

−

** check the layout of all progress dialogs

+

−

+

−

* Graphics

+

−

**check for graphics that need to be updated

+

−

+

−

Also see the [[http://dev.eclipse.org/viewcvs/index.cgi/platform-ui-home/testfix/componentAreaTesting.html?view=co Component Test Areas]] plan. The current owners of the components is actually described in [[http://www.eclipse.org/eclipse/platform-ui/componentAreas.php Component Areas]], but the suggestions of what to test are good.