Difference between revisions of "JDKUpdateTesting"

Revision as of 05:38, 27 April 2018

Once a new version of JDK x.y is released ( major version x) , we must test for the following things.

General

• 1) Ensure that there are no default JDK installed on the machine
• 2) Launch eclipse with the JDK x . Once launched ensure that in the preference Java-> Installed JREs , JDK x is selected.

• 3) On the launched eclipse, check the following.

a) Look at error log.
b) Ensure compiler compliance is x.
c) Create a sample java project with JavaSE-x EE.
d) Compile your repository plugins. 
e) Ensure compliance level for compiler is x and compile.
f) Change compliance level for compiler to x-1 and compile.
g) Also check c,d, e and f with java project created with JavaSE-(x-1) or whichever is the previous major java release.

• 4 Launch debug configuration and see if the debug launch is successful. Check 3a) to 3g).
• 5 Launch run configuration and see if the run launch is successful. Repeat steps 3a) to 3g)

• 6) Ensure JDK x is the default JDK installed on the machine and repeat 1 to 5.
• 7) Ensure JDK x-1 ( or previous major release version) is default JDK and repeat 1 to 5).
• 8) Ensure both JDK x and JDK (x-1) are present in installed JRE and then launch eclipse using JDK x (steps 3a) to 3g)
• 9) Ensure both JDK x and JDK (x-1) are present in installed JRE and then launch eclipse using JDK x-1 (steps 3a) to 3g)

JDT Core

• Look for new command line option in new javac
• TODO

JDT Debug

• Access rules applicable for the JDK should be tested.
• Inspection & Hover of local variables and parameters should be tested.
• Watchpoints, Exception breakpoints and other breakpoint types should be tested.

JDT UI

• Launch JUnit 5 and JUnit 4 tests with the new JDK.
• Launch both types of tests by placing the JUnit container in classpath and modulepath respectively.
• Launch all the above combinations in a project having module-info.java file and without that file.
• Launch all the above combinations by placing tests in source folder and then in test folder.

PDE

• Create system packages list using Java x and update org.eclipse.pde.api.tools\system_packages\JavaSE-x-systempackages.profile
• Update ASM if required
• Run PDE UI as well as API tools test with just Java x present in installed JRE
• Launching is covered in "General" section

PERFORMANCE

1) Put no baseline ( Put missing baseline as IGNORE) and run full build on a sample set of projects with only Java x in installed JRE
2) Put no baseline ( Put missing baseline as IGNORE) and run full build on a sample set of projects with only Java x-1 in installed JRE

• Compare timings of 1) and 2)

3) Put API baseline ( Put missing baseline as ERROR) and run full build on a sample set of projects with only Java x in installed JRE
4) Put API baseline ( Put missing baseline as ERROR) and run full build on a sample set of projects with only Java x-1 in installed JRE

• Compare timings of 3) and 4)

Misc

• TODO