Codecov has all the details on me somewhat flailing around trying to figure this out. At this point, I’m unsure of whether this failure is being caused by invalid paths or targeting the incorrect file in my configuration, so I’m somewhat at a loss here.
Hi @seanoshea, looks like there might be an issue with how you are collecting coverage. This is the raw report, and I’m only seeing coverage for this file
Hi @seanoshea, I think this is a path fixing issue. However, the thing that worries me is that the coverage report is coming from a dist folder, and I’m assuming you want coverage on src. I just want to double-check that you are running coverage on src files and not post-compiled ones.
If you don’t think that’s an issue, you can try adding
fixes:
- "/home/circleci/project/dist/::src/lib/"
to your codecov.yml
I can’t guarantee that Codecov will be able to understand that the file fuzzymatchingjs.cjs.js is actually fuzzingmatching.js, however. And I believe it won’t be able to properly handle the wrong filename here. I’m actually fairly certain this will not work and you’ll need to run coverage against your src files.
Thank you for your patience as you guided me through this. You mentioning that I was targeting the dist folder instead of the src folder prompted me to make some changes. https://github.com/seanoshea/fuzzymatchingjs/pull/13 is the result. I think the code coverage reports are coming through fine now.