Testing the Aurelia Skeleton Navigation App no longer works

**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.

https://github.com/webdriverio/webdriverio/issues/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.

Start with the “Testing the Aurelia Skeleton Navigation App” page and reproduce its end-to-end setup in the linked skeleton repository. Check the referenced WebdriverIO issue and the current Protractor/Chrome-driver compatibility before deciding what the documentation should recommend. Done means the documented setup works with current dependencies and the page clearly describes the supported approach.

Written by the indexing model from the issue text.