mirror of
https://github.com/SAP/jenkins-library.git
synced 2024-12-14 11:03:09 +02:00
dc9ce9a732
there is only one test class making use of it left. This test class is the GitUtilsTest itself. Hence moving this member downwards in the test class hierarchy into GitUtilsTest. I doubt it makes sense to make use of a generic git utils mock somewhere else since this basically means to test the GitUtils class in the conxtext of other examinees. For that there is no need. The GitUtils class should be tested by the corresponding test class, but not in a transive manner by other tests. For all other tests a specific git utils mock should be provided mocking the corresponding method class. This is already the case today, otherwise we would have more test classes making use of the generic git utils mock. |
||
|---|---|---|
| .. | ||
| cm | ||
| k8s | ||
| mta | ||
| tools | ||
| versioning | ||
| ConfigurationHelperTest.groovy | ||
| ConfigurationLoaderTest.groovy | ||
| ConfigurationMergerTest.groovy | ||
| EnvironmentUtilsTest.groovy | ||
| FileUtilsTest.groovy | ||
| GitUtilsTest.groovy | ||
| MapUtilsTest.groovy | ||
| MtaUtilsTest.groovy | ||
| UtilsTest.groovy | ||
| VersionTest.groovy | ||
| VersionUtilsTest.groovy | ||