Comment #6 on issue 24192 by [email protected]: Update chrome/http tests with accurate "expected results" http://code.google.com/p/chromium/issues/detail?id=24192
It's never been entirely clear, at least to me, what these chrome/http/mine/* tests were trying to do, nor what the expected results should be. They've been around forever, and never yet useful. On the other hand, the infrastructure is in place now to run http tests in the chrome/ directory too, so once we figure out what we want to see from them we can re-enable them before sending them upstream. I could also believe that the entire concept is flawed, and these tests will never have any point. But I don't know enough about what they're testing to say. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
