svn commit: r1882223 - in /maven/website/content: guides/development/guide-maven-development.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Sat Oct  3 18:41:39 2020
New Revision: 1882223

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/development/guide-maven-development.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/development/guide-maven-development.html
==============================================================================
--- maven/website/content/guides/development/guide-maven-development.html (original)
+++ maven/website/content/guides/development/guide-maven-development.html Sat Oct  3 18:41:39 2020
@@ -149,6 +149,7 @@ Maarten Mulders" />
 <p>See <a href="/scm.html">https://maven.apache.org/scm.html</a> for information. The Maven project uses the Apache GitBox Repositories, and all of them are dual-mirrored to <a class="externalLink" href="https://github.com/apache/"> GitHub</a>.</p></section><section>
 <h3><a name="Don.27t_forget_tests.21"></a>Don't forget tests!</h3>
 <p>You will find many unit tests. If at all possible, create or modify a unit test to demonstrate the problem, and then validate your fix.</p>
+<p>If you need to mock a class to write a test, use the Mockito framework. Parts of the Maven codebase predate Mockito so you will encounter existing tests that use EasyMock, PowerMock, and JMock. However, all newly written mocks should use Mockito, even if this means a module or a single class uses multiple mocking frameworks. If an existing test class has complicated legacy mock setup, you can add new Mockito based tests in a new test class. There is no requirement that all tests for a single model class must be in the same test class. It is OK to have multiple test classes per model class.</p>
 <p>If the problem case can't be set up in the unit tests, add an integration test. Before submitting a patch, in any case, you should run all of the integration tests. The tests require an empty local repository. See <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more details.</p></section><section>
 <h3><a name="Creating_and_submitting_a_patch">Creating and submitting a patch</a></h3>
 <p>The most convenient way is to create a GitHub fork from the Git repository you are working with. When you have either completed an issue or just want some feedback on the work you have done, create a pull request. We have a couple of guidelines when submitting contributions:</p>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.