Implement assertion error messages and more
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- testing-qa
Research direction
Review the follow-up context in #44 and locate the message tests that currently fail because util.inspect is not used. Trace the assertion error-message implementation, then confirm the work is done when the relevant message tests pass with util.inspect-based output.
Written by the indexing model from the issue text.
Description
As a follow-up of #44 it's still required to use util.inspect. That's currently not the case and a lot of message tests fail because of that.
- Dominant language
- JavaScript
- Stars
- 298
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from browserify/commonjs-assert
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
browserify/commonjs-assert#62 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
browserify/commonjs-assert#61 · 7 comments ·
All issues in browserify/commonjs-assert
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100