Cross-browser testing strategy

[giorgiosironi]

Long-term solution for https://github.com/elifesciences/elife-xpub/issues/1004

User Story:

As a product owner I want the key flow in launch not to break in order to avoid losing submissions coming from particular browsers and platforms and/or irritating users asking them to change their browser.

Product requirements/Acceptance criteria:

Non-functional:

• TBD

May depends on https://github.com/elifesciences/elife-xpub/issues/932 if we take advantage of that.

[giorgiosironi]

There are 1 or more ways we may go at this:

• in-project testing using Selenium, should cover the user interface while using simulators for all integrations
• end2end testing using Selenium, if possible avoid as you don't need the whole stack of multiple projects to discover a cross-browser issue
• extend the Selenium Firefox/Chrome support (easy to run in Docker) with BrowserStack/SauceLabs/similar. May be easy to run in public environments rather than locally, both for credentials and access.
• exploratory testing performed by humans for obscure cases or combinations, often with the aid of an external service BrowserStack/SauceLabs/similar.

/cc @diversemix @davidcmoulton @discodavey

[giorgiosironi]

Related to https://github.com/elifesciences/elife-xpub/issues/399, but functional rather than visual (covering input bugs rather than look and feel)

[hdrury1]

Re-naming given that we don't have an overall strategy for this that I'm aware of.