Support for process-wide incidents in the safe browsing incident reporting service.

chrome/browser/safe_browsing/incident_reporting_service_unittest.cc

Index: chrome/browser/safe_browsing/incident_reporting_service_unittest.cc
diff --git a/chrome/browser/safe_browsing/incident_reporting_service_unittest.cc b/chrome/browser/safe_browsing/incident_reporting_service_unittest.cc
index d3dcc190d1fa72737cd0d23ae684293c0e715d50..2439ed91c85bb53112fd42cc652f9f589867e011 100644
--- a/chrome/browser/safe_browsing/incident_reporting_service_unittest.cc
+++ b/chrome/browser/safe_browsing/incident_reporting_service_unittest.cc
@@ -680,6 +680,19 @@ TEST_F(IncidentReportingServiceTest, MigrateOldPref) {
   AssertNoUpload();
 }
 
+// Tests that no upload results from adding an incident that is not affiliated
+// with a profile.

[robertshield, 2014/08/04 01:35:12]

Is this true only if no other opted-in profile exists? If so, consider adding
the same test except that an opted-in profile is created first. In that case (if
I understand correctly) the incident should be associated to that opted-in
profile and an upload should occur?

[grt (UTC plus 2), 2014/08/04 14:15:33]

Yes.

+TEST_F(IncidentReportingServiceTest, ProcessWideNoProfileNoUpload) {
+  // Add the test incident.
+  AddTestIncident(NULL);
+
+  // Let all tasks run.
+  task_runner_->RunUntilIdle();
+
+  // No upload should have taken place.
+  AssertNoUpload();
+}
+
 // Parallel uploads
 // Shutdown during processing
 // environment colection taking longer than incident delay timer