Serenity/Screenplay does not permit a web application to be easily testable if it is presented in one or more iframes #532
Comments
nbarrett
pushed a commit
to nbarrett/serenity-core
that referenced
this issue
Oct 27, 2016
…in the TargetResolver
nbarrett
pushed a commit
to nbarrett/serenity-core
that referenced
this issue
Mar 9, 2017
…in the TargetResolver
nbarrett
pushed a commit
to nbarrett/serenity-core
that referenced
this issue
Mar 15, 2018
…in the TargetResolver
wakaleo
added a commit
that referenced
this issue
Mar 16, 2018
Issue #532: feat: added support for iframe switching
wakaleo
added a commit
that referenced
this issue
Mar 18, 2018
…he TargetResolver" This reverts commit a429d6c.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This could probably be done by manually switching frames directly at the driver level but it would be much more elegant if the iframe can be specified in a DRY fashion and for Serenity to take care of the iframe switching automatically. If using Screenplay, the logical place to do this would seem to be at the Target Level.
The text was updated successfully, but these errors were encountered: