I think it should only be allowed in tests that use a launcher which will properly isolate test cases. Currently interactive_ui_tests use in-proc tests. To make transition easier, I'm going to allow in-proc in them, but try to get rid of it finally (or make the launcher safer).
On Tue, Aug 25, 2009 at 16:36, Evan Stade <[email protected]> wrote: > On Tue, Aug 25, 2009 at 4:15 PM, Paweł Hajdan > Jr.<[email protected]> wrote: > > On Tue, Aug 25, 2009 at 16:08, Evan Stade <[email protected]> wrote: > >> > >> uh, for which binaries are in proc browser tests allowed? I know there > >> is one in interactive_ui_tests and it was causing problems (which > >> caused me to go and use the code to not use statics). > >> BrowserFocusUITests was the one. > > > > For now they're allowed for all binaries, but that's bad and I'm going to > > change that. > > right, by allowed I mean "should be allowed" > > > > >> > >> Also, and I am to blame for this one, view_id_util_unittest.cc is an > >> in-proc browser test running on unit_tests right now. > > > > It's now being changed on the trunk. > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
