• Check out https://www.cypress.io/ and https://devexpress.github.io/testcafe/ (Cawemo uses the latter because it works with multiple browsers)
• Choose one
• Write an E2E test suite for Cockpit (should cover simple scenarions as well as scenarios that we can currently not test reliably - check with Michael)
• Run a couple of times on Jenkins to assess build stability
• Assess and compare with our current protractor-based solution; aspects: stability, ease of writing tests, test execution time, concept, supported browsers, ...

Assesment
General

• supported Browsers
  Chrome, FF, IE11, Edge
  Does not require selenium, uses Proxy URL rewriting (similar to Selenium1, but handles edge cases better)

• Automated testing on IE11 using Browserstack proved to be unreliable. This might be caused by Browserstack as well as TestCafe

Selenium supports Chrome, FF, IE (but requires some configuration)

• We only use Chrome tests: Writing cross-browser selectors proved to be a problem in the past, this can't be solved by TestCafe

Pros

• Little bootstraping, easy to run
• Tests are easy to setup, offer all hooks currently used by our solution
• Migration of tests was straight forward

Cons

• no nested Tests (Instead of nested describe, only offers fixture and test)
• User Concept not compatible with our auth system
  Workaround: login for every test seperately
  makes simple tests (can be accessed, has tabs, ...) unneccessarily slow
  adds a potential point of failure
• loading of Translate Strings can be an issue when starting every test without cache