Allow forcing TestWebServer to use a specific port number.
Commit c4a3f88c ("TestWebServer needs to use a free port") has caused TestWebServer to use a random port number in each invocation. This does not play well with tests that assume the server will be running on a specific port (for example, an HTML asset trying to do XHR whose contents cannot be changed at runtime). start() and startSsl() can now be passed an optional port number; if it is being used, the server will fail to start like it did before the commit mentioned above. R=hush@chromium.org, yfriedman@chromium.org Review URL: https://codereview.chromium.org/666513002 Cr-Commit-Position: refs/heads/master@{#300151}
Showing
Please register or sign in to comment