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
We noticed on our team after 2.1.0 release that amOnPage action previously assumed the .url attribute from the page, but then after needed to be explicitly included (all our tests failed).
Steps to reproduce
Create test with amOnPage action: <amOnPage url="{{AdminLoginPage}}" stepKey="goToAdminLoginPage"/>
Generate tests by running: vendor/bin/robo generate:tests
Expected result
Warning message appears: Can not resolve argument on url attribute for amOnPage action. Step Key: "goToAdminLoginPage".
Actual result
Tests successfully generated and action amOnPage looks like this: $I->amOnPage("{{AdminLoginPage}}");
The text was updated successfully, but these errors were encountered:
I was able to reproduce this issue. @okolesnyk I understand we have some of these issues around for community members to tackle, but I don't like the idea of these issues sitting for so long (over a year in this case).
I would like to close this issue and create a Jira ticket instead. Are you ok with that?
General summary
We noticed on our team after 2.1.0 release that
amOnPage
action previously assumed the.url
attribute from the page, but then after needed to be explicitly included (all our tests failed).Steps to reproduce
amOnPage
action:<amOnPage url="{{AdminLoginPage}}" stepKey="goToAdminLoginPage"/>
vendor/bin/robo generate:tests
Expected result
Can not resolve argument on url attribute for amOnPage action. Step Key: "goToAdminLoginPage".
Actual result
amOnPage
looks like this:$I->amOnPage("{{AdminLoginPage}}");
The text was updated successfully, but these errors were encountered: