Code coverage is one of the most widely used quality metrics in embedded software development. Nearly every team I start working with tells me they aim to reach 80%+ code coverage. In fact, many ...

When a vendor claims its tool has 100% test coverage, that assertion can mean different things to different people. Some think 100% coverage means complete testing -- but, sadly, that's impossible.

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

When developers and engineers measure code coverage in embedded systems they can improve their device’s safety and performance. Embedded systems play a foundational ...

Software development teams are under a lot of pressure these days to ship code faster— secure, reliable code. Admittedly, "fast but good" is an age-old challenge for devs of nearly every stripe, but ...

There is a difference in semantics between code coverage generated from a simulator engine and code coverage generated from a formal engine. This paper seeks to raise the awareness of verification ...

Regardless of the software methodology a development team uses, unit testing is a way to ensure a baseline level of quality with every build. Some development teams discuss a unit testing strategy in ...

Every design verification technique requires coverage metrics to gauge progress, assess effectiveness, and help determine when the design is robust enough for tapeout. At every step of the way and ...

Whilethis approach may seem heavy-handed, it can be acceptable because theamount of critical code requiring MC/DC level testing is oftenrelatively small. A lack of complete test coverage almost always ...