Tests run never seem to finish on their own

[jhendershott]

This is probably more an issue with my implementation, but I'm using the rp-mocha-reporter and it's starting and logging the launches, however, it doesn't seem to resolve in a timely manner. I'm pretty new to this but currently, I'm having to force finish.

Is there a timeout on this? or something I should be doing after the tests to clean this up?

[evjlobanova]

@ElenaRomanchuk could you please take a look?

[evjlobanova]

@jhendershott 1.) There is a special configuration in Project Settings > General for launch interruption time 2.) In version 5.0 we have known issue with scheduling jobs which do not stop launches accordingly. Will be fixed in ver 5.1 3.) However, the issue appears due to issues in the framework, which doesn't send finish request for launch. So firstly, you need to troubleshoot you framework in regard to this issue.

[jhendershott]

Got it the Launch interuption time is what I'm looking for.

I need to figure out why it's not ending it, but this a perfect stop gap in the meantime.

[ElenaRomanchuk]

@jhendershott Unfortunately there is no timeout on launch finish. We are rewriting mocha-js-reporter and probably new version can solve your problem. We still haven't released this version, so you can try it by specifying github path with master branch for mocha-js-reporter in your package.json.

[jhendershott]

@ElenaRomanchuk thanks for the suggestion! I'll try it out and let you know.

[ElenaRomanchuk]

Hi @jhendershott , We have just released the new version of mocha reporter as a new package @reportportal/agent-js-mocha: https://www.npmjs.com/package/@reportportal/agent-js-mocha. It's fully compatible with ReportPortal version 5.* and async API v2 and has some additional features. The package rp-mocha-reporter is deprecated now. I recommend you to try it. Hope this solves your problem.

[ElenaRomanchuk]

@jhendershott Please, let us know if it solves your problem.

[bhoppeadoy]

Hi, I'm using the latest released version and have the same issue. I'm using protractor and the test runs and finishes as expected. I have a launch show up in my report portal server but it shows as "In Progress" and 3 out of the 4 test steps shows as "In Progress" and only one shows as "Passed"

I have not added any report API to my tests, I've only configured the report in mochaOpts

What sets the state of a test or suite in report portal? When is the state changed?

[ElenaRomanchuk]

Hi, it should be enough to configure the reporter and reporterOptions in mochaOpts. Mocha reporter gets "start test" and "end test" events from the runner which protractor uses to run the tests. So, it should work out of the box. Which version of protractor do you use? We will investigate this issue.

[bhoppeadoy]

These are the versions I'm using:

"protractor": "^5.4.2", "mocha": "^7.1.1", "chai": "^4.2.0"

Edit: I tried updating to the latest versions and still same issue: "protractor": "^7.0.0", "mocha": "^8.0.1",

[bhoppeadoy]

Any update on this?

[bhoppeadoy]

Any update?

[ostrovanka]

Hi, i'm seeing the same problem

"@reportportal/agent-js-mocha": "^5.0.1", "@reportportal/client-javascript": "^5.0.5", "mocha": "^9.0.0"

The only way I was able to make my launches finish is to use RPClient.getPromiseFinishAllItems();

but to be able to use this method I needed to know current launch id - so had to extend mocha reporter from @reportportal/agent-js-mocha to expose launch id.

[batallo]

I have the same issue using "@reportportal/agent-js-mocha": "^5.0.2", "@reportportal/client-javascript": "^5.0.7", "mocha": "^9.2.2". Would be grateful for any updates on possible fix

[sebpam]

Any resolution for this? Current seeing this intermittently for "@reportportal/agent-js-webdriverio": "^5.0.3", "@wdio/cli": "^7.19.7",