Content
View differences
Updated by Oliver Günther over 1 year ago
**As** a developer
**I want to** verify the code I write works as intended
**so that** we can can ship fast with confidence
**Acceptance criteria**
* Figure out what components we currently have tests for (pretty much Angular components only).
* Investigate what is needed to get the current test suite running green - both locally and on CI.
* Do an inventory of components and miscellaneous JS/TS code that does not currently have test coverage.
* Evaluate the current state of test frameworks and runners in the JS/TS ecosystem - and decide what will be the best fit for our future needs.
* Notes Oliver:
* We probably still want to test some angular web components such as the autocompleters
* Apart from that, we will likely have limited testing for reusable stimulus behaviors
* Develop some initial (very rudimentary) best practice guidelines, as well as infrastructure for testing frontend code going forward.
<br>
**I want to** verify the code I write works as intended
**so that** we can can ship fast with confidence
**Acceptance criteria**
* Figure out what components we currently have tests for (pretty much Angular components only).
* Investigate what is needed to get the current test suite running green - both locally and on CI.
* Do an inventory of components and miscellaneous JS/TS code that does not currently have test coverage.
* Evaluate the current state of test frameworks and runners in the JS/TS ecosystem - and decide what will be the best fit for our future needs.
* Notes Oliver:
* We probably still want to test some angular web components such as the autocompleters
* Apart from that, we will likely have limited testing for reusable stimulus behaviors
<br>