Uploaded October 2022 | Updated September 2026, 2 weeks ago
Coveralls is a website that provides reporting and visibility into code test coverage for a project repository. While code coverage in and of itself doesn't speak to the quality or relevance of software tests, it does provide visibility into places where you may have accidentally neglected to cover your code. It's free for open-source projects and provides transparency into your code coverage metrics for those who are evaluating whether to use or incorporate your open source project.
In this video, we adapt a previous implementation of Coveralls from our NerdDice RubyGem to our Rails 7 project. Instead of following the official documentation on the Coveralls website, we instead use the simplecov-lcov and coveralls_reborn gems.
Gotchas: Be sure to add the coverage/ folder to your .gitignore file. In this video, we make the mistake of neglecting to do so and show you how to recover from it.
This video covers:
00:00:12 Introduction and review solution from NerdDice RubyGem
00:03:21 Visit Coveralls site and add nerd_dice_dot_com repo
00:04:39 Install the required gems
00:05:55 Add coverage status badge into README
00:08:36 Add SimpleCov configuration to TestHelper
00:10:33 Uncomment and adapt code in main.yml of Github Action
00:12:40 Review the local SimpleCov report in a browser
00:14:17 Initial push of the changes, check on build, review on Coveralls
00:17:31 Restore sample tests from previous video and ensure it is working with Coveralls
00:25:03 Reset to the previous commit, add coverage/ to .gitignore and remove accidentally committed files from coverage folder from the commit with git rm --cached
00:32:26 Revew, pull request, close issue
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #githubactions
See other related StatelessCode videos:
- NerdDice RubyGem: Add Coveralls to Gem and Github Actions youtu.be/pztMKLIBFJ8
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
Coveralls is a website that provides reporting and visibility into code test coverage for a project repository. While code coverage in and of itself doesn't speak to the quality or relevance of software tests, it does provide visibility into places where you may have accidentally neglected to cover your code. It's free for open-source projects and provides transparency into your code coverage metrics for those who are evaluating whether to use or incorporate your open source project.
In this video, we adapt a previous implementation of Coveralls from our NerdDice RubyGem to our Rails 7 project. Instead of following the official documentation on the Coveralls website, we instead use the simplecov-lcov and coveralls_reborn gems.
Gotchas: Be sure to add the coverage/ folder to your .gitignore file. In this video, we make the mistake of neglecting to do so and show you how to recover from it.
This video covers:
00:00:12 Introduction and review solution from NerdDice RubyGem
00:03:21 Visit Coveralls site and add nerd_dice_dot_com repo
00:04:39 Install the required gems
00:05:55 Add coverage status badge into README
00:08:36 Add SimpleCov configuration to TestHelper
00:10:33 Uncomment and adapt code in main.yml of Github Action
00:12:40 Review the local SimpleCov report in a browser
00:14:17 Initial push of the changes, check on build, review on Coveralls
00:17:31 Restore sample tests from previous video and ensure it is working with Coveralls
00:25:03 Reset to the previous commit, add coverage/ to .gitignore and remove accidentally committed files from coverage folder from the commit with git rm --cached
00:32:26 Revew, pull request, close issue
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #githubactions
See other related StatelessCode videos:
- NerdDice RubyGem: Add Coveralls to Gem and Github Actions youtu.be/pztMKLIBFJ8
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.








