Typical test coverage includes functional, statement, branch, and conditional coverage. The idea is to match what percentage of code can be exercised by a test suite of one or more coverage criteria. Coverage tests are usually defined by rule or requirements.
Software delivery teams can utilize machine data to understand the line count, code density, and technical debt.
When your Splunk deployment is ingesting test coverage tool data, you can use it to accomplish application delivery and DevOps use cases.
Guidance for onboarding data can be found in the Spunk Documentation, Getting Data In (Splunk Enterprise) or Getting Data In (Splunk Cloud). In addition, these Splunk Add-Ons and Apps are helpful for working with test coverage tool data.
Looking for more information on data types? Download the Splunk Essential Guide to Machine Data