commit 040bcbd09cfd699a6f6806b986c322c53492928d
author Fred Shih <ffred@chromium.org> Wed Nov 06 20:30:52 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed Nov 06 20:30:52 2024
tree 1e7d6279c9e1c3e9f48ba1180059725e1c5b2c51
parent 77fffdfcf4e7e88121d09525faf267292e0a8967

Add mojo conformance validation test to ts/js bindings

Design doc: go/conformancets

This change adds the mojo conformance validation test to the js/ts
bindings.

The test cases are read and parsed by the C++ side. A new mojo service
is introduced to plumb the test cases to the typescript.

On the typescript side, a new receiver/remote pair is created for each
test case, then the buffer is manually injected into the receiver's
message router. This allows us to bypass the underlying C-runtime and
directly pass the message to the js message handler. This does require
adding a new test method in mojojs' interface support library.

Unfortunately, error reporting/handling is very inconsistent in the
js bindings. A combination of console.error, console.assert, exception
throwing, and onError callbacks are used to report errors. Therefore
we need to override all those functions to determine whether or not
a mojo error has been reported for a given buffer.

Bug: 376760886
Change-Id: I5f21d933c0325cf937009df604ddf27d4cb89bdb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5817681
Commit-Queue: Fred Shih <ffred@chromium.org>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Yuzhu Shen <yzshen@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1379210}