test: create strawman test suite

[ericprud]

see HTML and JSON-LD renderings of the manifest

[acoburn]

Ideally, this PR will target a separate (yet undefined) repository in order to keep the specification documents separate from the test suite artifacts and code.

[w3cbot]

This was discussed during the #lws meeting on 11 May 2026.

View the transcript

Test Suite PR #145

<TallTed> w3c/lws-protocol#145

acoburn: this PR has to do with the test suite
… opened by Eric a few weeks ago
… again, we can vote on it next week

<gb> Pull Request 145 test: create strawman test suite (by ericprud)

ericP: the first draft of the test suite wqs there to capture ....[breaking up a bit]
… we have to test the mechanism for ....
… I made something with the MANIFEST
… it can be merged without interacting with other documents
… please take a look at the MANIFEST,
… I try to work on it to ... but that's pretty optional

laurens: one question, do we want the test suite to live in the same LWS protocol repo
… should we make another repo for this?

pchampin: a separate repo would be ok
… both practices exist in W3C WGs
… I would be in favour of it, but it's up to the group

<laurens> +1

acoburn: I'm also in favor of this
… Samu Lang, who was at the f2f will be working on the test suite

laurens: I will reach out to Samu

---

[ericprud]

Per WG discussion, I moved the TS signature stuff to a new github repo called lws-contrib/signatures-in-typescript. The only remaining code is vanilla js in manifest.html. There were no objections to keeping the test suite in the same repo as the set of protocol specs, but it won't cost us much to move it in the future.