Hello,
We are implementing the primeng elements. When creating automated tests with protractor, we are experimenting problems on the spinners. The same problems we've noticed on the examples from: https://www.primefaces.org/primeng/#/spinner
To provide more details:
Here is the project: https://codesandbox.io/s/primengprotractor-cmq6s
In this example after the first click the search no longer works. Code blocked after line 23.
Can you help with this? We also noticed that after clciking the up button this element remains somehow "focused" so probably there is a miswsing mouseMove which then does not trigger mouseOut.
Thank you!
That's exactly what we experienced as well. We have to xit() all our e2e tests that involve a spinner.
AFAIK, the reason the spinner is not e2e testable using Protractor is the usage of setTimeout() within the spinner component.
The same problem occured with the growl component and it seems it got fixed by wrapping the setTimeout() into runOutsideAngular(). See https://github.com/primefaces/primeng/issues/4681
Any update on this?
Most helpful comment
That's exactly what we experienced as well. We have to xit() all our e2e tests that involve a spinner.
AFAIK, the reason the spinner is not e2e testable using Protractor is the usage of
setTimeout()within the spinner component.The same problem occured with the growl component and it seems it got fixed by wrapping the
setTimeout()intorunOutsideAngular(). See https://github.com/primefaces/primeng/issues/4681