Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Code Coverage Content on InfoQ

  • Rust 1.60 Released with LLVM-Native Code Coverage Along with Rust 2024 Roadmap

    Rust 1.60 stabilizes source-based code coverage using LLVM native instrumentation, re-enables incremental compilation by default, and enforces Instant monotonicity guarantees. Additionally, the Rust team has formalized its roadmap for Rust evolution until 2024.

  • Strategy for Mobile and Web Test Coverage

    Teams need to match testing with the market usage patterns across geographies of their apps as consumers are expecting smooth apps functionality across all digital channels. Here's a methodology and index for considering device/OS combinations together with other characteristics like aging, screen parameters and other testing related guidelines for data driven test coverage of the mobile market.

  • Updates to Google Chrome DevTools

    The upcoming version of Chrome DevTools has a number of new features that can help developers build faster web pages and have an easier time debugging complex asynchronous code. At Google I/O 2017, Paul Irish presented a State of the Union showcasing a number of these new features.

  • Measure and Improve Code Quality

    InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.

  • Java Community Release First OpenJDK Coverage Numbers

    The AdoptOpenJDK has released the first code coverage percentages for the OpenJDK codebase.

  • Testing Machine to Machine Systems

    Devices are becoming increasingly interconnected through the internet where they are communicating directly with each other. Testing such machine to machine (M2M) systems can be difficult due to their complexity and the usage of different platforms, as Peter Varhol explained in his talk about testing in the M2M world at the QA&Test 2014 conference.

  • NDepend 5 Can Chart Code Trends

    Patrick Smacchia has recently announced NDepend 5.0, the latest version of his .NET code analyzer coming with a number of enhancements: support for VS 2013, trend monitoring, new dashboard and a major UI facelift.

  • Agile and the Crutches of False Confidence

    False confidence is often grounded in wishful thinking. It is defined as a state where the projected reality and the actual reality might differ considerably, however for a limited period of time, it does give a feeling of having everything under control. There are many such situations in Agile development which make a team hold onto the false confidence crutch only to fall later.

  • Adobe Releases ActionScript Code Coverage Plug-in for Flash Builder

    Adobe has made available a prerelease of an ActionScript Code Coverage Plug-in for Flash Builder, which aims to help developers understand exactly what code is executed while an application is running. When added to Flash Builder, the plug-in provides a new Eclipse perspective that allows you to start the code coverage tool.

  • NDepend 3.0 Is Integrated with Visual Studio

    NDepend 3.0 comes integrated with Visual Studio analyzing code in real time, can analyze code over multiple VS solutions, supports editing of multiple CQL rules at one time, and comes with enhanced search and performance.

  • Faster Test Runs With Clover's Test Optimization

    The recent release of Clover 2.4 highlights a new "Test Optimization" feature that offers to speed up CI builds and allow developers to spend less time waiting for their tests to run. The feature leverages "per-test" coverage data to selectively run only the tests impacted by your code changes.

  • Careful With Your Coverage Metrics

    Christian Gruber takes some time to clarify the TDD stance on using code coverage metrics. He discusses what code coverage metrics do and don't tell you, how TDD fits into the picture, and how one might be best advised to use their code coverage metrics.

  • Coverity Readiness Manager Brings Quick Visibility to Code Characteristics

    Coverity recently released Readiness Manager for Java providing a dashboard and analysis for code complexity, violation of best practices, architectural integrity, interdependencies, and test coverage.

  • Getting Up-to-Speed on NDepend and Code Metrics

    Any tool is only good if it is in the hands of a developer who knows how to use it. NDepend is one of those tools which is very powerful but addresses an aspect of software development too few architects or developers understand, software metrics.

  • Cyclomatic Complexity Revisited

    Enerjy studied tens of thousands of source code files and found the optimum Cyclomatic Complexity number is 11, with a 28% defect probability. In fact, you are more likely to encounter a defect if you have lower complexity - is it time to make your methods are more complicated?