Sebastian Zimmeck

@katehausladen, did you add an entry/updated to the Wiki (quirks/known issues section)?

Oh, OK, I saw you mentioned above. Nevermind.

As we discussed, @sophieeng will spend another three weeks or so on this issue and #365.

@sophieeng, maybe use a different test framework? Can you check whether the following work (in that order): 1. [Vitest](https://vitest.dev/) ("Out-of-box ESM, TypeScript and JSX support powered by esbuild") 2. [AVA](https://github.com/avajs/ava)...

In our meeting today, @sophieeng clarified the two tasks to perform: 1. **Build process**: Our build process with webpack is the major obstacle of a pure ECMAscript solution for our...

As discussed, @sophieeng will take the lead on unit testing and continuous integration. This is a more of an experimental phase at the moment. What technologies do we use, how...

Great! Jest goes back to a suggestion by @lr-brown. Both @lr-brown and @jjeancharles are working on unit testing and CI for [Privacy Pioneer](https://github.com/privacy-tech-lab/privacy-pioneer). So, if it is helpful, please sync...

As discussed, @sophieeng will start a test folder, start compiling a list of features to test, and implement a few tests.

One important limitation (of any/most unit testing frameworks) is that we cannot test the UI fully. For example, if there is a pure display issue, e.g., a string is correctly...

> does browser matter? Like do firefox and chrome need different test, especially for Analysis mode which is only for ff. If there are differences in implementation, we could think...