Refactored import statements to use org.junit.Assert #1167
Refactored import statements to use org.junit.Assert #1167tfr42 wants to merge 6 commits intodeegree:mainfrom
Conversation
…cated methods in junit.framework.Assert. Upgrades to junit 4.13.2
|
Introduce constants for different units and measures. |
|
From a programmer's point of view it would be nice to use general available constant for most cases and only a local constant if required. |
|
Thank you for your contribution. Unfortunately, this PR has been inactive for 90 days (see PR stuck workflow). Of course this is not the final word. The PR can become unstuck, for example, by reengaging in the discussion, answering open questions, rebasing, or adding new commits to this PR. |
|
Thank you for your contribution. Unfortunately, this PR got stuck (see PR stuck workflow). Of course this is not the final word. If you think that we did wrong, then reopening this pull request, continuing the conversation, and/or finishing any outstanding tasks will help to restart the decision-making process. Perhaps we can then, with additional information, merge the pull request. Anyhow, we do appreciate your commitment to open source and to deegree in particular. |
This PR contains minor improvements of the usage of JUnit API.
0.01d, see https://junit.org/junit4/javadoc/4.13/org/junit/Assert.html#assertArrayEquals(double[],%20double[],%20double)