Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12969

Generate and report on per-test code coverage

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.3.0, 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: Tools
    • Storage Engines
    • 3
    • 2024-05-28 - FOLLOW ON SPRINT, 2024-06-11 - Dinosaurs go rawr, 2024-06-25 - Climbing BTrees

      This ticket (and branch) are a place to capture my May 2024 Skunkworks project.

      We currently have code coverage data for WT, generated by running a collection of tests, and achieving just over 50% code coverage. It would be very useful if it were possible to answer the questions such as the following very quickly/easily:

      • I’m modifying function X, and/or these lines of code: which existing tests cover this? This would help make a developer’s life easier.
      • Does a test (or set of tests) add code coverage compared to the rest of the set of tests? And if so, what? This would support optimising our testing.

      I think that gathering the data should not be too hard (and builds on the work to parallelise code coverage) - the real challenge is how to report it to users in an easy to understand/use way (this will involve building our own versions of the code coverage HTML reports).

      Note: the coverage data would have limitations due to some of our current code coverage tests being non-deterministic.

            Assignee:
            jeremy.thorp@mongodb.com Jeremy Thorp
            Reporter:
            jeremy.thorp@mongodb.com Jeremy Thorp
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: