[ERROR]: TypeError [ERR_INVALID_ARG_TYPE] when running playwright service with node v20.10.0 and set qase=true

[RF2023]

Describe the bug
Enabling qase on our build.yml file and running on MS playwright service is throwing an error.

To Reproduce
Steps to reproduce the behavior:

1. Step 1 'Running a test suite with a specific tag on gha'
2. Step 2 'send_to_qase: true in build.yml file'
3. Step 3 'suite doesnt run and throws the following error'
4. See error

Expected behavior
Test results should be sent to qase

Screenshots
If applicable, add screenshots to help explain your problem.

Setup information (please complete the following information):
Azure Subscription Id:798f112d-0c47-431d-9b57-eeae586eb023
Workspace Name: Playwright
Service trace Id (if available):
Log snippet (if available):
Browser on which tests are executed (if applicable): chromium
Time range (in PST) when the issue was experienced: Multiple times
Playwright Version: 1.42.1
Client machine OS: MAC
OS requested on Service: linux

Additional context
We have verified this after upgrading our node version as well, based on another ticket but the error still persists. Due to this we are unable to enable qase for MS Playwright service.

ErrorCaptureStackTrace(err); ^ TypeError: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined at new ReadStream (node:internal/fs/streams:174:5) at Object.createReadStream (node:fs:2916:10) at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:388:30) at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23) at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53) at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71 at new Promise (<anonymous>) at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12) at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:387:57 at Array.map (<anonymous>) at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:387:36) at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23) at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53) at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71 at new Promise (<anonymous>) at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12) at PlaywrightReporter.uploadAttachments (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:443:16) at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:231:43) at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23) at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53) at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71 at new Promise (<anonymous>) at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12) at PlaywrightReporter.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:245:16) at ReporterV2Wrapper.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/reporterV2.js:87:158) at /runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:47:65 at wrap (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:86:5) at Multiplexer.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:47:45) at InternalReporter.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/internalReporter.js:62:20) at JobDispatcher._reportTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/dispatcher.js:516:20) at JobDispatcher._onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/dispatcher.js:288:10) at WorkerHost.emit (node:events:513:28) at ChildProcess.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/processHost.js:105:16) at ChildProcess.emit (node:events:513:28) at emit (node:internal/child_process:946:14) at processTicksAndRejections (node:internal/process/task_queues:84:21) { code: 'ERR_INVALID_ARG_TYPE' }

[puagarwa]

Hi @RF2023
The stacktrace suggest error is coming from qase module and it doesnt seems like coming from playwright service. I would suggest you to check with QASE team.
If you still think this is related to MS playwright service, let me know why.

[RF2023]

I opened a ticket with QASE, i will keep you posted.

[puagarwa]

Closing the issue for now, feel free to reopen it if you still think its related to playwright service.

[RF2023]

So we are clearly seeing an issue when we use playwright.config.ts vs playwright.service.config.ts

latest error, it starts of hitting the qase API we get a notification saying qase run is created but , can you still confirm if this is not relating to the service and is a QASE issue? I have a open ticket with them as well.

`qase: Current PID: 2695

Running 32 tests using 10 workers

qase: Project ***** exists
qase: Using run 142 to publish test results`

`node:internal/fs/utils:699
    throw new ERR_INVALID_ARG_TYPE(propName, ['string', 'Buffer', 'URL'], path);
          ^

TypeError: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at new ReadStream (node:internal/fs/streams:185:5)
    at Object.createReadStream (node:fs:3076:10)
    at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:390:30)
    at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23)
    at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53)
    at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71
    at new Promise (<anonymous>)
    at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12)
    at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:389:57
    at Array.map (<anonymous>)
    at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:389:36)
    at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23)
    at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53)
    at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71
    at new Promise (<anonymous>)
    at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12)
    at PlaywrightReporter.uploadAttachments (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:445:16)
    at PlaywrightReporter.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/src/index.ts:233:43)
    at step (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:64:23)
    at Object.next (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:45:53)
    at /runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:39:71
    at new Promise (<anonymous>)
    at __awaiter (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:35:12)
    at PlaywrightReporter.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright-qase-reporter/dist/index.js:247:16)
    at ReporterV2Wrapper.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/reporterV2.js:87:150)
    at /runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:47:65
    at wrap (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:86:5)
    at Multiplexer.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/multiplexer.js:47:45)
    at InternalReporter.onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/reporters/internalReporter.js:62:20)
    at JobDispatcher._reportTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/dispatcher.js:518:20)
    at JobDispatcher._onTestEnd (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/dispatcher.js:284:10)
    at WorkerHost.emit (node:events:514:28)
    at ChildProcess.<anonymous> (/runner/_work/lively-automation/lively-automation/node_modules/playwright/lib/runner/processHost.js:105:16)
    at ChildProcess.emit (node:events:514:28)
    at emit (node:internal/child_process:951:14)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v20.10.0
Playwright tests failed with exit code 1`

[puagarwa]

