Support case groups #27
Labels
enhancement
New feature or request
Comments
Julian
added a commit
that referenced
this issue
Sep 23, 2022
Only does so at a per-case level. We'll evaluate other options in #27. It's also possible some global-level request will be useful, which we can also look at later. Lets test cases reference arbitrary additional schemas for retrieval. Also then makes the JSON-Schema-Test-Suite-specific support use this new registry to pass along remotes/-directory schemas. This is easier or harder with various implementations it seems, and it may be I've missed some APIs here for an implementation or two. Closes: #14.
Julian
added a commit
that referenced
this issue
Dec 12, 2023
These don't actually exist yet, but the schemas now do which is a start. The rest of the work is mostly in Python-land now. Refs: #27
|
The linked commit adds a schema for this at least. To be considered now is that we likely should refrain from sending harnesses anything but "leaf" test groups (i.e. ones that match the current structure), and preserve the nesting only in reports / for the UI. That should be mostly feasible with the committed schema, just requires some modification of the |
This was referenced Dec 17, 2023
Closed
Julian
added a commit
that referenced
this issue
Feb 1, 2024
These aren't used yet anywhere, but TestCase is now ready to be replaced at least. Refs: #27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Or generalize the notion itself of cases to groups.
Right now in the test suite we group cases by file (often by keyword).
We should reflect this structure in the report emitted by bowtie.
Backing off should perhaps take into account groups.
schemaandregistry(#14) are also probably in need of consideration after this is done -- right now they're per-case, but probably can be per-case-group, especially if the notions merge.The text was updated successfully, but these errors were encountered: