Jump to: navigation, search

Difference between revisions of "Equinox Performance Notes"

(New page: ==Significant Dates in History== * November 2006 - The JARs in the SDK were signed * February 2007 - The test framework was changed and the new one doesn't call -dev bin. * ?? - class load...)
 
(Notes)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==Significant Dates in History==
 
==Significant Dates in History==
* November 2006 - The JARs in the SDK were signed
+
* I20061107-0800 - The JARs in the SDK were signed. Previous I-build (M3 or I20061102-1715) is unsigned.
* February 2007 - The test framework was changed and the new one doesn't call -dev bin.
+
* On or after 20070217 - The updated test framework was used in performance tests. The new one doesn't add "-dev bin". (Which is a good thing.)
 
* ?? - class loader boot delegation was changed
 
* ?? - class loader boot delegation was changed
  
Line 7: Line 7:
 
* We need to ensure that JARs are signed (or not signed) in both the new tests and the baselines
 
* We need to ensure that JARs are signed (or not signed) in both the new tests and the baselines
 
* Potential factors in UI Application startup tests
 
* Potential factors in UI Application startup tests
** In 3.2 the SDK's default perspective was the Resource Perspective and in 3.3 it is the Java perspective
+
** In 3.2 the SDK's default perspective was the Resource Perspective and in 3.3 it is the Java perspective (Note: This is <strong>NOT</strong> true...it was changed earlier. Will leave this note so we don't forget and go down this path again)
** The Welcome screen is also opened in the UI App startup test
+
** The Welcome screen is also opened in the UI App startup test - can we suppress this?
  
  
[Category:Equinox]
+
[[Category:Equinox]]

Latest revision as of 11:03, 13 April 2007

Significant Dates in History

  • I20061107-0800 - The JARs in the SDK were signed. Previous I-build (M3 or I20061102-1715) is unsigned.
  • On or after 20070217 - The updated test framework was used in performance tests. The new one doesn't add "-dev bin". (Which is a good thing.)
  •  ?? - class loader boot delegation was changed

Notes

  • We need to ensure that JARs are signed (or not signed) in both the new tests and the baselines
  • Potential factors in UI Application startup tests
    • In 3.2 the SDK's default perspective was the Resource Perspective and in 3.3 it is the Java perspective (Note: This is NOT true...it was changed earlier. Will leave this note so we don't forget and go down this path again)
    • The Welcome screen is also opened in the UI App startup test - can we suppress this?