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
# Optionally specify a title (Heading level 1) for the report. Leading and trailing whitespace are ignored.
159
+
# This is useful for separating your test report from other sections in the build summary.
160
+
# If omitted or set to whitespace/empty, no title will be printed.
161
+
report-title: ''
157
162
158
163
# Customize the title of badges shown for each Actions Summary.
159
164
# Useful when distinguish summaries for tests ran in multiple Actions steps.
@@ -345,7 +350,7 @@ Support for Swift test results in xUnit format is experimental - should work but
345
350
346
351
Unfortunately, there are some known issues and limitations caused by GitHub API:
347
352
348
-
- Test report (i.e. Check Run summary) is markdown text. No custom styling or HTML is possible.
353
+
- Test report (i.e. build summary) is Markdown text. No custom styling or HTML is possible.
349
354
- Maximum report size is 65535 bytes. Input parameters `list-suites` and `list-tests` will be automatically adjusted if max size is exceeded.
350
355
- Test report can't reference any additional files (e.g. screenshots). You can use `actions/upload-artifact@v4` to upload them and inspect them manually.
351
356
- Check Runs are created for specific commit SHA. It's not possible to specify under which workflow test report should belong if more
0 commit comments