[
https://issues.apache.org/jira/browse/DAFFODIL-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Beckerle updated DAFFODIL-2815:
------------------------------------
Priority: Minor (was: Major)
> Implement Schema Coverage Test Tool in Daffodil
> -----------------------------------------------
>
> Key: DAFFODIL-2815
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2815
> Project: Daffodil
> Issue Type: New Feature
> Reporter: Olabusayo Kilo
> Priority: Minor
>
> It would be nice if there was a way for daffodil to report how much of a
> schema is represented by TDML tests.
>
> Possible Solutions:
> # for each TRD structure we'd keep a parse and unparse bit in a hash table.
> At the end of a parse/unparse cycle we could look at all those bits and see
> what is not touched.
> # I wonder if there are existing code coverage libraries or file formats we
> could use? I'm not sure how specific they are to actual programming languages
> or if it's just like "line X in file Y was hit" kind of thing--information
> that we already have in the InfosetInputter/Outputters and TRDs. It would be
> nice if we don't need to reinvent the wheel, especially if we could take
> advantage of tools that can make visual representations and code coverage
> analysis.
> I also wonder if maybe there's an approach similar to java debugging and how
> I _think_ code coverage works in Java, where we just enable a "java agent"?
> This could modify byte code (e.g. of an InfosetInputter/Outputter) to call
> functions at the appropriate time to create the code coverage reports without
> ever having to modify Daffodil itself--sort of a pluggable code coverage
> thing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)