-
Notifications
You must be signed in to change notification settings - Fork 14
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
Agent fails on this.findTestItem(this.testItems, test.title, playwrightProjectName).id; #45
Comments
@oranje322 Could you please check the issue above? |
Hi, I have also discovered this issue, it fails in beforeAll for my case. The failing line is ( https://github.com/reportportal/agent-js-playwright/blob/master/src/reporter.ts#L391 ): Since it's ok when item not found( see https://github.com/reportportal/client-javascript/blob/master/lib/report-portal-client.js#L400 ) i fixed this as:
Best Regards, |
Hello, The bug will be fixed in the next version agent. |
The fix was released in version 5.0.4 #49 |
Hi guys. I'm using in repo @playwright/test version 1.20 and agent in version 5.0.3 and when I enabled the option with
includeTestSteps
, then at beginning of the test run it throw an error:Error in reporter TypeError: Cannot read property 'id' of undefined
in.../node_modules/@reportportal/agent-js-playwright/src/reporter.ts:411
When I console.logged this line of code, then it looks like not always this method returns the step. But I've added a check - basic if:
if (this.findTestItem(this.nestedSteps, step.title, playwrightProjectName))
for methodonStepEnd
and it started to work. Steps are properly attached to report. But still there is a similar error inonStepBegin
:Error in reporter TypeError: Cannot read property 'id' of undefined at RPReporter.onStepBegin (.../node_modules/@reportportal/agent-js-playwright/src/reporter.ts:391:100)
together with error:
Failed to start nested step. Error: timeout of 30000ms exceeded at .../node_modules/@reportportal/client-javascript/lib/rest.js:37:15
Not sure how to solve it...
The text was updated successfully, but these errors were encountered: