Acceptance tests fail for prod builds of pass-ui

[jabrah]

Parts of the current acceptance tests use data-test-* attributes to select certain elements for inspection, but these data attributes are stripped from the HTML for production builds. This is by design in the Ember build process, as these attributes are intended to be used for Ember tests.

We'll need to rewrite those parts of the acceptance tests that utilize these selectors to use other selectors. This may involve adding new element IDs where necessary

[jabrah]

As a temporary hold over, we can configure the Ember builds to not strip the selectors for prod builds: https://github.com/mainmatter/ember-test-selectors#configuration

[jabrah]

Currently rewriting the selectors to not use the data-test-* attributes. This will work in the short term, but is not readable and will make updating and/or adding tests a bit painful. A better solution will be to add IDs to important UI elements and make sure the UI templates make sense semantically.

We should also look into making the authoring of tests easier. We could look at setting up Page Models in Testcafe, basically creating a page level API for interacting with the UI in tests

[jabrah]

eclipse-pass/pass-acceptance-testing#8
eclipse-pass/pass-ui#1191

Decided to keep the data-test-* attributes in prod builds after all. The don't add extra information and only increase bundle size a small amount.

Ran into issues running the acceptance tests in my Windows environment, even though they ran without issue in other environments (Linux, Mac)