Wrong coverage with function named `error`
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I have to investigate more on what exactly can cause this, but here is the coverage of one of my [files](https://github.com/yanickrochon/co-efficient/blob/master/lib/parser.js) :



I had to add the `console.log` to see if these lines were actually being executed or not...
Especially when the function is actually being called and properly covered.

Contributor guide
No contributing guide indexed for this repository
Research direction
The issue is about incorrect coverage reporting for a function named 'error' in lib/parser.js. Start by examining the coverage tool's instrumentation and reporting logic, likely in the main semcov source files. Reproduce the issue by writing a test that calls the 'error' function and check the coverage output. Look at how function names are tracked and why 'error' might be misreported.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100