Bug 13769 - run-webkit-tests or DumpRenderTree needs to be able to capture httpd logs
Summary: run-webkit-tests or DumpRenderTree needs to be able to capture httpd logs
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-18 00:53 PDT by Brady Eidson
Modified: 2011-05-26 10:24 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brady Eidson 2007-05-18 00:53:28 PDT
run-webkit-tests or DumpRenderTree needs to be able to capture httpd logs.

There are some cases we would like to test regarding network connections where the connection is made to the server but doesn't persist long enough to provide any delegate calls we could otherwise capture in DRT.
Comment 1 Adam Roben (:aroben) 2011-05-26 09:47:21 PDT
Brady, are you asking for something here beyond the log support we already have? access.log and error.log are put into the layout-test-results directory and linked to from results.html. Maybe you're asking to have per-test log output and be able to include it in the expected results?
Comment 2 Brady Eidson 2011-05-26 10:24:32 PDT
(In reply to comment #1)
> Brady, are you asking for something here beyond the log support we already have? access.log and error.log are put into the layout-test-results directory and linked to from results.html. Maybe you're asking to have per-test log output and be able to include it in the expected results?

Having filed the bug over 4 years ago, I don't remember what my original use case was  :)

But I think now (and probably thought then) that it would be useful to actually capture HTTP traffic in DRT and be able to include it individual test output.  Either built in to DRT like "layoutTestController.dumpHTTPTraffic()" or some callbacks to the page so it can integrate HTTP traffic into the DOM directly.

Of course the traffic would have to be formatted somehow so it would look the same across test runs, like we do with certain URLs, etc.