Add Finch testing configs for ReportCertificateErrors study

chrome/browser/ssl/certificate_reporting_test_utils.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/ssl/certificate_reporting_test_utils.h"
 
 #include "base/bind.h"
 #include "base/bind_helpers.h"
 #include "base/metrics/field_trial.h"
 #include "base/prefs/pref_service.h"
 #include "base/run_loop.h"
+#include "base/strings/string_number_conversions.h"
 #include "chrome/browser/browser_process.h"
 #include "chrome/browser/profiles/profile.h"
 #include "chrome/browser/safe_browsing/ping_manager.h"
 #include "chrome/browser/safe_browsing/safe_browsing_service.h"
 #include "chrome/browser/safe_browsing/ui_manager.h"
 #include "chrome/browser/ssl/cert_report_helper.h"
 #include "chrome/browser/ssl/certificate_error_report.h"
 #include "chrome/browser/ssl/ssl_cert_reporter.h"
 #include "chrome/browser/ui/browser.h"
 #include "chrome/common/pref_names.h"
@@ skipping 134 matching lines @@
     return nullptr;
 
   scoped_ptr<MockSSLCertReporter> ssl_cert_reporter(new MockSSLCertReporter(
       sb_service->ui_manager(), expect_report == CERT_REPORT_EXPECTED
                                     ? run_loop->QuitClosure()
                                     : base::Bind(&base::DoNothing)));
   ssl_cert_reporter->set_expect_report(expect_report == CERT_REPORT_EXPECTED);
   return ssl_cert_reporter.Pass();
 }
 
-// Helper function to set the Finch options.
-void SetCertReportingFinchConfig(const std::string& group_name,
-                                 const std::string& param_value) {
-  base::FieldTrialList::CreateFieldTrial(CertReportHelper::kFinchExperimentName,
-                                         group_name);
-  if (!param_value.empty()) {
-    std::map<std::string, std::string> params;
-    params[CertReportHelper::kFinchParamName] = param_value;
-    variations::AssociateVariationParams(CertReportHelper::kFinchExperimentName,
-                                         group_name, params);
+ExpectReport GetReportExpectedFromFinch() {
+  const std::string group_name = base::FieldTrialList::FindFullName(
+      CertReportHelper::kFinchExperimentName);
+
+  if (group_name == CertReportHelper::kFinchGroupShowPossiblySend) {
+    const std::string param = variations::GetVariationParamValue(
+        CertReportHelper::kFinchExperimentName,
+        CertReportHelper::kFinchParamName);
+    double sendingThreshold;
+    if (!base::StringToDouble(param, &sendingThreshold))
+      return CERT_REPORT_NOT_EXPECTED;
+
+    if (sendingThreshold == 1.0)

[meacer, 2015/07/21 06:04:31]

You might want to compare sendingThreshold against a slightly lower value such
as 1.0-epsilon here

[estark, 2015/07/21 14:50:09]

I was actually hoping to try to discourage Finch configs that result in
non-deterministic behavior. Another alternative might be to check if the value
is between 0 and 1 (exclusive) and if so fail the test?

[meacer, 2015/07/21 17:36:25]

Not sure if that check would be reliable either, but I don't see why it wouldn't
be.

Of course the other option is to let this go through and see if the tests fail
at all on trybots (they probably won't?)

+      return CertificateReportingTestUtils::CERT_REPORT_EXPECTED;
   }
-}
-
-// Helper function to set the Finch options in case we have no parameter.
-void SetCertReportingFinchConfig(const std::string& group_name) {
-  SetCertReportingFinchConfig(group_name, std::string());
+  return CertificateReportingTestUtils::CERT_REPORT_NOT_EXPECTED;
 }
 
 }  // namespace CertificateReportingTestUtils