You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following along with "Testing the Aurelia Skeleton Navigation App".
Looking at the skeleton repository there are questions about whether its still the currently supported way, with the CLI project templates probably being the preferred long term option.
Out of the box this fails because Chrome has moved on since the time this was all setup.
The easiest way for me was to run npm install protractor@^5.0.0 -D and pray that upgrading protractor didn't break anything else, it appears to run successfully.
Is using protractor still the preferred way of doing e2e tests?
Perhaps I need to take you up on looking at the new docs @EisenbergEffect as this is the stuff our company is most deficient in and the one I'm the most keen to get setup correctly.
The text was updated successfully, but these errors were encountered:
We're just about to update all our skeletons, based on what the CLI now generates. The CLI is the preferred way to set things up. It's been difficult to maintain the skeletons apart from that, so we're unifying that shortly.
I'm submitting a bug report
https://aurelia.io/docs/testing/end-to-end#testing-the-aurelia-skeleton-navigation-app
Following along with "Testing the Aurelia Skeleton Navigation App".
Looking at the skeleton repository there are questions about whether its still the currently supported way, with the CLI project templates probably being the preferred long term option.
Out of the box this fails because Chrome has moved on since the time this was all setup.
webdriverio/webdriverio#2631 says to update the chrome driver.
The easiest way for me was to run
npm install protractor@^5.0.0 -D
and pray that upgrading protractor didn't break anything else, it appears to run successfully.Is using protractor still the preferred way of doing e2e tests?
Perhaps I need to take you up on looking at the new docs @EisenbergEffect as this is the stuff our company is most deficient in and the one I'm the most keen to get setup correctly.
The text was updated successfully, but these errors were encountered: