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
@@ -38,7 +38,7 @@ Test authors will be able to inspect if the issue is a failing issue and will be
38
38
39
39
## Detailed design
40
40
41
-
###Severity Enum
41
+
###Severity Enum
42
42
43
43
We introduce a Severity enum to categorize issues detected during testing. This enum is crucial for distinguishing between different levels of test issues and is defined as follows:
44
44
@@ -65,7 +65,7 @@ extension Issue {
65
65
}
66
66
```
67
67
68
-
###Recording Non-Failing Issues
68
+
###Recording Non-Failing Issues
69
69
To enable test authors to log non-failing issues without affecting test results, we provide a method for recording such issues:
70
70
71
71
```swift
@@ -96,7 +96,7 @@ Here is the `Issue.record` method definition with severity as a parameter.
96
96
// ...
97
97
```
98
98
99
-
###Issue Type Enhancements
99
+
###Issue Type Enhancements
100
100
101
101
The Issue type is enhanced with two new properties to better handle and report issues:
102
102
-`severity`: This property allows access to the specific severity level of an issue, enabling more precise handling of test results.
@@ -131,7 +131,7 @@ extension Issue {
131
131
}
132
132
```
133
133
134
-
Example usage of `severity` and `isFailure:
134
+
Example usage of `severity` and `isFailure`:
135
135
```swift
136
136
// ...
137
137
withKnownIssue {
@@ -185,7 +185,7 @@ When there is an issue recorded with severity warning the output looks like this
185
185
To use severity today, checkout the branch here: https://github.com/swiftlang/swift-testing/pull/1189
For more details on how to checkout a branch for a package refer to this: https://developer.apple.com/documentation/packagedescription/package/dependency/package(url:branch:)
0 commit comments