Neon Two Day Test Pass

Testing days: Monday, 2016-05-02 and Tuesday 2016-05-03
Test Build: Declared 4.6 M7 build
Testers: Noopur, Markus and Dani

Setup

Platforms

Workbench Setup

Use the Java editor breadcrumb whenever possible. Each new bug must state whether it is a regression or not.

New Neon Functionality (All)

Test all (not just JDT!) new features that have been added during Neon development. This can be done by testing the features mentioned in the M1-M7, see M7 New and Noteworthy as an entry point.

Test all new advertised features

Smoke Test (Markus, Noopur)

Peform the {JDT/UI, Text, Search} Smoke Test. Note that the test script may be a bit out of date, since we don't run this regularly any more. Simply update the script when you find outdated stuff.

Views and Editors (Dani)

Workspace and Project Setup (Markus)

Setup workspaces and projects in ways unusual compared to your normal setup. Test the following workspace and project setups:

Workspace Compatibility (Noopur)

Verify that an existing workspace can be started on the new version and is fully functional. Also verify that preferences exported with an older workspace can be imported and work. Check the .log for serious problems.
Verify that projects created and checked into a repository with an older version can be checked out with Neon.

About Info (Dani)

Verify that all plug-ins and features appear correctly in the About dialog:

Freestyle Testing (All)

Once all of the above test items are done, start with a fresh workspace and change the settings in a way you normally don't work.

Implement a little feature or tool or create a patch for one of your favorite bugs. Use refactorings and UI gestures you don't normally use.