Validate incoming JS Message Headers: test message parser

mojo/public/js/bindings/tests/codec_unittests.js

 // Copyright 2013 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.
 
 define([

[abarth-chromium, 2014/07/23 02:13:52]

Sorry, I was unclear.  I think it's fine for the _unittests.js files to be
adjacent to the files they test.  That's the normal convention in Chrome for
_unittests.cc files.  What I meant is that supporting code for unit tests (e.g.,
JavaScript modules or C++ code) should be in the test subdirectory.  For
example, moving run_js_tests.cc into this directory is great.

[hansmuller, 2014/07/23 18:06:35]

OK, I've moved the unit tests up the parent directory, where the corresponding
implementation files are.

     "gin/test/expect",
     "mojo/public/js/bindings/codec",
     "mojo/public/interfaces/bindings/tests/sample_service.mojom",
   ], function(expect, codec, sample) {
   testBar();
   testFoo();
   testTypes();
   testAlign();
   testUtf8();
   this.result = "PASS";
@@ skipping 203 matching lines @@
     expect(actualMemory.length).toEqual(expectedMemory.length);
     expect(actualMemory).toEqual(expectedMemory);
 
     var reader = new codec.MessageReader(message);
     expect(reader.payloadSize).toBe(payloadSize);
     expect(reader.messageName).toBe(messageName);
     var str2 = reader.decoder.decodeStringPointer();
     expect(str2).toEqual(str);
   }
 });