![Set up a Salesforce Development Environment on Ubuntu 24.04
In this video, we guide you through setting up a Salesforce development environment on a new install of Ubuntu 24.04. The only things we have installed so far are Visual Studio Code, bzip2 and tar. We have other recent videos linked where we install Node.js (via NVM), VS Code, and Git, so we breeze through those steps quickly in this video.We start by installing Node. Then we install the Java 17 OpenJDK (and save the directory from the installation output so we can set it in the VS Code settings later.) After that we install Git.For the Salesforce CLI, I always use the install via NPM option, irrespective of which operating system I use. I find it to be easier to maintain and upgrade. After the CLI is installed, we install the Salesforce Extension Pack (including the expanded version). After the extension pack is installed we can set the Salesforcedx-vscode-apex Java: Home value in VS Code settings.We authorize our DevHub (a TrailHead developer edition) and create a scratch org and make it our default org with `sf config set`.When we try the `sf org open` command, it fails. Salesforce CLI assumes that the temporary directory being used is the system temporary directory. Ubuntu 24.04 has Firefox installed using snap. Snap sandboxing places the temp directory in the users home directory instead. There are two ways to resolve this. You can execute `TMPDIR=$HOME/temp sf org open [your-flags]` every time you run the sf org open command. This is tedious. The other option is that you can install a browser via apt instead of snap. Unfortunately Chromium will not work for this because the apt install uses snap. To resolve it, we install Chrome and make it the default browser. Theres a privacy trade-off here. Make the decision thats best for you.After we have the ability to open our scratch org, we create a Hello World! Taxation is theft! Lightning Web Component with a simple Jest test. We run npm install on the SFDX project directory so that we can run our JavaScript tests and everything.Finally we deploy the component to our scratch org, create a Lightning page with a few different instances of it, and retrieve everything back to our project.This video covers: 00:00:00 Introduction 00:01:38 Install Node 20 (requires curl and NVM) 00:03:19 Install Java 17 OpenJDK and copy the Java Home directory from the output 00:05:21 Install Git and Salesforce CLI NPM package 00:07:57 Install Salesforce Extension Pack (including Expanded) and configure Salesforce Java Home setting in VS Code 00:11:47 Use Salesforce CLI to login to DevHub 00:14:12 Create a scratch org 00:18:20 Workaround issue to get `sf org open` to work, option 1 adding TMPDIR variable to beginning of command 00:21:45 Alternative workaround, install Chrome via apt and set as default browser 00:29:13 Create a Hello World! Taxation is theft! Lightning Web Component and ensure Jest test framework works 00:36:35 Deploy the component to the scratch org, add to a Lightning Page, and retrieve the whole project back 00:40:37 Conclusion and preview of other upcoming Salesforce material #setup #configuration #install #linux #ubuntu #debian #deb #terminal #ubuntu24 #lts #github #code #visualstudiocode #vscode #apt #git #node #nodejs #nvm #npm #java #jdk #openjdk #salesforce #sfdx #salesforcecli #workaround #scratchorg #helloworldtaxationistheft #jest #lightningwebcomponent #lwcSee other related StatelessCode videos:- Install Ubuntu 24.04 LTS Desktop https://youtu.be/yHxuNUovS20- Install Node.js (versions 18, 20, 22) with NVM on Ubuntu 24.04 https://youtu.be/YyEf1QWfg9Y- Install Visual Studio Code on Ubuntu 24.04 https://youtu.be/GdmHY1JhLI8- Install Git on Ubuntu 24.04 and Configure for Verified Commits in GitHub https://youtu.be/CagiEjuqKxU- Migrate from SFDX CLI version 7.x to Salesforce CLI version 2.x https://youtu.be/kyii2tPwcBI- Codecast: Install Salesforce DX on Ubuntu 20.04 (from 2021) https://youtu.be/JaVf4FYcYw0Resources that we relied upon for this solution:- Lightning Web Components Developer Guide: Develop with Salesforce DX Tools https://developer.salesforce.com/docs/platform/lwc/guide/get-started-sfdx.html- Salesforce CLI Setup Guide https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm- Node.js package manager instructions (you can choose your OS and preferred method) https://nodejs.org/en/download/package-manager - Salesforce CLI Command Reference https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_unified.htm- sf org open GitHub issue on forcedotcom/cli repo https://github.com/forcedotcom/cli/issues/2769- Command line workaround by setting TMPDIR variable https://github.com/salesforcecli/plugin-org/pull/992#issuecomment-2013234183
This video is CC0 - No rights reserved. All code is released under the UNLICENSE. Set up a Salesforce Development Environment on Ubuntu 24.04](https://i.ytimg.com/vi/OC4R71bQO4g/mqdefault.jpg)

