[JENKINS-60940] - Migration of GitAPITests from JUnit 3 to JUnit 4

[GAyan17]

JENKINS-60940 - Migration of GitAPITests from JUnit 3 to JUnit 4

Added Class GitAPITest, for migration of GitAPITestCase from JUnit 3 to JUnit 4, added the first test getRemoteUrl

Checklist

• I have read the CONTRIBUTING doc
• I have referenced the Jira issue related to my changes in one or more commit messages
• I have added tests that verify my changes
• Unit tests pass locally with my changes
• I have added documentation as necessary
• No Javadoc warnings were introduced with my changes
• No spotbugs warnings were introduced with my changes
• I have interactively tested my changes

Types of changes

What types of changes does your code introduce?

• Infrastructure change (non-breaking change which updates dependencies or improves infrastructure)

[MarkEWaite]

This looks very good. I'd like the pull request to include the removal of the test from GitAPITestCase so that it is clear in the single pull request that the test is moving from one location to another

[GAyan17]

@MarkEWaite Sure, I will do that. And should I update more tests in this PR, or should I make another if in case you wish to merge this?

[MarkEWaite]

Looks good. Thanks for doing it.

Once we have the base file included (was GitClientTest in the examples I created, is now GitAPITest in what you've created), then I prefer more small pull requests rather than fewer, larger pull requests.

[GAyan17]

Thanks @MarkEWaite,
Small PR approach seems reasonable, it would help to avoid any big errors or failures, and tracking will be easy. I would follow that, as of now I have migrated smaller tests as suggested. Should I commit them for review?

[MarkEWaite]

Thanks @MarkEWaite,
Small PR approach seems reasonable, it would help to avoid any big errors or failures, and tracking will be easy. I would follow that, as of now I have migrated smaller tests as suggested. Should I commit them for review?

Yes, that would be great. I've merged this change so that you have the base class available for subsequent pull requests.