-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote exit tests to API #324
base: main
Are you sure you want to change the base?
Conversation
fe21f14
to
988ddfe
Compare
988ddfe
to
697123a
Compare
19f37c3
to
4825821
Compare
feb425b
to
e84b014
Compare
6f0e7f0
to
875b870
Compare
875b870
to
4365611
Compare
4365611
to
7d25e07
Compare
Rebased. |
ecda40c
to
59ec9f5
Compare
@swift-ci test |
59ec9f5
to
4c0d958
Compare
@swift-ci test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this article, it's really helpful for developers!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @grynspan!
@swift-ci test |
53ba137
to
8fd5bde
Compare
@swift-ci test |
One of the first enhancement requests we received for swift-testing was the ability to test for precondition failures and other critical failures that terminate the current process when they occur. This feature is also frequently requested for XCTest. With swift-testing, we have the opportunity to build such a feature in an ergonomic way. Read the full proposal [here](https://github.com/apple/swift-testing/blob/jgrynspan/exit-tests-proposal/Documentation/Proposals/NNNN-exit-tests.md).
…ial language standard)
8fd5bde
to
ab42c8b
Compare
@swift-ci test |
This PR promotes exit tests to API, pending approval of the proposal at swiftlang/swift-evolution#2718.
View the full proposal here.
Checklist: