Giters
agnivade
/
wasmbrowsertest
Run WASM tests inside your browser
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
177
Watchers:
7
Issues:
21
Forks:
23
agnivade/wasmbrowsertest Issues
Is there away to click "OK" on an alert window?
Updated
3 months ago
Comments count
1
Accept permission
Updated
4 months ago
Comments count
2
A way to test WASM aims to be run in the web worker
Updated
4 months ago
Comments count
10
update documentation regarding go 1.20 coverage tools
Closed
4 months ago
Comments count
3
error generating coverage report
Closed
7 months ago
Comments count
7
cross browser testing
Closed
7 months ago
Comments count
5
`total length of command line and environment variables exceeds limit` in GitHub Actions
Closed
a year ago
Comments count
27
using -- to signify end of options
Closed
2 years ago
Comments count
8
Error: command line too long
Closed
2 years ago
Comments count
6
goroutine support
Closed
3 years ago
Comments count
14
Is there an example dockerfile?
Closed
3 years ago
Comments count
1
please enable discussions on this repo
Closed
3 years ago
Comments count
4
Support -shuffle flag
Closed
3 years ago
Comments count
1
`could not dial` errors on the latest Chrome on GitHub Actions
Closed
3 years ago
Comments count
4
wasmbrowsertest taking too long and not printing any output
Closed
4 years ago
Comments count
39
"panic: newosproc: not implemented" when executing in travis
Closed
4 years ago
Comments count
1
Run examples
Closed
4 years ago
Comments count
12
Need GPU disabled in chromedp to run
Closed
4 years ago
Comments count
17
Tests work in real Chrome in Windows but not chromedp in WSL
Closed
4 years ago
Comments count
1
Support collecting code coverage
Closed
5 years ago
Comments count
7
Support passing through environment variables
Closed
5 years ago
Comments count
3