Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(109)

Side by Side Diff: mojo/public/js/bindings/tests/validation_unittests.js

Issue 411553003: Validate incoming JS Message Headers: test message parser (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Factored common Buffer class, moved JS binding tests Created 6 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 // Copyright 2013 The Chromium Authors. All rights reserved. 1 // Copyright 2013 The Chromium Authors. All rights reserved.
Matt Perry 2014/07/23 00:39:38 2014
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 define(["gtest"], function(gtest) { 5 define([
6 gtest.expectTrue(true, "true is true"); 6 "gin/test/expect",
7 gtest.expectFalse(false, "false is false"); 7 "mojo/bindings/js/message_file_parser"
8 gtest.expectTrue(this, "this is " + this); 8 ], function(expect, parser) {
9 9
10
11 expect(parser.checkMessageFileParser()).toBeNull();
yzshen1 2014/07/23 07:26:55 Why putting the testing code in message_file_parse
hansmuller 2014/07/23 18:06:36 I didn't wanted to export parser internals like Fi
yzshen1 2014/07/23 19:53:38 I am not sure I understand: The parser will need t
hansmuller 2014/07/23 21:43:44 What I'd written for the original patch was to inc
10 this.result = "PASS"; 12 this.result = "PASS";
11 }); 13 });
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698