I tried the tests again on trybot. Interestingly they ran without problem this time. Nothing changed except that the initial timeout of InProcessBrowserTest was increased from 30 seconds to 5 minutes. See: http://build.chromium.org/buildbot/try-server/builders/win/builds/17863/steps/browser_tests/logs/stdio
The EscapeToDefaultMatch is expected to fail, because I haven't submit the CL to fix this issue yet. Them I'm wondering if it's still true that trybot doesn't support such kind of interactive tests? Regards James Su 2009/9/11 James Su <[email protected]> > Good news. I'll try it tomorrow. Will interactive_ui_tests runs on trybot > (maybe in the future) ? > Regards > James Su > > 2009/9/11 Jay Campan <[email protected]> > > > Oh, I found it. So I'm wondering why not just move browser_focus_uitest >> into >> > browser_tests? Is it because the trybot limitation (no active desktop)? >> If >> > it's the case, then what should I do for my test? Moving it into >> > interactive_ui_tests is apparently not a right solution. >> >> Yes, the browser focus tests need an active desktop. >> I have just landed a change that makes interactive ui tests run like >> browser tests (on Windows only for now). >> This is not yet used by the build-bots or try bots but should be soon >> (probably tomorrow). >> That makes it OK to use any kind of tests (including >> IN_PROC_BROWSER_TEST) inside the interactive UI tests. >> Since you need to simulate keyboard events, interactive ui tests is >> where you want your tests. >> To add it to the new interactive ui tests, add them to the >> interactive_ui_tests_dll target in chrome.gyp. >> To run them, build the test_launcher project and run: >> test_launcher --lib=interactive_ui_tests_dll >> >> Jay >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
