Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "JDKUpdateTesting"

(JDT Core)
(JDT Core)
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Once a new version of JDK x.y is released ( major version x) , we must test for the following things.
 
Once a new version of JDK x.y is released ( major version x) , we must test for the following things.
 +
<b>Ensure that the latest release candidate JDK is taken for testing.</b>
  
 
== General  ==
 
== General  ==
* 1 Ensure that there are no default JDK installed on the machine
+
* 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.
+
* 2) Launch eclipse with the JDK x . Once launched ensure that in the preference Java-> Installed JREs , JDK x is selected.
  
* 3 Launch debug configuration and see if the debug launch is successful
+
* 3) On the launched eclipse, check the following.
  a) look at error log
+
  a) Look at error log.
  b) Ensure compiler compliance is x
+
  b) Ensure compiler compliance is x.
  c) create a sample java project with JavaSE-x EE
+
  c) Create a sample java project with JavaSE-x EE.
  d) compile your repository plugins  
+
  d) Compile your repository plugins.
  e) ensure compliance level for compiler is x
+
  e) Ensure compliance level for compiler is x and compile.
  f) change compliance level for compiler to x-1  
+
  f) Change compliance level for compiler to x-1 and compile.
  g) also check c,d and e with java project created with JavaSE-(x-1) or whichever is the previous major java release
+
  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 run configuration and see if the run launch is successful  
+
* 4 Launch debug configuration and see if the debug launch is successful. Check 3a) to 3g).
Repeat steps 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)
  
* 5) Ensure JDK x is the default JDK installed on the machine and repeat 1 to 4
 
* 6) Ensure JDK x-1 ( or previous major release version) is default JDK and repeat 1 to 4.
 
* 7) Ensure both JDK x and JDK x-1 are present in installed JRE and then launch using JDK x (steps 3a) to 3g)
 
* 8) Ensure both JDK x and JDK x-1 are present in installed JRE and then launch using JDK x-1 (steps 3a) to 3g)
 
 
 
 
== JDT Core ==
 
== JDT Core ==
 
* Look for new command line option in new javac
 
* Look for new command line option in new javac
 +
* try out examples from the examples wiki  for eg for Java 14 - https://wiki.eclipse.org/Java14/Examples
  
 
== JDT Debug ==
 
== JDT Debug ==
* TO DO
+
* 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 ==
 
== JDT UI ==
* TODO
+
* 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 ==
 
== PDE ==
* Add EE descriptions for Java x. See {{bug|527360}} for example.
+
* Create system packages list using Java x and update org.eclipse.pde.api.tools\system_packages\JavaSE-x-systempackages.profile
 
* Update ASM if required  
 
* Update ASM if required  
 
* Run PDE UI as well as API tools test with just Java x present in installed JRE
 
* Run PDE UI as well as API tools test with just Java x present in installed JRE
 
* Launching is covered in "General" section
 
* Launching is covered in "General" section
 +
* Check https://bugs.eclipse.org/bugs/show_bug.cgi?id=541307 for Java x
 +
* check if export plugin works ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=544038)
 +
* check if no illegal argument exception ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=537282)
 +
 +
== 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==
 
== Misc==
 
*TODO
 
*TODO

Latest revision as of 10:06, 16 March 2020

Once a new version of JDK x.y is released ( major version x) , we must test for the following things. Ensure that the latest release candidate JDK is taken for testing.

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

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

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

Back to the top