Repository navigation
Standardized test cases #97
Description
Activity
https://github.com/Informatievlaanderen/VSDS-Testbed
The test suits are categorized by the non-normative keyworks : MUST SHOULD OPTIONALThe 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.mdI 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? go-fed/activity#46Hello @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.Thanks
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
Pieter will start with a PR, @xdxxxdx will review and add things afterwards
Started something here: #120
- pinned this issue
on Apr 2, 2025 - unpinned this issue
on Apr 2, 2025
Metadata
Metadata
Assignees
Type
Projects
- Status
Test cases need to be carefully standardized
Please comment with: existing cases elsewhere, and proposals to categorize the tests.
Pull request started in #120