Christopher Hiller

Results 256 issues of Christopher Hiller

I like the output codecov.io gives in its integration. Example: ![image](https://user-images.githubusercontent.com/924465/58994661-2b29ee80-87a6-11e9-89ef-dd03c6f167ee.png) The graphical stuff is kind of useless, but it provides good contextual information otherwise. @mochajs/core anyone have an opinion...

status: accepting prs
type: chore
area: repository tooling
core-team

when we transitioned to Rollup/Babel, we misconfigured Babel such that all language APIs polyfilled by `core-js` would be accessible not just by Mocha, but by tests and code under test....

type: bug
semver-patch

This would really help teams that have very large test suites. I am not sure exactly how other test frameworks accomplish this, but I can think of a few strategies....

type: feature
status: accepting prs
area: usability
area: node.js

I have a couple ideas for improvements here now that we're past the MVP: 1. Detect if we're only running a single file, and disable parallel mode automatically. Running a...

type: feature
status: accepting prs
semver-major
area: parallel mode

As part of PR #4241, I was tweaking a few things in our test helper module, which helps Mocha call itself in a child process for end-to-end testing. It got...

type: chore
area: repository tooling
core-team
status: in discussion

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify. We may be able...

status: accepting prs
type: chore
area: repository tooling
core-team

We need plugin API(s). More to follow.

type: feature
future
status: in discussion

In the timeout-handling code in `Runnable#resetTimeout`, if `_enableTimeouts` was `false`, Mocha would completely avoid setting a timer, even if the timeout was set to `0`. This PR changes the behavior...

type: bug
semver-patch
area: node.js
status: in triage

I identified a use case for a custom JSDoc tag in our source. Let's tag code that exists for the sole purpose of supporting a particular environment. Then, if/when we...

type: feature
status: accepting prs
area: repository tooling

Currently, only the `mochajs.org` branch will be published whenever it's updated. That's fine for ensuring our site doesn't reflect `master`, but what we should *really* do is have multiple sites--e.g.,...

type: feature
status: accepting prs
area: documentation
core-team