Add more unit tests for JS bindings to Core

Add more unit tests for JS bindings to Core

This CL adds core_unittests.js, which tests basic functionality in the
JavaScript bindings for Mojo's core messaging APIs.

R=aa@chromium.org
BUG=317398
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=234460

[abarth-chromium, 2013-11-12 00:33:12]

We clearly need a better unit testing system for our JavaScript code.  If we use
CommonJS, maybe we'll be able to re-use a unit testing harness from Node.

[Aaron Boodman, 2013-11-12 01:56:16]

Yeah, so unit testing was one motivation for why the extension binding system
uses modules, and specifically CommonJS modules.

Here's an example of a unit test from the extension system:

http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/j...

(sadly, it looks like one of the only ones that was ever made)

But, hey look at all these happy little modules that together make of the
renderer side of the extension system:

https://code.google.com/p/chromium/codesearch#search/&q=require%20file:render...

http://git.chromium.org/gitweb/?p=chromium.git;a=tree;f=chrome/renderer/resou...

It really turned out to be quite a nice system. We probably need something like
this. Or maybe the same thing.

https://codereview.chromium.org/67173007/diff/1/mojo/public/bindings/js/core.cc
File mojo/public/bindings/js/core.cc (right):

https://codereview.chromium.org/67173007/diff/1/mojo/public/bindings/js/core....
mojo/public/bindings/js/core.cc:154: templ->Set(gin::StringToSymbol(isolate,
"RESULT_OK"),
Hm. That's unsatisfying.

[Aaron Boodman, 2013-11-12 05:51:00]

(lgtm)

[abarth-chromium, 2013-11-12 06:25:18]

On 2013/11/12 01:56:16, Aaron Boodman wrote:
> Yeah, so unit testing was one motivation for why the extension binding system
> uses modules, and specifically CommonJS modules.

I'd be in favor of using CommonJS.  Can we re-use the same mechanism from the
extension system?

I found
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/renderer/ex...,
but I was expecting to find something in third_party.  Maybe we need to factor
the CommonJS implementation out of the extensions system?

[commit-bot: I haz the power, 2013-11-12 06:27:48]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/abarth@chromium.org/67173007/1

[commit-bot: I haz the power, 2013-11-12 07:13:41]

Sorry for I got bad news for ya.
Compile failed with a clobber build on linux_chromeos_clang.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-11-12 07:24:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/abarth@chromium.org/67173007/1

[commit-bot: I haz the power, 2013-11-12 07:48:46]

Sorry for I got bad news for ya.
Compile failed with a clobber build on linux_chromeos_clang.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-11-12 07:56:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/abarth@chromium.org/67173007/1

[commit-bot: I haz the power, 2013-11-12 08:21:01]

Sorry for I got bad news for ya.
Compile failed with a clobber build on linux_chromeos_clang.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-11-12 08:27:33]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/abarth@chromium.org/67173007/1

[commit-bot: I haz the power, 2013-11-12 08:36:59]

Change committed as 234460