Jira (PUP-4966) Collect code coverage information and export to code coverage

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-4966   Re: Collect code coverage information and export to code coverage The difficulty here is to find all the AST that was evaluated - there is a class called '' (a.k.a 'main') that is the concatenation of all topscopes. This concatenation is performed by a "code merger". It should be possible to navigate the merged code for the "main" class and drill down until finding Puppet::Pops::Model::Program instances (and subsequently the rest of the AST nodes inside of the Program). Once having found the "Program" object, there are methods that traverse every element inside the tree (eAllContents). As an example, the validator (checker4.0) does this. When collecting the result; it needs to be collected after each compilation, it should propagate the counts from the adapters, but not hold on to the adapters themselves as that would then cause all of the data from that compilation to be bound in memory. At the end of a compilation, it cannot yet reduce the count information since the result should perhaps be a report across multiple compilations. Thus, each compilation propagates information about files and counts (offset, length, count) to a "code coverag" object with a life cycle spanning over multiple compiles. Add Comment   This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.