Document supported Mocha interfaces - #435
Merged
Merged
Conversation
Clarify that the plugin supports BDD, TDD, and Require, but not Exports, QUnit, or third-party UIs with different syntax. Point wrapper APIs to additionalCustomNames.
lo1tuma
added a commit
that referenced
this pull request
Jul 17, 2026
Document supported Mocha interfaces
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Clarifies which Mocha interfaces the plugin supports.
The README and consistent-interface docs now state that BDD, TDD, and Require are supported, while Exports, QUnit, and third-party UIs with different syntax are not.
Wrapper APIs that still expose suite, test, or hook call functions are pointed to additionalCustomNames.