Eclipse4.1/TestPlan

Test Plan

This page contains information for testing the RC candidates for the Eclipse 4.1 SDK. If you encounter any issues get in touch with Eric, Paul or Remy before creating a defect and we'll take the appropriate action (this will save both of us time, which is a commodity in short supply...;-).

Please take a look at the Known Issues wiki page so you can see what we already know about the current state of the SDK.

We're really testing at this point for two things:

• Completeness: The 4.1 SDK should be functionally equivalent to 3.7. Use the SDK to do you regular development work...anything that results in a loss of functionality is a serious defect. The most likely candidates would be menu or toolbar items that are either missing or inactive under circumstances where they'd be available in 3.7 but we have experienced cases where a particular view (i.e. the Variables & Breakpoints views) where the contents of the views are not shown when they should be.

• Robustness: Under regular use there should be no errors generated to the log file and you should never see the 'Error Dialog'. The most worrisome situation is that we have in the past been able to get the UI Model into states where it becomes internally corrupt, leading to the SDK becoming unusable (i.e. almost any operation results in an Error Dialog, in the worst cases this includes attempts to Restart / Exit). Please run your eclipse session with the -consolelog option and ensure that there are no uncaught exceptions being thrown.

General Testing

While using the SDK try changing up your standard workflows:

• Play with the drag and drop. This is an area where we have experienced issues, especially when using the newly available functionality of being able to drag editors into view stacks or detached windows. Also, try dragging views and/or view stacks into the Editor Area as well as moving them back out.
• Open perspectives you might not normally use and play with them. Once you've tinkered for a while ensure that the 'Reset Perspective' reliably gets you back to a good state.

NOTE: The current behavior of the UI when dragging a view into the shared area needs some explanation (this will eventually go into the 4.1 SDK docs ;-). Since we cannot show a view in two places at once if you move a view into the shared area it should automatically be hidden in any other perspectives. If you drag it back out again it is NOT expected to re-appear in the other perspectives but re-opening it should result in the view appearing in it's regular location.

Install Testing

Since the initial exposure of most folks to the new SDK will be the various release train components installing their code on top of 4.1 and testing it we must be sure that this path is working correctly. If you normally extend your eclipse install (i.e. SWT Tools...) then ensure that this works correctly.