Research various JS testing frameworks

[hoch]

• Research various JS testing frameworks (e.g. An article from BrowserStack)
• Prioritize frameworks that offer robust support for asynchronous testing and mocking of Web Audio APIs

[hoch]

@terryzfeng @Kizjkre I think we can use this issue to record/document the research. What do you think?

[hoch]

This looks pretty comprehensive, but I haven't checked on how to capture/analysis audio output: https://playwright.dev/

[hoch]

Some criteria to consider:

• Widely known and stable.
• Less overhead is better; we only need something that can run/measure the Web Audio API.
• It can run the realtime AudioContext and capture the rendered audio result.
• It can measure the audio rendering performance.
• (Stretch) It can run on the latest Chromium automatically via GitHub's CI.

[terryzfeng]

Base Questions: Which test frameworks are:

1. Easy to use / documented
2. Realtime use and Headless (for CI)
3. Uses actual audio driver

[terryzfeng]

Here is the research/findings/documentation I have for the Playwright framework. Learning Playwright became quite involved and I needed to write myself a README.

https://docs.google.com/document/d/1e7G9jc4kuVZWvjylTtFE76DzQBsOG6lZSFmV19Kc5cY/edit

[Kizjkre]

The two branches in this repo has two prototypes: one using Puppeteer and one using just client-side code.

https://github.com/Kizjkre/puppeteer-webaudio-test

[Kizjkre]

--autoplay-policy=no-user-gesture-required is a pretty useful argument to have.

[terryzfeng]

@Kizjkre I added no-user-gesture-required which worked with Chrome but it doesn't look like Firefox supports it, so the tests weren't compatible.. I couldn't quite figure out the flags

[terryzfeng]

Linking the PR for Playwright: https://github.com/GoogleChromeLabs/web-audio-samples/pull/368