Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
The lights cut out. The crowd roars. It’s time. The band takes the stage. They’ve practiced the songs, particularly the covers. They’ve sound checked the coverage of the speakers. They know the lighting rig has the proper colored gels covering the lamps. They’re nervous, but they’ve got it all covered. Similarly, code coverage can give you confidence before your app performs on production and also tell you how live code is used (or not used). We’ll cover how to leverage ruby’s different coverage measurement techniques in concert to assist your crew and delight your audience. Kevin Murphy Kevin lives near Boston, where he is a Software Developer at The Gnar Company. He’s doing the best he can to cope with a year of concerts that could have been.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled "Enough Coverage To Beat The Band" presented at RubyConf 2020 by software developer Kevin Murphy, the concept of code coverage in software development is vividly illustrated using a concert metaphor. Kevin draws parallels between preparing for live music performances and the importance of code coverage in software applications, emphasizing how proper coverage can boost confidence in deployment and ensure code quality. Key Points Discussed: - **Introduction to Coverage**: Kevin introduces himself and sets the stage by describing the excitement of a concert as an analogy for the coding process. He explains the need for thorough preparation in both scenarios and how coverage serves as a crucial tool for developers. - **Types of Coverage**: - **Lines Coverage**: Demonstrates how to track the execution of each line of code. He uses an example of a band's practice set, where the execution of certain lines (or strings broken) is counted during performances. - **One-Shot Coverage**: Focuses on specific instances, such as optimizing equipment usage for a particular show, illustrating how this mode aids developers in identifying unutilized parts of their code. - **Methods Coverage**: Highlights tracking how often specific methods are executed rather than individual lines. This is exemplified through the lighting team managing numerous stage lights to determine which were actively used. - **Branches Coverage**: Discusses the exploration of conditionals in the code, comparing it to transitioning between songs in a setlist, highlighting potential bugs like an off-by-one error that could affect performance. - **Practical Applications**: Each coverage type offers insights that allow developers to refine their code, minimize dead code, and streamline performance, akin to a band's preparation for diverse concert settings. - **Conclusion and Recommendations**: Kevin summarizes the benefits of utilizing Ruby's coverage tools, suggesting gems like 'simplecov' and 'coverband' for assessing test and production code coverage respectively. He encourages audience members to utilize these tools to enhance their coding practices. - **Engagement**: Kevin invites attendees to participate in a live Q&A in the associated Slack channel for further discussion on coverage and share personal concert experiences. The video serves as both an educational session on Ruby's coverage module and a creative reminder of the parallels between the meticulous preparation of a concert and software development, emphasizing the importance of such practices in ensuring high-quality code delivery.
Suggest modifications
Cancel
