You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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 testsdon't even create driver instances on Sauce Labsdo 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.
The text was updated successfully, but these errors were encountered: