Standardized test cases

[pietercolpaert]

Test cases need to be carefully standardized

Please comment with: existing cases elsewhere, and proposals to categorize the tests.

Pull request started in https://github.com/TREEcg/specification/pull/120

[xdxxxdx]

https://github.com/Informatievlaanderen/VSDS-Testbed The test suits are categorized by the non-normative keyworks : MUST SHOULD OPTIONAL

The identified test points are listed here: [The test suit targets more LDES, not include the new extraction algorithm] https://github.com/xdxxxdx/pyldes_kbo/blob/main/ConformanceTesting/TressSpec/TreeSpecConformancePoints.md

[xdxxxdx]

I think we need to

• First, identify what this test is against. e.g. is it supposed to test against the input/output of the pipeline of a tree server?
• Second we need to think about which kind of tool, or frame we would like these tests to run.
  • postman collection?
  • etc. How test run is interacted with?

It will be helpful if we can have some reference test suits. e.g. test suite for activity hub? https://github.com/go-fed/activity/issues/46

[xdxxxdx]

Hello @pietercolpaert ,

I prepared some step-to-step test case idea in the following attached slides. If time fits, I would like to talk about it in the next TREE meeting (dec 2024). Please let me know what do you think about it.

Slides Proposition

Thanks

[pietercolpaert]

As discussed in the call of 2024-12-04:

• We’ll focus the spec’s test suite on the client test cases
• We’ll pull request a new report in this repository which will contain a full text description of the test cases
• We’ll make a new repository with test suite assets that can be used by client implementers

[pietercolpaert]

Pieter will start with a PR, @xdxxxdx will review and add things afterwards

[pietercolpaert]

Started something here: https://github.com/TREEcg/specification/pull/120