Playwright Custom Reporter not running when integrating with SauceLabs about saucectl-run-action HOT 6 CLOSED

Actually, I did end up finding a viable workaround!

Try this:

const config: PlaywrightTestConfig = {
  reporter: [['./testrail/reporter/testrail.reporter.ts']],
}

from saucectl-run-action.

Ah ok, makes sense.
Maybe adding a warning/info message about that here to avoid explaining it again: https://docs.saucelabs.com/web-apps/automated-testing/playwright/yaml/#reporters

Thanks!

from saucectl-run-action.

Indeed, we set the reporters to list, junit and our own internal reporter, thereby overriding your reporter settings. As it stands, I don't see a way to work around this limitation. I'll create a feature request ticket internally 👍

from saucectl-run-action.

Thank you! Looking forward to the resolution!

from saucectl-run-action.

The Custom Reporter is working as expected when the Playwright tests run in SauceLabs using your workaround!

I could take a guess on why this is working; however, it would be just a guess.
How come providing an Array<Array<string>> for the reporter in the configuration works over providing a string for the reporter?

from saucectl-run-action.

There's a logic in place that concats arrays together, but if the value is a primitive, and we have an explicit setting for it, ours takes precedence (this is so we can override certain user settings so that playwright functions or integrates better with our cloud).

from saucectl-run-action.