HI @RF2023 , Even though the above log clearly pointing at issue in Qase package but lets do below to further understanding if MPT service has any role here.

• playwright.service.config inherit playwright.config and override few fields where one is them is essential for service integration which is connectOption, others are optional like ignoreSnapshots, snapshotPathTemplate, please comment these two and try once, if works then all good.
• We could also try to disable service via this change
  • if issue persist then service.config has issue and we can work it out but service itself doesnt have any issue.
  • if issue goes away, then we need to deep dive to understand qase dependency.

Basically we are trying to find of we have issue in service.config or service+Qase use case.

[RF2023]

Thats exactly what i was thinking to isolate whether its just qase or service+case. For now its looking like the later, but let me experiment with yours and get back to you. Thank you !!

…

On Fri, May 17, 2024 at 3:19 AM Puneet Agarwal ***@***.***> wrote: HI @RF2023 <https://github.com/RF2023> , Even though the above log clearly pointing at issue in Qase package but lets do below to further understanding if MPT service has any role here. - playwright.service.config inherit playwright.config and override few fields where one is them is essential for service integration which is connectOption, others are optional like ignoreSnapshots, snapshotPathTemplate, please comment these two and try once, if works then all good. - We could also try to disable service via this change <https://github.com/microsoft/playwright-testing-service/pull/108/files> - if issue persist then service.config has issue and we can work it out but service itself doesnt have any issue. - if issue goes away, then we need to deep dive to understand qase dependency. Basically we are trying to find of we have issue in service.config or service+Qase use case. — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ6GIWB6YF7AK2TREVVEJGLZCWVQJAVCNFSM6AAAAABHCJATDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHEYTCMRXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Regards, Shravan Kumar Eetha Sr QA Engineer Lively, Inc. | www.livelyme.com <https://livelyme.com/>

[RF2023]

- Its definitely hitting QASE API as we are getting a notification saying a test run has been created. playwright.service.config inherit playwright.config and override few fields where one is them is essential for service integration which is connectOption, others are optional like ignoreSnapshots, snapshotPathTemplate, please comment these two and try once, if works then all good -* This didnt work and same error using service.* - Tried it not using the service file and the normal file, results are getting published to QASE. I just tried the service few minutes ago, if at all you can check the logs based on the time of this email.

…

On Fri, May 17, 2024 at 3:19 AM Puneet Agarwal ***@***.***> wrote: HI @RF2023 <https://github.com/RF2023> , Even though the above log clearly pointing at issue in Qase package but lets do below to further understanding if MPT service has any role here. - playwright.service.config inherit playwright.config and override few fields where one is them is essential for service integration which is connectOption, others are optional like ignoreSnapshots, snapshotPathTemplate, please comment these two and try once, if works then all good. - We could also try to disable service via this change <https://github.com/microsoft/playwright-testing-service/pull/108/files> - if issue persist then service.config has issue and we can work it out but service itself doesnt have any issue. - if issue goes away, then we need to deep dive to understand qase dependency. Basically we are trying to find of we have issue in service.config or service+Qase use case. — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ6GIWB6YF7AK2TREVVEJGLZCWVQJAVCNFSM6AAAAABHCJATDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHEYTCMRXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Regards, Shravan Kumar Eetha Sr QA Engineer Lively, Inc. | www.livelyme.com <https://livelyme.com/>

[puagarwa]

HI @RF2023, can you please try my other suggestion as well
We could also try to disable service via this change

• if issue persist then service.config has issue and we can work it out but service itself doesnt have any issue.
• if issue goes away, then we need to deep dive to understand qase dependency.

[RF2023]

So when you say disable service, the tests are not running on service unless we specify the service file. Did i understand that correctly? Do you want me to still make the changes suggested and use the service config file? This is how our file which triggers the tests to qase looks test: name: ****** uses: ./.github/workflows/auto.yml with: environment: localhost config_file: playwright.service.config.ts tag: ***** send_to_qase: true

…

On Fri, May 17, 2024 at 2:54 PM Puneet Agarwal ***@***.***> wrote: HI @RF2023 <https://github.com/RF2023>, can you please try my other suggestion as well We could also try to disable service via this change <https://github.com/microsoft/playwright-testing-service/pull/108/files> - if issue persist then service.config has issue and we can work it out but service itself doesnt have any issue. - if issue goes away, then we need to deep dive to understand qase dependency. — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ6GIWDSB5BEWNTS4CWL7QDZCZG5JAVCNFSM6AAAAABHCJATDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGIYDKNBUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Regards, Shravan Kumar Eetha Sr QA Engineer Lively, Inc. | www.livelyme.com <https://livelyme.com/>

[Sid200026]

Hi @RF2023

So when you say disable service, the tests are not running on service
unless we specify the service file. Did i understand that correctly?
Do you want me to still make the changes suggested and use the service
config file?

Since running with no service using playwright.config.ts file is already working, we want you to run with service disabled but using the playwright.service.config.ts file. This can be achieved by not passing the connectOptions parameter - Reference PR - env variable to toggle MPT service #108