Getting protractor to click button in rapid succession WITHOUT waiting
up vote
0
down vote
favorite
This is pretty ironic because every single answer I came across while looking for the solution is explicitly trying to accomplish the exact reverse.
I'm trying to write a test case to ensure that my button that fires off a POST request doesn't respond to clicks beyond the first one in case someone has a habit of doubleclicking buttons. I have ignoreSynchronization set to true but the clicks apparently wait for the page load, so by the time the second click triggers, the button can no longer be found because the application advanced to the next page. I have also tried to trigger the click outside of protractor itself, but because the mechanism I'm using to disable the button is CSS-based (pointer-events: none), clicks triggered via javascript ignore the attribute and trigger the event anyway.
I have tried:
- Using browser.actions to do doubleclicks
- Calling
element.click()twice - Using
browser.executeScriptto trigger the click event. - Busywaiting on the mouse click handler so that protractor can get in the clicks
- Introducing delay on the mockjax response so that protractor can get in the clicks
Any help would be appreciated.
Note: My application doesn't actually use angular :X
javascript unit-testing protractor
asked Nov 22 at 9:55
tacobot
112
add a comment |
up vote
0
down vote
favorite
This is pretty ironic because every single answer I came across while looking for the solution is explicitly trying to accomplish the exact reverse.
I'm trying to write a test case to ensure that my button that fires off a POST request doesn't respond to clicks beyond the first one in case someone has a habit of doubleclicking buttons. I have ignoreSynchronization set to true but the clicks apparently wait for the page load, so by the time the second click triggers, the button can no longer be found because the application advanced to the next page. I have also tried to trigger the click outside of protractor itself, but because the mechanism I'm using to disable the button is CSS-based (pointer-events: none), clicks triggered via javascript ignore the attribute and trigger the event anyway.
I have tried:
- Using browser.actions to do doubleclicks
- Calling
element.click()twice - Using
browser.executeScriptto trigger the click event. - Busywaiting on the mouse click handler so that protractor can get in the clicks
- Introducing delay on the mockjax response so that protractor can get in the clicks
Any help would be appreciated.
Note: My application doesn't actually use angular :X
javascript unit-testing protractor
asked Nov 22 at 9:55
tacobot
112
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This is pretty ironic because every single answer I came across while looking for the solution is explicitly trying to accomplish the exact reverse.
I'm trying to write a test case to ensure that my button that fires off a POST request doesn't respond to clicks beyond the first one in case someone has a habit of doubleclicking buttons. I have ignoreSynchronization set to true but the clicks apparently wait for the page load, so by the time the second click triggers, the button can no longer be found because the application advanced to the next page. I have also tried to trigger the click outside of protractor itself, but because the mechanism I'm using to disable the button is CSS-based (pointer-events: none), clicks triggered via javascript ignore the attribute and trigger the event anyway.
I have tried:
- Using browser.actions to do doubleclicks
- Calling
element.click()twice - Using
browser.executeScriptto trigger the click event. - Busywaiting on the mouse click handler so that protractor can get in the clicks
- Introducing delay on the mockjax response so that protractor can get in the clicks
Any help would be appreciated.
Note: My application doesn't actually use angular :X
javascript unit-testing protractor
asked Nov 22 at 9:55
tacobot
112
This is pretty ironic because every single answer I came across while looking for the solution is explicitly trying to accomplish the exact reverse.
I'm trying to write a test case to ensure that my button that fires off a POST request doesn't respond to clicks beyond the first one in case someone has a habit of doubleclicking buttons. I have ignoreSynchronization set to true but the clicks apparently wait for the page load, so by the time the second click triggers, the button can no longer be found because the application advanced to the next page. I have also tried to trigger the click outside of protractor itself, but because the mechanism I'm using to disable the button is CSS-based (pointer-events: none), clicks triggered via javascript ignore the attribute and trigger the event anyway.
I have tried:
- Using browser.actions to do doubleclicks
- Calling
element.click()twice - Using
browser.executeScriptto trigger the click event. - Busywaiting on the mouse click handler so that protractor can get in the clicks
- Introducing delay on the mockjax response so that protractor can get in the clicks
Any help would be appreciated.
Note: My application doesn't actually use angular :X
javascript unit-testing protractor
javascript unit-testing protractor
asked Nov 22 at 9:55
tacobot
112
asked Nov 22 at 9:55
tacobot
112
asked Nov 22 at 9:55
tacobot
112
asked Nov 22 at 9:55
tacobot
112
asked Nov 22 at 9:55
tacobot
112
112
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428237%2fgetting-protractor-to-click-button-in-rapid-succession-without-waiting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
