代码拉取完成，页面将自动刷新
#Code Coverage (Like a Boss)
##Abstract
Code Coverage tools can prove to be invaluable resources in software projects large and small. But just like putting a hammer in your toolbox won't build you a safer house, Code Coverage tools will do little for you on their own, without a process to follow.
In this talk, you'll learn:
Confused about the difference between line coverage, statement coverage, function coverage, and branch coverage? How about pre-instrumented source vs. on-the-fly instrumentation? What the heck are Istanbul and Blanket? Here's a crash course in Code Coverage tools & methodology, and a summary of the current lay of the land in the JavaScript world.
Code Coverage is meaningless if it's not enforced. But nobody likes being the one who chronically nags their teammates. By automating the process of enforcing a minimum coverage threshold, this responsibility is passed on to a robot. We'll look into using Grunt to handle this task, and how you can configure a solution that runs on popular CI frameworks like TravisCI and Jenkins. Over time, this process can change the culture of teams to a "test-first" mindset.
Now that you love Code Coverage, find out how your tool's statistics are lying to you. It's easy to get a false sense of security based on coverage percentages. Whether intentional or not, there are many ways that developers can manipulate the system to produce misleading coverage statistics. Luckily, there are a few simple strategies that can mitigate this issue, and keep your numbers honest.
How much coverage is "good enough"? 50%? 75%? 90%? Just as a Zen master lives in a constant pursuit of enlightenment, so must we never cease to pursue better code coverage. But is it really about the numbers? Learn why chasing a high coverage percentage is a bad strategy, and how to explain that to your number-oriented boss.
Code Coverage serves as a great "fail safe" for catching untested or under-tested code. But it does nothing to ensure that the tests we write are actually meaningful. To accomplish this, we need actual human brains, eyeballs, and conversations. Learn how to implement a "Feature Coverage" process as an essential companion to Code Coverage, and how this will instill harmony in your team between Product Managers, QA, and developers.
##Speaker Bio
Dave works from the mountains of Colorado as the lead UI Architect for Model N, Inc. He describes solving complex coding problems as "pulling splinters out of his brain," insisting that it "feels better than it sounds." When not coding, he enjoys playing the drums, running, biking, and snowshoeing.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
马建仓 AI 助手
