Testing process for Javascript APIs

Basically, every part of the spec needs to be tested to get out of
Candidate Recommendation. This means that all parts of the spec that are
normative should have the same amount of coverage.

Currently, testing information is centralized here:

http://testthewebforward.org/

This information is mostly JS API-centric, but still will be useful as
we can create a JS-based test-harness even for the delivery in JSON(LD)
of the Social API. Then, we can use that to parse and validate the AS
2.0 and show multiple implementations of both the API and AS 2.0 (and
hopefully federation).

Tests are contributed via pull requests on Github. We can create a
"SocialAPI" section as soon as we want, but now is likely premature:

https://github.com/w3c/web-platform-tests

The test approval process generally requires a few reviewers to make
sure the test fits. See here for details:

http://testthewebforward.org/docs/review-process.html

This is done using the Critic software ran by James Graham that
integrates well with Github. For an example, see here:

https://critic.hoppipolla.co.uk/r/3900


Hope this helps.

   cheers,
      harry

Received on Wednesday, 4 February 2015 01:02:56 UTC