Cpp bindings: Return false from Validator::Accept() on unrecognized message or invalid flags

mojo/public/cpp/bindings/tests/validation_unittest.cc

Index: mojo/public/cpp/bindings/tests/validation_unittest.cc
diff --git a/mojo/public/cpp/bindings/tests/validation_unittest.cc b/mojo/public/cpp/bindings/tests/validation_unittest.cc
index 8139fe433efebde88306aab20271e0e1b1aeea50..750a54e5e11fac81487d9eaa991e666d2a412a56 100644
--- a/mojo/public/cpp/bindings/tests/validation_unittest.cc
+++ b/mojo/public/cpp/bindings/tests/validation_unittest.cc
@@ -371,6 +371,16 @@ TEST_F(ValidationTest, Conformance) {
   RunValidationTests("conformance_", validators.GetHead());
 }
 
+// This test is similar to the Conformance test but for responses.

[yzshen1, 2015/03/13 22:55:03]

"Conformance" means "all binding implementations need to pass these tests to
claim that they conform to the validation algorithm".
"Response" sounds like a different way of categorizing tests. But these tests
are still conformance tests.

One idea is to use conformance_rqst_ (request) and conformance_resp_ (response)
as prefix.

Another issue: I am pretty sure that other language bindings won't run these
test cases (unless you make similar changes) because they use prefix to filter
tests as well.

[rudominer, 2015/03/16 21:24:31]

I have settled on the "conformance_" prefix for the current request-oriented
tests and "resp_conformance_" prefix for the response-oriented tests. Notice
that there is no real advantage to having the two sets of files have a common
prefix because in every language we need to have the testing code treat the two
sets differently because they use different interfaces. In other words if we
were to use "conformance_req_" and "conformance_resp_" as the prefixes, that
would involve a lot of work to change the existing file names but no real
advantage because the tests would then no longer be able to look for the prefix
"conformance_" but would have to start looking for the two prefixes
conformance_req_" and conformance_resp" separately.
Right and that is good for now since the tests would break and we would have to
exclude them as we have done with the JS test.

+TEST_F(ValidationTest, Response) {
+  DummyMessageReceiver dummy_receiver;
+  mojo::internal::FilterChain validators(&dummy_receiver);
+  validators.Append<mojo::internal::MessageHeaderValidator>();
+  validators.Append<ConformanceTestInterface::ResponseValidator_>();
+
+  RunValidationTests("response_", validators.GetHead());
+}
+
 // Test that InterfacePtr<X> applies the correct validators and they don't
 // conflict with each other:
 //   - MessageHeaderValidator