[Question] Chrome extension with github action.
See original GitHub issueHi guys,
I have a question. When I am testing my chrome extension locally everything is ok and works perfectly well. But when I run a test inside GitHub action I get this error: Test timeout of 30000ms exceeded while setting up "context".
Is it even possible to test chrome extension inside with Github actions?
My version of playwright: 1.28.1
Here is my test:
Here is my GitHub action:
if you have any questions, feel free to ask!
Issue Analytics
- State:
- Created 10 months ago
- Reactions:4
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to release chrome extension from GitHub repository
There are a few ways to do this: by using npm module (article about that) (suits for you. You can setup script by...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
Now – you'd like to run the build and the tests for 3 browsers – chrome, firefox and Safari. The catch? Safari runs...
Read more >Migrating a JS project from Travis to GitHub Actions
The build itself is just npm ci to install dependencies and then npm test . Although not shown here, some of the npm...
Read more >Best GitHub Chrome Extensions - Rewind Backups
Learn the best Chrome extensions for GitHub developers. ... and users frequently take action such as pushing changes to the codebase or ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Closing as part of the triage process since it seemed stale. Please create a new issue with a detailed reproducible or feature request if you still face issues.
@sleaper I had the same issue and for me it was missing dist folder - I forgot to add build step before test step, check it out