- From: Benjamin Goering <ben@bengo.co>
- Date: Tue, 6 Feb 2024 19:22:03 -0800
- To: public-solid <public-solid@w3.org>
Hey there. I just wanted to shout and say that I found the document at https://solidproject.org/ED/qa really interesting when considering how to represent test cases for ActivityPub https://www.w3.org/TR/activitypub/ It seems[0] to jive well with the rest of this test methodology, at least at a high level https://www.w3.org/TR/test-methodology/ In activitypub-testing[1], a test runner for activitypub, I’d like to explore ways of publishing test cases that interop with and/or share tooling with the “Test Case Descriptions” from Solid QA https://solidproject.org/ED/qa#test-case-description That way the tool could support browsing and maybe even running tests published anywhere on the web as long as it can fetch/parse the Test Case Description or Test Suite by URL. I’m collecting a list of known implementations of Test Case Description from Solid QA so I could use them as test fixtures in any fetcher/parser. Anyone wanna show off an example test case description or two that I aim to emulate? I want to do something similar for to describe test cases like https://socialweb.coop/activitypub/test-cases/outbox-post-servers-must-return-a-201-created-http-code/ or https://activitypub-testing-website.socialweb.coop/test-cases/actor-must-serve-as2-object-to-get For example, I could try to modify the html to mark up some of the properties of the test case description using rdfa and/or I could also embed a <script> tag with JSON-LD (or any other rdf) with the data all in one place. I could also work on content negotiation for various media types at the http layer. Is everyone already doing the same thing? Thanks again to the authors of that Solid QA doc. Good work so far! [0]: https://bengo.is/activitypub/apply-w3-test-methodology/ [1]: https://socialweb.coop/activitypub-testing/
Received on Wednesday, 7 February 2024 03:22:22 UTC