If you run “forge coverage” in a foundry project, you’ll get a table showing how much of your lines and branches are covered.
If you want to see visually which lines and branches are or are not covered, use the following steps
brew install genhtml
mkdir coverage
forge coverage --report lcov && genhtml lcov.info --branch-coverage --output-dir coverage
coverage/index.html
And you’ll be able to see a coverage report like what you see at the top of the page.
If you get this error, do
brew install ekhtml
and it will install genhtml.
This tutorial was created by Matteo Vendittoli, a student at the RareSkills blockchain bootcamp.
It is also possible to view line coverage directly inside Visual Studio Code. Credit to 0xasp_ on Twitter for sharing this with us (original tweet).
forge coverage --report lcov
Pick display coverage report
Originally Published Feb 8, 2023
20 Common Solidity Beginner Mistakes Our intent is not to be patronizing towards developers early in their journey with this article. Having reviewed code from numerous Solidity developers, we’ve seen some mistakes occur more frequently and we list those here. By no means is this an exhaustive list of mistakes a Solidity developer can make. […]
Smart Contract Foundry Upgrades with the OpenZeppelin Plugin Upgrading a smart contract is a multistep and error-prone process, so to minimize the chances of human error, it is desirable to use a tool that automates the procedure as much as possible. Therefore, the OpenZeppelin Upgrade Plugin streamlines deploying, upgrading and managing smart contracts built with Foundry or […]
UUPS: Universal Upgradeable Proxy Standard (ERC-1822) The UUPS pattern is a proxy pattern where the upgrade function resides in the implementation contract, but changes the implementation address stored in the proxy contract via a delegatecall from the proxy. The high level mechanism is shown in the animation below: Similar to the Transparent Upgradeable Proxy, the […]
Try Catch and all the ways Solidity can revert This article describes all the kinds of errors that can happen when a smart contract is called, and how the Solidity Try / Catch block responds (or fails to respond) to each of them. To understand how Try / Catch works in Solidity, we must understand […]
As a RareSkills researcher, you will be contributing to the technical content we post on our website.
We’re looking for someone to design and implement security measures and defense-in-depth controls to prevent and limit vulnerabilities.
We’re looking for a Senior Full-Stack Engineer to play a foundational role in working across the entire offchain stack of products.
We are seeking a talented Rust Developer to build a robust, scalable blockchain indexers and analytic backend.