Bug 129215 - performance tests that run too fast (< 100 ms)
Summary: performance tests that run too fast (< 100 ms)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.2 RC7   Edit
Assignee: Karice McIntyre CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance, test
Depends on:
Blocks:
 
Reported: 2006-02-23 14:53 EST by Karice McIntyre CLA
Modified: 2006-07-13 12:00 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karice McIntyre CLA 2006-02-23 14:53:43 EST 
The test org.eclipse.ui.tests.performance.EditorSwitchTest#testEditorSwitch:perf_basic,perf_outline()
is running in less than 100 ms on most of the test machines.  That's too fast.  Need to increase the length of time for which this test runs.

We may want to call BasicPerformanceTest.exercise(Runnable, int, int, int) instead of BasicPerformanceTest.exercise(Runnable) from the EditorSwitchTest instead.
Comment 1 Karice McIntyre CLA 2006-03-08 14:52:28 EST 
Tests that run in less than 100 ms: (as of 3.2 M5a)
*performance.EditorSwitchTest#testEditorSwitch:perf_basic,perf_outline()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.BookmarkView()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.ContentOutline()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.ProblemView()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.ProgressView()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.PropertySheet()
*performance.OpenCloseViewTest#showView:org.eclipse.ui.views.ResourceNavigator()
*performance.layout.ComputeSizeTest#Massively Recursive TrimLayout computeSize()
*performance.layout.ResizeTest#Presentation org.eclipse.ui.internal.presentations.R21PresentationFactory editor setSize()
*performance.layout.ResizeTest#Presentation org.eclipse.ui.presentations.WorkbenchPresentationFactory standalone without title setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.BookmarkView setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.ContentOutline setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.ProblemView setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.ProgressView setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.PropertySheet setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.ResourceNavigator setSize()
*performance.layout.ResizeTest#View org.eclipse.ui.views.TaskList setSize()
*rcp.performance.EmptyWorkbenchPerfTest#testOpen() [close]
*rcp.performance.EmptyWorkbenchPerfTest#testRestore() [close]
Comment 2 Karice McIntyre CLA 2006-04-05 12:23:14 EDT 
Shaun, were all of the tests that run too fast fixed?
Comment 3 Karice McIntyre CLA 2006-06-15 16:40:20 EDT 
All tests listed below but the rcp tests are running on the order of 100ms or greater.
Comment 4 Karice McIntyre CLA 2006-07-13 12:00:58 EDT 
resolving this bug as fixed against 3.2 since bug 116284 and bug 116282 cover the problems with the rcp tests running too fast.