This is, essentially, documentation for future developers.
The e2e tests tend to break every once in a while; not because of a mismatch between the tested behaviour and the actual behaviour, but because of subtle dependency issues involving Angular, Protractor, Selenium and various WebDriver implementations (in this particular case: Chrome and Firefox). It can be fixed, either by downgrading a browser, or by manually adjusting dependency version numbers in the package.json file of the protractor npm package or one of its dependencies (forgot which).
This problem is inherent to the use of Protractor and Selenium.
The content of the current e2e tests may or may not be up to date. Fixing the tests again in order to verify this is not important enough right now.
This is, essentially, documentation for future developers.
The e2e tests tend to break every once in a while; not because of a mismatch between the tested behaviour and the actual behaviour, but because of subtle dependency issues involving Angular, Protractor, Selenium and various WebDriver implementations (in this particular case: Chrome and Firefox). It can be fixed, either by downgrading a browser, or by manually adjusting dependency version numbers in the
package.jsonfile of the protractor npm package or one of its dependencies (forgot which).This problem is inherent to the use of Protractor and Selenium.
The content of the current e2e tests may or may not be up to date. Fixing the tests again in order to verify this is not important enough right now.