Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60940

Convert git client plugin tests from JUnit 3 to JUnit 4

    • 3.13.0

      The git client plugin tests have started their transition process to retire the JUnit 3 based GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest. They should be replaced by the parameterized GitClientTest.

      For each test in GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest:

      • If it is already tested in GitClientTest, delete the test from the JUnit 3 based tests
      • If it is not already tested in GitClientTest, write a test in GitClientTest or in a new test class and delete the test from the JUnit 3 based tests

      This issue could be worked by multiple people concurrently, so long as they coordinate with one another on the specific tests they are converting.

          [JENKINS-60940] Convert git client plugin tests from JUnit 3 to JUnit 4

          Mark Waite created issue -
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          Mark Waite made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Mark Waite made changes -
          Description Original: The git client plugin tests have started their transition process to retire the JUnit 3 based GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest. They should be replaced by the parameterized GitClientTest.

          For each test in GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest:
          * If it is already tested in GitClientTest, delete the test from the JUnit 3 based tests
          * If it is not already tested in GitClientTest, write a test in GitClientTest and delete the test from the JUnit 3 based tests

          This issue could be worked by multiple people concurrently, so long as they coordinate with one another on the specific tests they are converting.
          New: The git client plugin tests have started their transition process to retire the JUnit 3 based GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest. They should be replaced by the parameterized GitClientTest.

          For each test in GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest:
          * If it is already tested in GitClientTest, delete the test from the JUnit 3 based tests
          * If it is not already tested in GitClientTest, write a test in GitClientTest or in a new test class and delete the test from the JUnit 3 based tests

          This issue could be worked by multiple people concurrently, so long as they coordinate with one another on the specific tests they are converting.
          Mark Waite made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Mark Waite made changes -
          Labels Original: newbie-friendly New: hacktoberfest newbie-friendly
          Daud Kakumirizi made changes -
          Assignee New: Daud Kakumirizi [ kdaud ]
          Mark Waite made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          Mark Waite made changes -
          Assignee Original: Daud Kakumirizi [ kdaud ] New: Hrushi20 [ hrushi20 ]
          Mark Waite made changes -
          Released As New: 3.13.0
          Status Original: Fixed but Unreleased [ 10203 ] New: Closed [ 6 ]

            hrushi20 Hrushi20
            markewaite Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: