You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have an API or mechanism to perform an action once inside a suite type before or after running all of that suite's tests.
Conceptually, this would be similar to XCTest's class-level +setUp and +tearDown APIs, or what some other testing libraries call "BeforeAll" and "AfterAll". However, for a more modern Swift solution, it may be better to use a closure- or scoped access- style API, since that interoperates better with Swift concurrency and allows using @TaskLocal.
rdar://103616215
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response
The text was updated successfully, but these errors were encountered:
Or something like that. Runner can then detect that a suite type conforms to this protocol and, if so, trivially call those functions at the appropriate times.
Description
We should have an API or mechanism to perform an action once inside a suite type before or after running all of that suite's tests.
Conceptually, this would be similar to XCTest's class-level
+setUp
and+tearDown
APIs, or what some other testing libraries call "BeforeAll" and "AfterAll". However, for a more modern Swift solution, it may be better to use a closure- or scoped access- style API, since that interoperates better with Swift concurrency and allows using@TaskLocal
.rdar://103616215
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of
swift --version && uname -a
)No response
The text was updated successfully, but these errors were encountered: