Return tests discovered by workspace/tests
and textDocument/tests
in a hierarchical format
#1149
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.
This ways the client doesn’t need to create a hierarchical structure using the container names. It is also more flexible and allows nesting of test suites + the addition of labels and tags for swift-testing.
The data structure for
TestItem
has been heavily inspired by VS Code’sTestItem
for the test explorer, which should make it fairly straightforward to integrate these results into the VS Code test explorer.A known limitation is that the test IDs are currently not qualified by the module name. I’m planning to implement this soon via a follow-up PR (#1150).
Definition of TestItem in VS Code