Skip to content

Conversation

@stefanbinoj
Copy link
Contributor

@stefanbinoj stefanbinoj commented Oct 19, 2025

ref #1064

Changes

  • Reduced test retries to 1
  • Added List reporter for local testing
  • Added List + HTML reporters for CI testing to improve readabilityreadability
Before – Without List Reporter After – With List Reporter
Screenshot 2025-10-19 at 6 46 11 AM Screenshot 2025-10-19 at 6 46 39 AM

AI Disclosure

No AI was used for any part of this contribution.

Self Review

All changes have been reviewed and tested by myself.

Live Stream Disclosure

Viewed both live streams of antiwork and guidelines to follow


- name: Upload Playwright HTML report
if: always()
if: ${{ !cancelled() }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation copied from flexile

@stefanbinoj
Copy link
Contributor Author

@slavingia can i get a review?

workers: process.env.CI ? "100%" : undefined,
/* Reporter to use. See https://playwright.dev/docs/test-reporters */
reporter: [["html", { open: process.env.CI ? "never" : "on-failure" }]],
reporter: process.env.CI ? [["list"], ["html"]] : "list",
Copy link
Contributor

@sm17p sm17p Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add github formatter to the CI list? It would be nice to see why the spec failed in PR reviews.

Actually I don't remember if it'd be displayed in Files changed tab but it should show up on actions run and here. We can try once maybe by failing a spec intentionally?

One caveat is there would be a slight increase in CI time, so we'll have to track it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
reporter: process.env.CI ? [["list"], ["html"]] : "list",
reporter: [["list"], ["html", { open: process.env.CI ? "never" : "on-failure" }], ["github"],

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sm17p Thanks for the comment, but it seems there’s no change in the report after switching togithub
check here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you try by failing a spec?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still doesn’t seem like it’s anything worthwhile here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants