Fix handling of unexpected cases in bit-flip test.

mojo/apps/js/test/js_to_cpp.mojom

 module js_to_cpp {
 
 // This struct encompasses all of the basic types, so that they
 // may be sent from C++ to JS and back for validation.
 struct EchoArgs {
   int64 si64;
   int32 si32;
   int16 si16;
   int8  si8;
   uint64 ui64;
@@ skipping 10 matching lines @@
   string[] string_array;
   handle<message_pipe> message_handle;
   handle<data_pipe_consumer> data_handle;
 };
 
 struct EchoArgsList {
   EchoArgsList next;
   EchoArgs item;
 };
 
+// Note: For messages which control test flow, pick numbers that are unlikely

[viettrungluu, 2014/05/22 19:24:18]

Would it be better to use a completely separate interface for control purposes?
Doing so would ensure that no matter how hard you're fuzzing, you won't end up
accidentally starting/stopping the test.

(Also, at some point, we may probably enforce that the ordinals be consecutive
or something like that.)

+// to be hit as a result of our deliberate corruption of response messages.
 interface CppSide {
-  StartTest();  // Sent for all tests to notify that the JS side is now ready.
-  TestFinished();  // Indicates end for echo, bit-flip, and back-pointer tests.
+  // Sent for all tests to notify that the JS side is now ready.
+  StartTest @88888888 ();

[viettrungluu, 2014/05/22 21:19:12]

Style nit: Probably format this as:

  StartTest@88888888();

[Tom Sepez, 2014/05/22 21:22:22]

Done.

+
+  // Indicates end for echo, bit-flip, and back-pointer tests.
+  TestFinished @99999999 ();

[viettrungluu, 2014/05/22 21:19:12]

"

[Tom Sepez, 2014/05/22 21:22:22]

Done.

+
+  // Responses from specific tests.
   PingResponse();
   EchoResponse(EchoArgsList list);
   BitFlipResponse(EchoArgsList arg);
   BackPointerResponse(EchoArgsList arg);
 };
 
 [Client=CppSide]
 interface JsSide {
   Ping();
   Echo(int32 numIterations, EchoArgs arg);
   BitFlip(EchoArgs arg);
   BackPointer(EchoArgs arg);
 };
 
 }