-
Notifications
You must be signed in to change notification settings - Fork 38
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
How do you simulate clicks on elements? #83
Comments
I'm struggling with a similar issue here (need to test a file upload widget), I'm thinking instead we should expose more of the Phantom API. @arunoda what do you think? Basically on the ClientConnector constructor, store the Phantom page object as this.page instead of a local variable, then we could use the full Phantom API. The one argument against is keeping Laika independent of Phantom… but for true end-to-end testing you need a browser API. (Funny timing you bring this up now, I was just writing that on a local branch!) |
I like the idea of exposing phantom's page object... |
implemented in commit c78bae6, if this looks good to everyone I'll pull-request it edit: I know this isn't “the github way”, I should just make the PR 😸 but I don't want to split the conversation into yet another thread just yet until we're more or less in agreement |
actually there seems to have no good alternative to phantomjs yet. So I'm fine with exposing the page object. |
After I found that jQuery's
$.trigger()
doesn't work I did some googling and came up with a function like this:Is this an issue? Am I doing something completely wrong here?
If there's no other way to do this then a function like this should probably be shipped with laika. What do you think?
The text was updated successfully, but these errors were encountered: