Skip to content

Conversation

@mark-wiemer
Copy link
Member

PR Checklist

Overview

  • Contributing and development were a bit overlapped in that both covered writing code to some degree
  • Development was very outdated, recommending Node 14
  • Neither had clear instructions for repro'ing an issue
  • Neither had clear instructions for using the DEBUG environment variable

Yes, this PR is mostly for myself :D

@codecov
Copy link

codecov bot commented Nov 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.41%. Comparing base (e923e40) to head (042b516).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5538   +/-   ##
=======================================
  Coverage   88.41%   88.41%           
=======================================
  Files          66       66           
  Lines        4792     4792           
  Branches      977      977           
=======================================
  Hits         4237     4237           
  Misses        555      555           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.


## Reproducing issues

We recommend creating a folder named `sandbox` within this repo, and then using a child project within `sandbox` for each issue you want to repro.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually have a different repro flow. I keep a folder at ~/repos/repros as a sibling to ~/repos/mocha. It's a Git repo with a branch for each test case / reproduction. The publicly interesting ones get pushed to https://github.com/JoshuaKGoldberg/repros.

Alternately, sometimes I use ~/repos/mocha-examples to get starting reproductions. It's pretty handy.

I don't think we should recommend such a specific usage flow. Not every user is going to want this.

Proposal: how about making this more general, like saying having some folder somewhere?

We recommend creating a folder named `sandbox` within this repo, and then using a child project within `sandbox` for each issue you want to repro.

`package.json` will have a reference to the local Mocha build and any options you need for your repro.
We recommend [`cross-env`](https://www.npmjs.com/package/cross-env) for applying the `DEBUG` environment variable to get detailed logs (via the [`debug`](https://www.npmjs.com/package/debug) package).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cross-env is only useful if you're on Windows. If you're on Mac or Linux then you can omit it.

@JoshuaKGoldberg JoshuaKGoldberg added the status: waiting for author waiting on response from OP or other posters - more information needed label Dec 18, 2025
Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>
@mark-wiemer
Copy link
Member Author

Thanks for the review :) I'll come back to this after Christmas

@mark-wiemer mark-wiemer removed the status: waiting for author waiting on response from OP or other posters - more information needed label Jan 3, 2026
@mark-wiemer
Copy link
Member Author

(Removed "waiting for author" label as, well, it doesn't feel right when the author is a maintainer!)

@mark-wiemer mark-wiemer added this to the Chores milestone Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

📝 Docs: Unclear how to consistently repro issues

2 participants