Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Talk Proposal] Enough Coverage To Beat The Band #82

Open
kevin-j-m opened this issue Sep 28, 2021 · 0 comments
Open

[Talk Proposal] Enough Coverage To Beat The Band #82

kevin-j-m opened this issue Sep 28, 2021 · 0 comments
Labels

Comments

@kevin-j-m
Copy link

kevin-j-m commented Sep 28, 2021

Abstract

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.

Detail

https://kevinjmurphy.com/posts/coverage/ | https://youtu.be/EyLO0EEm3BQ

We'll discuss in detail each of the coverage modes that ruby provides, which answer the following questions:

  • Lines - how many times was each line executed?
  • Oneshot Lines - which lines were executed?
  • Methods - how many times was each method executed?
  • Branches - how many times was each conditional executed?

Bio

Kevin lives near Boston, where he is a Software Developer. He’s doing the best he can to cope with 2 years of concerts that could have been.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants