PR for latest progresses on testing spec #154
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Ieben Smessaert <smessie@users.noreply.github.com>
Co-authored-by: Ieben Smessaert <smessie@users.noreply.github.com>
Co-authored-by: Ieben Smessaert <smessie@users.noreply.github.com>
feat: update test specification
- I envision that the spec tests can only test a tree:Node (basic elements of the Tree), or a part of the full tree graph, therefore I made these two categories in the conformance points. - The tests, in my view, need to emphasize the minimum requirements of a TREE implementation (the content of the TREE). - I included the generated HTML in the PR as well. Please feel free to comment on the current version. I would like to collect feedback on the current format and will remove the HTML once the PR is settled.
fix; merge the update of the main branch
refine
Collaborator
Author
|
Hey @rorlic, please feel free to leave comments on this PR based on our earlier discussion during the W3C meeting. I’ll make sure to take them into account for future improvements of this PR. Thanks! |
pietercolpaert
requested changes
Nov 12, 2025
04-tests.bs
Outdated
| * **Pass/Fail Criteria**: Pass if the client retrieves the expected number of members; fail if the count does not match or if any errors occur during retrieval. | ||
|
|
||
| --- | ||
| ## Traverse Search Tree: Relation Handling ## {#relation-handling} |
Member
There was a problem hiding this comment.
I would make these test cases optional to implement: depends on the goals of the client which relations it wants to support. However, the test cases are important: we need to be able to point to the fact that a client does support a specific type of relation and thus point at those specific test cases
Collaborator
Author
There was a problem hiding this comment.
Marked the optional(s).
Collaborator
Author
|
TODO: Also remove the performance part of testing from the PR, or organize it better. |
…nsistency Signed-off-by: XD <Xueying.Deng@imec.be>
Signed-off-by: XD <Xueying.Deng@imec.be>
Signed-off-by: XD <Xueying.Deng@imec.be>
Signed-off-by: XD <Xueying.Deng@imec.be>
Signed-off-by: XD <Xueying.Deng@imec.be>
Signed-off-by: XD <Xueying.Deng@imec.be>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.