Allow running actions before taking screenshots
cameron-martin opened this issue · comments
Cameron Martin commented
There are a couple of options here that I can see:
- Expose an implementation-specific object from the
Browser
implementation, for example aPage
object in the respective underlying frameworks. - Expose an abstraction that implements common actions, e.g. hiding elements by selector, clicking elements by selector, etc, as well as an escape hatch of executing arbitrary js.
Which is best?