Feature #42253
Updated by Stephan Müller over 4 years ago
In order to make it easier for contributors to write frontend tests, we need to define and document what valid tests are.
It should cover e.g. (some ideas, please correct me or add additional ones):
* General introduction about testing and e2e/unit tests
* What are e2e/unit tests designed for?
* Which e2e/unit tests are considered to be valid?
* How should an e2e/unit test look like?
* What should an e2e/unit test cover?
* What should an e2e/unit test NOT cover?
* Best practices/examples/howtos
https://www.protractortest.org/#/faq#what-s-the-difference-between-karma-and-protractor-when-do-i-use-which-
https://www.yearofmoo.com/2013/09/advanced-testing-and-debugging-in-angularjs.html#so-what-tool-do-we-use-to-perform-testing
https://testingjavascript.com/
https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html