Copilot commented on code in PR #240: URL: https://github.com/apache/maven-plugin-testing/pull/240#discussion_r2470976452
########## maven-plugin-testing-harness/src/site/markdown/index.md: ########## @@ -23,9 +23,28 @@ date: February 2008 The Maven Plugin Testing Harness provides mechanisms to manage tests on Mojos, i.e. by pre-constructing the [Plexus](http://plexus.codehaus.org) components, providing stub objects for Maven functionality such as projects, and populating fields from an XML file that resembles the plugin configuration in the POM. - The best way to start is to read the cookbook [How to use Maven Plugin Testing Harness](./getting-started/index.html). +### Migration to 3.4.0 + +Since version `3.4.0`, the Maven Plugin Testing Harness has been migrated to use JUnit 5 as the testing framework. +This change allows for more modern testing practices and improved integration with other tools. + +JUit 5 extension `MojoExtension` and annotation `@MojoTest` have similar functionalities Review Comment: Corrected spelling of 'JUit' to 'JUnit'. ```suggestion JUnit 5 extension `MojoExtension` and annotation `@MojoTest` have similar functionalities ``` ########## maven-plugin-testing-harness/src/site/markdown/index.md: ########## @@ -23,9 +23,28 @@ date: February 2008 The Maven Plugin Testing Harness provides mechanisms to manage tests on Mojos, i.e. by pre-constructing the [Plexus](http://plexus.codehaus.org) components, providing stub objects for Maven functionality such as projects, and populating fields from an XML file that resembles the plugin configuration in the POM. - The best way to start is to read the cookbook [How to use Maven Plugin Testing Harness](./getting-started/index.html). +### Migration to 3.4.0 + +Since version `3.4.0`, the Maven Plugin Testing Harness has been migrated to use JUnit 5 as the testing framework. +This change allows for more modern testing practices and improved integration with other tools. + +JUit 5 extension `MojoExtension` and annotation `@MojoTest` have similar functionalities +as in [Maven 4](https://maven.apache.org/ref/4-LATEST/maven-impl-modules/maven-testing/apidocs/index.html) +for easier migration of tests for Maven 4. + +Project still support Junit 3/4 `AbstractMojoTestCase` and Junit 4 `MojoRule` tests for backward compatibility Review Comment: Grammar error: 'support' should be 'supports' to agree with the singular subject 'Project'. ```suggestion Project still supports Junit 3/4 `AbstractMojoTestCase` and Junit 4 `MojoRule` tests for backward compatibility ``` ########## maven-plugin-testing-harness/src/site/markdown/index.md: ########## @@ -23,9 +23,28 @@ date: February 2008 The Maven Plugin Testing Harness provides mechanisms to manage tests on Mojos, i.e. by pre-constructing the [Plexus](http://plexus.codehaus.org) components, providing stub objects for Maven functionality such as projects, and populating fields from an XML file that resembles the plugin configuration in the POM. - The best way to start is to read the cookbook [How to use Maven Plugin Testing Harness](./getting-started/index.html). +### Migration to 3.4.0 + +Since version `3.4.0`, the Maven Plugin Testing Harness has been migrated to use JUnit 5 as the testing framework. +This change allows for more modern testing practices and improved integration with other tools. + +JUit 5 extension `MojoExtension` and annotation `@MojoTest` have similar functionalities +as in [Maven 4](https://maven.apache.org/ref/4-LATEST/maven-impl-modules/maven-testing/apidocs/index.html) +for easier migration of tests for Maven 4. + +Project still support Junit 3/4 `AbstractMojoTestCase` and Junit 4 `MojoRule` tests for backward compatibility Review Comment: Inconsistent capitalization of 'Junit' - should be 'JUnit' to match standard naming convention and usage elsewhere in the document. ```suggestion Project still support JUnit 3/4 `AbstractMojoTestCase` and JUnit 4 `MojoRule` tests for backward compatibility ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
