On Sat, Dec 19, 2009 at 02:25, Drew Wilson <atwil...@chromium.org> wrote:
> Is there another way to do it? Perhaps ui_test should register its own
> NotificationObserver with the AutomationProvider framework? Or is that a
> bogus approach?
I'd really suggest starting with a browser_test instead. It's much
easier to write a test that way, and much easier to change things
around, so you're more likely to find a correct and simple way. Then
you can port it to ui_tests (which generally adds complexity, but
isn't as hard) if you want a bigger test.
Generally using NotificationObservers to wait for things is a good sign. :)
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
