Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2010-12-31Convert all JGit unit tests to JUnit 4Robin Rosenberg1-1/+1
Eclipse has some problem re-running single JUnit tests if the tests are in Junit 3 format, but the JUnit 4 launcher is used. This was quite unnecessary and the move was not completed. We still have no JUnit4 test. This completes the extermination of JUnit3. Most of the work was global searce/replace using regular expression, followed by numerous invocarions of quick-fix and organize imports and verification that we had the same number of tests before and after. - Annotations were introduced. - All references to JUnit3 classes removed - Half-good replacement for getting the test name. This was needed to make the TestRngs work. The initialization of TestRngs was also made lazily since we can not longer find out the test name in runtime in the @Before methods. - Renamed test classes to end with Test, with the exception of TestTranslateBundle, which fails from Maven - Moved JGitTestUtil to the junit support bundle Change-Id: Iddcd3da6ca927a7be773a9c63ebf8bb2147e2d13 Signed-off-by: Robin Rosenberg <> Signed-off-by: Shawn O. Pearce <>
2010-02-10http.test: Use JUnit 3 test runnerShawn O. Pearce1-1/+1
JGit relies on JUnit 3, not JUnit 4. Change-Id: Ic5a0ae1564d7744c203321857fc603e7008dbf13 Signed-off-by: Shawn O. Pearce <>
2010-01-23Make HTTP test project work in EclipseRobin Rosenberg1-0/+15
The Jetty components are not available as part of Eclipse, but a P2 packaged version can be found via [1] for Eclipse 3.5 and newer. [1] Change-Id: Ibd5930bb9fc9589125876ca50c52e58bd31b051c Signed-off-by: Robin Rosenberg <> Signed-off-by: Shawn O. Pearce <>

    Back to the top