Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JDKUpdateTesting"
Line 38: | Line 38: | ||
== PERFORMANCE== | == 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 | 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 | in installed JRE | ||
− | |||
− | * 3) Put API baseline ( Put missing baseline as ERROR) and run full build on a sample set of projects with only Java x | + | *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 | 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 | in installed JRE | ||
− | Compare timings of 3) and 4) | + | |
+ | *Compare timings of 3) and 4) | ||
*TODO | *TODO | ||
== Misc== | == Misc== | ||
*TODO | *TODO |
Revision as of 05:19, 15 February 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
JDT Debug
- TO DO
JDT UI
- TODO
PDE
- Add EE descriptions for Java x. See bug 527360 for example.
- 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)
- TODO
Misc
- TODO