I'm using the core-aam/acacia/json/ as a temporary directory for these tests.

These tests use js object that contains an entry for each table in core-aam. So the tests are very simple:

<div id=test role=blockquote>quote</div>

<script>
  AAMUtils.verifyAPI(
    'test',   /* dom id of object to test in accessibility tree */
    rolemap['blockquote'],   /* object representing all statements in https://w3c.github.io/core-aam/#blockquote */
    'role=blockquote'   /* string used in subtest name */
  );
</script>

Here is the result of this test: https://spectranaut.github.io/examples/wpt/role_blockquote_test.html

Right now the test has one subtest for each API, regardless of whether or not that API applies to platform the test is being run on. The test was run on linux, so only the first test -- the test of the linux API Atspi -- is useful. The other tests aren't actually run (because you can't run a mac accessibility API test on linux), which you can see by expanding and seeing No assertions run. If you are curious about this design, read more in this other PR's description