Move existing Mojo JS <--> CPP tests out of webui test harness.

Move existing Mojo JS <--> CPP tests out of webui test harness.

The mojo webui test in content_browsertests was not the proper place to
perform bindings-related fuzzing (though it was initially convenient).  As a
 first step, move the existing tests to the new "framework" sky added in
  https://src.chromium.org/viewvc/chrome?revision=267208&view=revision

This also restores the webui code to something near its original purpose,
although I've kept a few of the hooks that may be useful as real webui 
tests are added.

R=sky@chromium.org

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

[Tom Sepez, 2014-04-30 23:34:27]

Sky, please take a look.  Thanks heaps.

[sky, 2014-05-01 03:20:38]

https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
File mojo/apps/js/test/js_to_cpp_unittest.cc (right):

https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
mojo/apps/js/test/js_to_cpp_unittest.cc:27: int message_count = 0;
Can you scope these to JsToCppTest (or the subclass, whatever makes sense). That
way they're initialized correctly for each iteration and better scoped.

https://codereview.chromium.org/268593002/diff/20001/mojo/public/interfaces/b...
File mojo/public/interfaces/bindings/tests/js_to_cpp.mojom (left):

https://codereview.chromium.org/268593002/diff/20001/mojo/public/interfaces/b...
mojo/public/interfaces/bindings/tests/js_to_cpp.mojom:1: module mojo {
I think this would better fit right next to the test rather than here.

[Tom Sepez, 2014-05-01 17:48:26]

https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
File mojo/apps/js/test/js_to_cpp_unittest.cc (right):

https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
mojo/apps/js/test/js_to_cpp_unittest.cc:27: int message_count = 0;
On 2014/05/01 03:20:38, sky wrote:
> Can you scope these to JsToCppTest (or the subclass, whatever makes sense).
That
> way they're initialized correctly for each iteration and better scoped.

Moved to PingCppSideConnection / EchoCppSideConnection as it's methods are the
ones that update this.

https://codereview.chromium.org/268593002/diff/20001/mojo/public/interfaces/b...
File mojo/public/interfaces/bindings/tests/js_to_cpp.mojom (left):

https://codereview.chromium.org/268593002/diff/20001/mojo/public/interfaces/b...
mojo/public/interfaces/bindings/tests/js_to_cpp.mojom:1: module mojo {
On 2014/05/01 03:20:38, sky wrote:
> I think this would better fit right next to the test rather than here.
I'm confused. Are you talking about the module statement or the comment that
follows?  Where did you intend it to go?

[Tom Sepez, 2014-05-01 17:51:24]

On 2014/05/01 17:48:26, Tom Sepez wrote:
>
https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
> File mojo/apps/js/test/js_to_cpp_unittest.cc (right):
> 
>
https://codereview.chromium.org/268593002/diff/20001/mojo/apps/js/test/js_to_...
 I'm confused. Are you talking about the module statement or the comment that
> follows?  Where did you intend it to go?
Or did you mean the directory for file itself?  That makes sense.  I'll move it.

[Tom Sepez, 2014-05-01 18:11:35]

Sky, please review. Thanks.

[sky, 2014-05-01 18:15:11]

LGTM - ya, moving to different directory is what I meant. Sorry for not being
clear.

[Tom Sepez, 2014-05-01 19:39:38]

The CQ bit was checked by tsepez@chromium.org

[commit-bot: I haz the power, 2014-05-01 19:40:29]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tsepez@chromium.org/268593002/60001

[commit-bot: I haz the power, 2014-05-02 00:49:07]

Change committed as 267703