juherr commented on PR #3179: URL: https://github.com/apache/maven-surefire/pull/3179#issuecomment-3816338329
TestNG contributor here – and apologies if this isn't the right place to discuss this. I believe this move could be positive for the Java community. While JUnit versions prior to 5 and TestNG are largely in maintenance mode today, the JUnit 5 platform has clearly become the most mature and actively maintained solution for testing in the Java ecosystem. From that perspective, moving the abstraction level from Maven to JUnit itself does make sense. That said, I think @Tibor17 's concerns and experience are important. For a change of this importance, a more incremental approach may be worth considering if there is a risk of breaking existing setups. Based on my understanding, the testng-engine does not yet cover all TestNG features and still sees relatively limited adoption, which may increase the migration risk. For example, would it be possible to keep the JUnit 5 provider enabled by default while disabling legacy providers, but still allow running both side by side during a transition phase? -- 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]
