3.9 out of 5
Google doesn't verify reviews. Learn more about results and reviews.
- All reviews
- Recent
- Helpful
- Highest to lowest rating
- Lowest to highest rating
- English
- All languages
Kirill BirgerJan 31, 2024
It only works some of the time, and in the least useful way possible, in a github PR. This functionality should not need an extension, especially not one that requires such permissions
Dmytro SavochkinOct 11, 2023
Only works with small PRs
Lachlan CooperMay 8, 2023
It's nice to see test coverage directly in GitHub, but the extension itself is not very reliable. I often see rendering errors appear at the bottom of PR pages, and files with inline comments are often pushed far over to a single column making them totally unreadable.
Jon WieseSep 28, 2022
Permission to access browser history is now required, which is excessive
Wout SlakhorstSep 28, 2022
Recent changes require the extension access to your browsing history. This is not acceptable. Update: permissions have been restored as before.
Diego SilvaSep 27, 2022
The extension is good, but this new permission to read browser history makes no sense and should not be required.
Brandt LareauMar 25, 2022
Not super reliable and it only shows 20 files of coverage even if there are more in the PR. This would not be a problem if there was a way around the limitation but this extension is the only way.
Viktor KövesFeb 9, 2022
Is it perfect? No, absolutely not. But it's a super helpful extension that can save you a lot of time running around different sites to understand why your code coverage went down. I do wonder though if a cleaner solution would be to improve the Code Climate site to actually have clear coverage change reports on their end.
isratenedaSep 13, 2021
It's useful to see what parts of your code are not tested on GitHub
Leônidas VilleneuveSep 6, 2021
Very slow, only shows up to 25 files.