agnivade/wasmbrowsertest

Issues

• Flaky test TestRun/panic_fails in Windows

  #59 opened 16 days ago by agnivade
  3

• getting a webgl context fails on macOS

  #57 opened 19 days ago by hajimehoshi
  5

• Is there away to click "OK" on an alert window?

  #55 opened 16 days ago by fs111
  2

• Accept permission

  #25 opened 3 years ago by inkeliz
  2

• A way to test WASM aims to be run in the web worker

  #50 opened 8 months ago by magodo
  10

• update documentation regarding go 1.20 coverage tools

  #51 opened 5 months ago by mlctrez
  3

• error generating coverage report

  #46 opened 8 months ago by mlctrez
  7

• cross browser testing

  #32 opened 8 months ago by joeblew99
  5

• `total length of command line and environment variables exceeds limit` in GitHub Actions

  #40 opened a year ago by hajimehoshi
  27

• using -- to signify end of options

  #33 opened 2 years ago by FrankReh
  8

• Error: command line too long

  #30 opened 3 years ago by realPy
  6

• goroutine support

  #29 opened 3 years ago by unicomp21
  14

• Is there an example dockerfile?

  #28 opened 3 years ago by unicomp21
  1

• please enable discussions on this repo

  #27 opened 3 years ago by unicomp21
  4

• Support -shuffle flag

  #23 opened 3 years ago by hajimehoshi
  1

• `could not dial` errors on the latest Chrome on GitHub Actions

  #22 opened 3 years ago by hajimehoshi
  4

• wasmbrowsertest taking too long and not printing any output

  #15 opened 4 years ago by nhooyr
  39

• "panic: newosproc: not implemented" when executing in travis

  #16 opened 4 years ago by wizardishungry
  1

• Run examples

  #14 opened 4 years ago by orsinium
  12

• Need GPU disabled in chromedp to run

  #10 opened 4 years ago by Gregory-Ledray
  17

• Tests work in real Chrome in Windows but not chromedp in WSL

  #12 opened 4 years ago by Gregory-Ledray
  1

• Support collecting code coverage

  #5 opened 5 years ago by nhooyr
  7

• Support passing through environment variables

  #6 opened 5 years ago by nhooyr
  3