Mars M4 Test Plan
Testing day: Tuesday 2014-12-09
Test Build: latest available I-build
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers:
Noopur,
Markus,
Dani
Setup
Builds
- 4.4.2 build: everybody
- 4.5 build: everybody
Platforms
- Windows 7: Markus, Dani
- Linux-GTK: Noopur, Dani
- Mac OS X 10.10: Markus
Goal
- test new functionality added since 4.5 M3
- verify that severe bugs are correctly fixed
- verify that all 4.4.2 bugs are correctly fixed
Test New Functionality
Note: First test the items where your name is listed first. Then test the other items.
Separate preference for "Unused exception parameter" (Dani, Noopur - Questions: Markus)
Detection for unused exception parameters has been added in an early 4.5 milestone.
Initially, it was controlled by the "Unused method parameter" option, but for 4.5 M4,
a separate option has been introduced.
- verify that no unused exception parameters are reported if only "Unused method parameter" is set to "Warning"
- verify that the new option works
Custom code formatter implementations (Noopur, Markus - Questions: Markus)
- verify that the code formatter preference page looks and works as in the past
- write a plug-in that contributes to the
org.eclipse.jdt.core.javaFormatter extension point
- verify that the code formatter preference page now shows an option to choose the formatter implementation
- verify that the toggling works and your formatter is used
- verify for workspace- and project-specific preferences
Links in Javadoc hovers/view (Noopur, Dani - Questions: Markus)
- verify that links in Javadoc hovers still work after bug 431768 (see steps in comment 21)
- verify that links still work if Javadoc is not inherited
- verify that links still work if Javadoc is extracted from source
JUnit view supports re-running parameterized tests (Markus, Noopur - Questions: Markus)
- use Moritz' blog post
as inspiration and try to break the added features, e.g. by using a custom test runner
4.4.2 Bug Verification (All)
Before starting to verify a bug add a comment indicating that you are about to verify it.
4.5 Bug Verification (All)
Before starting to verify a bug add a comment indicating that you are about to verify it.
Sanity Check The Build (All)
Sanity check the build by using it for development (either on "real" code or your pet project).