Skip to content

Conversation

plemarquand
Copy link
Contributor

Because swift-testing suites can be defined through nested extensions the tests provided might not be directly parented to the test target. For instance, the test target might be Foo, and one of the child testItems in the document tests response might be Foo.Bar/Baz. If we simply attach the testItems to the root test target then the intermediate suite Bar will be dropped. To avoid this, syntheize the intermediate children just like we synthesize the test target.

Because swift-testing suites can be defined through nested extensions
the tests provided might not be directly parented to the test target.
For instance, the test target might be `Foo`, and one of the child
`testItems` in the document tests response might be `Foo.Bar/Baz`.
If we simply attach the `testItems` to the root test target then the
intermediate suite `Bar` will be dropped. To avoid this, syntheize
the intermediate children just like we synthesize the test target.
@plemarquand plemarquand merged commit 5cc4236 into swiftlang:main Dec 16, 2024
15 checks passed
@plemarquand plemarquand deleted the test-item-parent-synthesis branch December 16, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants