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
Copy file name to clipboardExpand all lines: README.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,10 @@ You can also run `xunit.ts` from a script in your `package.json`:
85
85
}
86
86
```
87
87
88
+
#### Filtering tests
89
+
90
+
The `xunit` command can take one or more `--filter` flags (`-f` alias) followed by a regular expression to match `TestSuiteName.TestMethodName`. See the [full documentation](https://ecoAPM.github.io/xunit.ts) for more details.
91
+
88
92
## Output
89
93
90
94
### Console
@@ -100,10 +104,10 @@ My Test Suite
100
104
Passed: 1
101
105
Total: 1
102
106
103
-
~/example $ _
107
+
~/example $ _
104
108
```
105
109
106
-
See the [full documentation](https://ecoAPM.github.io/xunit.ts) for a list of all available output options.
110
+
Results can also be output in JUnit and Sonar XML formats, for import into other systems. See the [full documentation](https://ecoAPM.github.io/xunit.ts) for a list of all available output options.
If you don't want to run your entire test suite, you can pass one or more `--filter` flags to the `xunit` command.
83
+
84
+
Filters are regular expressions that will match against the string `{TestSuiteName}.{TestMethodName}`.
85
+
86
+
Using our example above, of a test suite named `MyTestSuite` with a test method named `MyFirstTest`, we could use any of the following filters to include that test in our test run:
0 commit comments