juergba on inspect-timeout
fix: disable of timeout order o… additional test (compare)
next. First there are important PR's in
v7.0.0which finally should be published like dropping Node v6. Second the older the
release/v6.2.xbranch gets, the more conflicting gets the
cherry-picking, eg. I can't tell you the implications when we release some PR's of my
uncaughtExceptionstuff now and the rest later ... It just gets too complicated and too risky (for me).
await. Default remains ES5 (=> IE11).
@Munter I'm unsure about the
browserify process, regarding ignored files. We have three informations:
I have two questions:
landed-on-v6.2.xwhich doesnt seem right as we havnt released
6.2.3yet (and mite opt for v7 instead). Can u confirm if ok to remove pls. Im starting on CHANGELOG for 7.
landed-on-v6.2.xshould be removed.
Sorry, I tried to update my last answer, but edit was grayed out.
I'm now running into a new error it doesn't matter which html template I am using for the browser tests I am now getting this error:
mocha.js:9 Uncaught ReferenceError: require is not defined at mocha.js:9
The two templates are under docs folder and browser folder
Here is the template I'm using:
I reviewed the contributing guidelines and it said if you are doing something browser based it's likely a change under bin / lib browser-entry.js
I am trying to get my html template to recognize my local version of mocha so that I can make changes to the way that the browser based tests display results.
I have tried using the mocha.js file under bin and lib and I get the same error either way. Need help figuring out how to get my local mocha app recognized on this template.
Thanks for any help provided!
lib/reporters/html.jsto change the reporter output, then run
npm run buildto build/bundle
/mocha.js. load this file to see your changes
I followed the instructions above for bundling together the root mocha.js file.
my steps were as followed:
under docs -> example -> tests.html
under reporters -> html.js
I started with a simple change for proof of concept:
under statsTemplate variable changed failures -> failure
from the cli:
ran npm build ./
which completes without error
I then open tests.html in a chrome browser and still see the s at the end of failures under statsTemplate ul area?
npm start build
nps is executing `build` : browserify -e browser-entry.js --plugin ./scripts/dedefine --ignore 'fs' --ignore 'glob' --ignore 'path' --ignore 'supports-color' -o mocha.js
@juergba Will do.
Yikes, that's not a good error for a CDN to send out
6:16:47 PM: --- 6:16:47 PM: operator: load 6:16:47 PM: expected: "200 https://unpkg.com/mocha/mocha.css" 6:16:47 PM: actual: "HTTP 429 Too Many Requests" 6:16:47 PM: at: docs/_site/example/tests.html:6:34 <link rel="stylesheet" href="https://unpkg.com/mocha/mocha.css"> 6:16:47 PM: ...