Bukama commented on PR #232: URL: https://github.com/apache/maven-scm/pull/232#issuecomment-2562251973
> That's not good and the JUnit project no longer recommends it. The problem is it doesn't indicate which line of code threw the exception so you can get false positives — tests that pass when they shouldn't — when the same exception class gets thrown from somewhere unexpected. The code line `assertNotNull(e.getMessage());` does not check for a specific line of code either. And I know that the way to test assertions in JUnit Jupiter is different. -- 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]
