Module manager test

[govza]

* denotes required fields

Priority*

• High: This PR needs to be merged first, before other tasks.
• Medium: This PR should be merged quickly to prevent conflicts due to common changes. (default)
• Low: This PR does not affect other tasks, so it can be merged later.

Purpose of the PR*

Run tests for separated features

Changes*

Created e2e-moduler GH workflow

How to check the feature

1. pnpm module-manager --de tests random-module
2. pnpm run e2e
3. pnpm module-manager -r random-module
4. pnpm run e2e

Closes #937

[PatrykKuniczak]

What determines the current browser for pnpm e2e ?

Browser on which we're currently are or what?

And tests run will iterate on both browsers and run tests for both?

And fix CodeQL issues.

And it isn't possible to run it on local machine, only on CI, are you think about to add it also as a package.json script?

[govza]

What determines the current browser for pnpm e2e ?

Browser on which we're currently are or what?

And tests run will iterate on both browsers and run tests for both?

And fix CodeQL issues.

And it isn't possible to run it on local machine, only on CI, are you think about to add it also as a package.json script?

pnpm e2e runs by default on chrome, pnpm e2e:firefox runs on firefox
the matrix strategy defined in workflow allows to run them altogether in parallel,
It's possible to run it locally since it's just - remove all module, - run e2e, - restore random module, - run e2e,
but I don't see any use-case for it.

IDK how to trigger them here, before merge, but they were running on my fork
https://github.com/govza/chrome-extension-boilerplate-react-vite/actions/runs/15101977726

[PatrykKuniczak]

@govza I'm also wondering about use case of local run, and i think we can skip it, because it should work only on CI.

And why it isn't working here, i don't freaking know, i was trying everything to get knowledge, why it can't work.
I see you have pull_request_target and i think it should work, let's set permissions: write-all for test, and check it then.

But overall there's something wrong with settings of repo, because on my fork it also works better.
@Jonghakseo need to take a look on that problem deeper.

[PatrykKuniczak]

LGTM very good work :)