Skip to content

Coverage report tooling #2

@dergoegge

Description

@dergoegge

To analyzing the effectiveness of testing scenarios, tooling should be implemented to create code coverage reports for:

  • Individual test cases
  • All test cases of a single scenario
  • All tests cases

Compiling the target for clang source code coverage and running each test case with the LocalRunner should suffice in collecting the coverage information. Removing the coverage information for the snapshot creation code (i.e. code run by Scenario::new) might be nice to get a better picture of what code is being fuzzed (#9).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions