[ 
https://issues.apache.org/jira/browse/MNG-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701744#comment-16701744
 ] 

ASF GitHub Bot commented on MNG-6527:
-------------------------------------

diffblue-assistant opened a new pull request #196: [MNG-6527] - Add unit tests 
for org.apache.maven.repository.MavenArtifactMetadata
URL: https://github.com/apache/maven/pull/196
 
 
   Hi,
   
   I've analysed your codebase and produced some unit tests for the following 
classes - org.apache.maven.repository.MavenArtifactMetadata.
   
   I've written the tests for these functions with the help of 
[Diffblue](https://www.diffblue.com/) 
[Cover](https://www.diffblue.com/datasheet).
   
   Hopefully, these tests should help you detect regressions caused by future 
code changes.
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed 
          for the change (usually before you start working on it).  Trivial 
changes like typos do not 
          require a JIRA issue.  Your pull request should address just this 
issue, without 
          pulling in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line 
and body.
    - [x] Format the pull request title like `[MNG-XXX] - Fixes bug in 
ApproximateQuantiles`,
          where you replace `MNG-XXX` with the appropriate JIRA issue. Best 
practice
          is to use the JIRA issue title in the pull request title and in the 
first line of the 
          commit message.
    - [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
          be performed on your pull request automatically.
    - [x] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add unit tests for org.apache.maven.repository.MavenArtifactMetadata
> --------------------------------------------------------------------
>
>                 Key: MNG-6527
>                 URL: https://issues.apache.org/jira/browse/MNG-6527
>             Project: Maven
>          Issue Type: Test
>            Reporter: Louis Mills
>            Priority: Major
>              Labels: pull-request-available
>
> These tests were written by Diffblue Cover.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to