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

Screenplay tests do not show proper names on Sauce Labs #7

Open
zhtaoang opened this issue Oct 26, 2016 · 3 comments
Open

Screenplay tests do not show proper names on Sauce Labs #7

zhtaoang opened this issue Oct 26, 2016 · 3 comments

Comments

@zhtaoang
Copy link

zhtaoang commented Oct 26, 2016

mvn clean verify -Ppageobjects -Dsaucelabs.target.platform=win10 -Dwebdriver.driver=chrome -Dsaucelabs.driver.version=48 -Dsaucelabs.url=http://taoz:<somesaucekey-IDon'tWantOthersToSeeItOnGithub>@ondemand.saucelabs.com:80/wd/hub -Dsaucelabs.access.key=<somesaucekey-IDon'tWantOthersToSeeItOnGithub> -Dsaucelabs.user.id=taoz -Dwebdriver.base.url=http://todomvc.com/examples/angularjs/#/ -Dmaven.test.failure.ignore=true

The above works, which is pageobject version. But once I removed -Ppageobjects switching to 'screenplay' pattern, those tests don't even create driver instances on Sauce Labs do not show up on Sauce Labs Dashboard with proper names.

Maybe it is easily fixable. I haven't looked into the reason yet. Just want to report the behavior here.

@wakaleo
Copy link
Member

wakaleo commented Oct 27, 2016

What error are you getting?

@zhtaoang zhtaoang changed the title Screenplay tests do not run properly on Sauce Labs Screenplay tests do not show proper names on Sauce Labs Oct 27, 2016
@zhtaoang
Copy link
Author

zhtaoang commented Oct 27, 2016

screenplaydonothavenames
I updated the chrome version and now screenplay test examples can run on Sauce Labs now. So it's no longer a serious issue, because the serenity report itself seems to be OK. And the only difference is that the page object model tests show their names on Sauce Labs dashboard but screen play tests do not, which doesn't bother me much. Thanks for the response and the great work you guys have done.

@zhtaoang
Copy link
Author

zhtaoang commented Oct 31, 2016

And for tests like "TodosBelongToAUser.should_not_affect_todos_belonging_to_another_user()"
with two actors and therefore two driver/browser instances,
there is only one report video link for sauce labs recording, which points to the latter started instance. This might be a future feature, maybe there can be multiple links matching the actors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants