Enable automated mouse cursor tests on more ports 
https://bugs.webkit.org/show_bug.cgi?id=101225
Summary Enable automated mouse cursor tests on more ports
Rick Byers
Reported 2012-11-05 08:38:40 PST
In bug 100550 some automated tests were added (fast/events/mouse-cursor.html) for testing mouse cursor behavior, and more tests will follow using the same infrastructure. These tests rely on a 'testRunner.getCurrentCursorInfo' API which needs to be added to each port that wants to use these tests (currently only chromium has it). This bug tracks adding the getCurrentCursorInfo API to the other ports and unskipping the mouse-cursor tests on that port (port-specific bugs can be filed for each port as desired).
Attachments
Add attachment proposed patch, testcase, etc.
Rick Byers
Comment 1 2012-11-08 12:40:41 PST
I changed the test infrastructure work on all ports that define USE(LAZY_NATIVE_CURSOR) - i.e. Mac, Win, GTK, QT and EFL. Chromium will get this soon in bug 101501. I think (but I'm not sure) that leaves only BLACKBERRY and WX, neither of which appear to have TestExpectations files in the tree. Antonio, any idea if blackberry will want this, and if I should be listing the test as failing on blackberry somewhere? Malcolm, looks like you recently did cursor work for WX - what about that port?
Antonio Gomes
Comment 2 2012-11-09 05:57:59 PST
m(In reply to comment #1) > I changed the test infrastructure work on all ports that define USE(LAZY_NATIVE_CURSOR) - i.e. Mac, Win, GTK, QT and EFL. > > Chromium will get this soon in bug 101501. > > I think (but I'm not sure) that leaves only BLACKBERRY and WX, neither of which appear to have TestExpectations files in the tree. > > Antonio, any idea if blackberry will want this, and if I should be listing the test as failing on blackberry somewhere? > > Malcolm, looks like you recently did cursor work for WX - what about that port? mike?
Note You need to log in before you can comment on or make changes to this bug.