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.

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

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 ...

New dotnet-coverage tool collects code coverage for console and web applications, merges coverage reports, instruments binaries, and calculates code coverage for each test separately. Microsoft has ...

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 ...

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 ...

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 ...

Coverage has become a key technology in the pursuit of efficient and accurate verification of large designs. Obviously, simulation is still the cornerstone of verification, but the time when a single ...