Bug 109443

Summary: Web Inspector: [Extensions API] expose ExtensionServerClient to tests so tests use same port as extensions API
Product: WebKit Reporter: Andrey Kosyakov <caseq>
Component: Web Inspector (Deprecated)Assignee: Andrey Kosyakov <caseq>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, keishi, loislo, pfeldman, pmuellr, vsevik, web-inspector-bugs, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch vsevik: review+

Description Andrey Kosyakov 2013-02-11 08:39:12 PST
We currently have a separate message channel for evals in front-end context invoked from extension tests. This has negative impact on tests stability, as the message delivery order is not guaranteed for two different ports -- the extension output interleaving with front-end output (i.e. from console.log()) is a common source of flakiness. The proposed fix is to expose extensionServer to test code, so we can re-use the existing port and make sure test output is well serialized WRT extension commands.
Comment 1 Andrey Kosyakov 2013-02-11 08:42:50 PST
Created attachment 187580 [details]
Patch
Comment 2 Andrey Kosyakov 2013-02-11 10:02:59 PST
Committed r142485: <http://trac.webkit.org/changeset/142485>