-
Notifications
You must be signed in to change notification settings - Fork 0
Add Test Reporter GitHub Action Plugin
#32
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -55,7 +55,14 @@ jobs: | |||||
| env: | ||||||
| VUNIT_CI_MODE: "true" | ||||||
| timeout-minutes: 15 # Test execution timeout | ||||||
|
|
||||||
| - name: Test Report | ||||||
| uses: dorny/test-reporter@c8370352934b730bc7f9acc17180a1f5f3964ffd # v2 | ||||||
| if: ${{ !cancelled() }} | ||||||
| with: | ||||||
| name: VUnit Test Results | ||||||
|
||||||
| name: VUnit Test Results | |
| name: VUnit Test Report Summary |
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.
The new "Test Report" step uses a different conditional (
if: ${{ !cancelled() }}) compared to the other test reporting steps in the workflow (lines 68, 75, 82) which useif: always(). This inconsistency means this step won't run if the "Run VUnit tests" step fails, while the other test reporting steps will. For consistent test result reporting regardless of test outcome, consider usingif: always()instead.