Issue 2242: Accessibility UI tests should not use global
FindWindow/EnumWindows etc functions
http://code.google.com/p/chromium/issues/detail?id=2242
New issue report by [EMAIL PROTECTED]:
The accessibility UI test utils in accessibility_util.cc use global window
searching functions. This means these tests will be flaky when other Chrome
windows are open on the same computer. e.g. an engineer running the UI
tests may get unpredictable results because the UI test will connect to
his/her running _release_ build window instead of the test window!
The tests should use a function like EnumThreadWindows to enumerate only
the windows of the child process that was started.
Issue attributes:
Status: Assigned
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-Windows Area-BrowserUI
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
