Closed Bug 386372 Opened 17 years ago Closed 14 years ago

need an automated test for testing keynav performance in the browser

Categories

(Testing :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rcampbell, Unassigned)

References

Details

(Keywords: perf)

It was noted on trunk that keynav performance on Linux seemed slower in some recent builds on Google Calendar. (see bug 379843 for details) After a discussion in IRC with Mike Pedersen, we suggested a small testing tool to simulate and time  keystrokes as part of our performance testing toolkit.
Component: Testing → Release Engineering: Future
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
robcee: is this covered by mozmill?  Do we still want this test?
I'm not sure, but I suspect it could. You'd have to ask the mozmill crew.
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Henrik: does Mozmill have any tests like this?
We do not have performance tests in Mozmill yet. While it should be technical possible we do not have a web ui to display times and do any comparisons of those like what is possible with Talos.

If existing frameworks cannot handle performance tests on external web sites we should think about adding this as a basic feature to Mozmill.
found in triage. 

aiui, this looks like its waiting for test to be written - pushing over to QA.
Component: Release Engineering → General
Product: mozilla.org → Core
QA Contact: release → general
Version: other → unspecified
you missed!
Component: General → New Frameworks
Product: Core → Testing
QA Contact: general → new-frameworks
on further reflection, I'm not even sure I understand this bug anymore. What does "keynav performance mean?" Keyboard Navigation in Google calendar could refer to the keyboard shortcuts or back and forward navigation using the keyboard.

I'm going to close as invalid.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Component: New Frameworks → General
You need to log in before you can comment on or make changes to this bug.