shellscape/mocha-chrome

Issues

• Is this still maintained?

  #46 opened 3 years ago by steevhise
  3

• how to debug, mocha-chrome not detecting mocha.run

  #43 opened 4 years ago by acthp
  0

• test failures with recent builds of chrome

  #32 opened 5 years ago by Spongman
  3

• mocha's output is always uncolorified

  #40 opened 5 years ago by gamtiq
  2

• Feature request: Pass args to chrome

  #16 opened 5 years ago by GordonSmith
  17

• net::ERR_INSECURE_RESPONSE when protocol is https

  #1 opened 5 years ago by ferbs
  1

• With xunit reporter, output is inconsistent, and output option can't be set

  #34 opened 5 years ago by acthp
  1

• Unicode characters become garbled on Windows

  #18 opened 5 years ago by jgranick
  7

• Custom reporter suggestion

  #29 opened 6 years ago by gsmeets
  1

• feature request: override default chrome parameters

  #28 opened 6 years ago by Spongman
  3

• 'Error: no test specified'

  #27 opened 6 years ago by channg
  0

• Ability to save results to file, like mocha-phantomjs

  #25 opened 6 years ago by dietergeerts
  4

• Add a pre exit hook

  #14 opened 7 years ago by stoffeastrom
  4

• test failure results in orphaned chrome.exe processes

  #24 opened 7 years ago by Spongman
  7

• Feature request: Allow customization/confguration of the mocha start timeout

  #19 opened 7 years ago by ivrtaric
  5

• Incorrect `mocha.run()` called with no tests

  #13 opened 7 years ago by stoffeastrom
  11

• Add support of Node 6.x

  #8 opened 7 years ago by pgn-vole
  4

• mocha-chrome: unexpected token

  #10 opened 7 years ago by robhicks
  6

• Unexpected token function

  #9 opened 7 years ago by kettanaito
  1