Google has expressed interest in having us run tests against their safe browsing test server. Separately from integrating it into the normal unit test process (which I've filed bug 502932 on), they're also interested in having some sort of test run that downloads the latest version of the server, runs tests against it, and sends the results back to Google. This would make it easy for them to find out if server-side changes they're making will break our safe browsing implementation. (Filing this directly in Future since we don't have the details hashed out yet.)
Ted any updates on this?
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
(In reply to comment #0) > (Filing this directly in Future since we don't have the details hashed out > yet.) (In reply to comment #2) > bug 509813 has some details. Ted, is this still something that we still want to do? Have the details been hashed out?
Marking this bug as resolved->incomplete because we don't have details on what to implement yet. Lets file a new bug when we get these details
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
This is still something we want to do. I'm no longer working on this, but bryner and gcasto should have the details for you.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.