#27 resolve service_worker target not showing with current ci

[Anonymous]

Originally created by: craigwh10

We have:

• a service_worker, which is a type available in puppeteer tags
• a content_script which on tab change, it triggers the command amendment handler
• a popup_script which sends messages including changed value payload to content_script to trigger handler with change

https://github.com/craigwh10/dependency_install_swapper/blob/c278444d8c34c0e5f5db000f9ce93673b74319a1/.github/workflows/health-check.js.yml#L29-L44

Shows the commented out jobs, the first uses a shared job to install chrome - which shows to be visible inside the tests.

Currently, the only targets that are being picked up are page and browser, and the tests hang waiting for target.

Have tried increasing timeouts.

https://github.com/marketplace/actions/puppeteer-headful is an option I've tried without much success but is still a viable option

Useful resouce

• https://github.com/craigwh10/dependency_install_swapper/tree/main/ci-test
• This emulates the pipeline environment via a docker image with associate shell scripts to build and see log output in a logfile.
• https://github.com/marketplace/actions/setup-chrome
• https://stackoverflow.com/questions/62228154/puppeteer-fails-to-initiate-in-github-actions
• https://github.com/mujo-code/chrome-extension/blob/master/packages/extension/src/e2e.test.js
• https://github.com/puppeteer/puppeteer/issues/4796 (is an apparent issue in puppeteer-headful)
• https://github.com/marketplace/actions/puppeteer-headful-for-chrome-extension-testing
• https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
• https://stackoverflow.com/questions/50073334/service-worker-installation-in-headless-chrome-via-puppeteer (possibly useful for service_worker task)