-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Support for Multiremote #106
Comments
This comment has been minimized.
This comment has been minimized.
@christian-bromann Is there a workaround you would recommend for right now? Currently I have a solution that works with chai that looks like this ` export const messageDevices = ( const test = async () => { The problem I have with this approach is that $() returns a type of Promise<WebdriverIO.Element>; |
@christian-bromann is there any movement on this? |
That would be idea, see the |
@evilC @DerekCL i have been able to work around this with my current setup i have been building out, which involves defining each browser separately for tests. for example at the top of a test file, i have the following in order to use multiremote with two different instances of chrome (both defined in then within the test, you can use expect based upon each browser individually. like, |
@amandaflagg it would be however also nice to be able to make assertion for one command on both browsers, e.g.: expect(browser).toHaveTitle(["titleA", "titleB"]) Maybe we can even allow a fancier syntax like: expect(browser).toHaveTitle({
mobileChromeBrowser: "titleA",
chromeBrowser: "titleB"
}) |
Allow users to use this assertion library with multiremote. Using the
isMultiremote
flag of thebrowser
object should help to determine the current mode and allows to then iterate over the multiremote instances to do separate assertions.The text was updated successfully, but these errors were encountered: