Skip to content
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

Support for suite retry using Jasmine #157

Open
itayTipalti opened this issue May 26, 2021 · 8 comments
Open

Support for suite retry using Jasmine #157

itayTipalti opened this issue May 26, 2021 · 8 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@itayTipalti
Copy link

itayTipalti commented May 26, 2021

hi,

The problem

When I run tests in wdio using jasmine, the current retry mechanism does not support a retry in the suite(describe) level.
maybe there could be a retry mechanism to avoid the next issue ,where there are duplications in the suite names:

image

Environment

WebdriverIO version: 6
wdio-reportportal-version version: 6.4
Node.js version:14.16.0
WDIO Testrunner and version(mocha\cucumber\jasmine):Jasmine: 7.5.2
Additional wdio packages used (if applicable):wdio-reportportal-reporter,wdio-reportportal-service

Thanks!

@BorisOsipov
Copy link
Owner

@itayTipalti I am not sure that RP supports suite retry and I don't have plans to implement this.

@BorisOsipov BorisOsipov changed the title Support for retry using Jasmine Support for suite retry using Jasmine May 26, 2021
@itayTipalti
Copy link
Author

@BorisOsipov

I know that the current retry mechanism allows a retry to the same test item, where it identifies the name and reports into the same test item(exists right now).

Maybe there is a way that in case of 2 suites with the same name, the second suite will be reported into the first suite in case retry flag is activated?

@BorisOsipov
Copy link
Owner

Maybe there is a way that in case of 2 suites with the same name, the second suite will be reported into the first suite in case retry flag is activated?

maybe. I didn't try. As I see on rp api there is no difference between suite and test testitems. But I don't know how will rp process suite retry in reality.

@itayTipalti
Copy link
Author

@BorisOsipov

From my experience you cannot start a root item which is a retry of another item (it returns an error that it is not possible).
It seems that only retrying a test item inside one suite is optimal for that.

@BorisOsipov
Copy link
Owner

@itayTipalti ok. and what do you want from reporter if Rp doesn't support suites retry?

@itayTipalti
Copy link
Author

@BorisOsipov
If possible, To create a workaround that does the following:
If there is a suite, that failed, and the same suite is being executed again(part of retry), so (if the flag for that is true), the reporter will report to the first suite, instead of creating a new suite.

If the existing property, "setRetryTrue" is true, so what will happen is that the same tests will be reported to the first suite, and will be shown as retried. it will be a great way to show a suite that all its tests were retried, instead of creating a new suite

@BorisOsipov
Copy link
Owner

@BorisOsipov theoretically it looks possible. RP allows report testitem in closed suite. But I can't make any promise to implement it in near future. It is not easy and it will be long

@BorisOsipov BorisOsipov added enhancement New feature or request help wanted Extra attention is needed labels May 26, 2021
@itayTipalti
Copy link
Author

@BorisOsipov
ok, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants