Set default Clover coverage project name#6210
Set default Clover coverage project name#6210Staubiii wants to merge 1 commit intosebastianbergmann:mainfrom
Conversation
Some Clover XML report processing tools require the project name to be set. e.g. https://issues.jenkins.io/browse/JENKINS-75648
|
Thank you for your contribution. I am open to the change you propose. However, if I look at https://bitbucket.org/atlassian/clover/raw/master/etc/schema/clover.xsd and understand ... <xs:element name="project">
<xs:annotation>
<xs:documentation>
Project metrics relating to non-test source.
@name - project name (optional)
@timestamp - seconds since UTC
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="metrics" type="projectMetrics"/>
<xs:element maxOccurs="unbounded" ref="package"/>
</xs:sequence>
<xs:attribute name="name"/>
<xs:attribute name="timestamp" use="required" type="xs:integer"/>
</xs:complexType>
</xs:element>... correctly then the |
|
I totally missed in my first comment that the Clover XML writer in fact does generate the |
|
I am open to accepting the change you propose. I am reluctant to change PHPUnit 8.5, PHPUnit 9.6, and PHPUnit 10.5 as these versions have reached the end of their bugfix support. The proposed change should go into It would help me if somebody could look into whether https://bitbucket.org/atlassian/clover/raw/master/etc/schema/clover.xsd is, in fact, the official/canonical schema for Clover XML and, if it is, look into whether there are any other changes PHPUnit (or phpunit/php-code-coverage, rather) needs to implement to comply with the schema. |
|
I cherry-picked this into |
Some Clover XML report processing tools require the project name to be set.
e.g. https://issues.jenkins.io/browse/JENKINS-75648
Could this be backported to phpunit 8.5?