Mocha jest migration #207
Open
Mocha jest migration #207
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Putting emitted Typescript etc. into dist/ folder, as to make doing cleans of builds cleaner to exorcise the demon of ts-emit-clean from the codebase once and for all.
Migrating from mocha to jest to move to more current unit testing tools that will place nicer with the VSCode debugger.
Owner
|
Look, I'm cherry-picking all the new commits from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Experimental migration away away from mocha to jest. The goal is to be able to easily debug individual recast unit tests with a single click (via the VSCode Jest extension). Easing debuggability should increase incentive for people to make fixes.