The code base is composed of multiple modules. To be clear, domi was referring to the test module (which is a peer of the core module you’ve been working in), not the test directory of the core module. Strictly speaking, tests that use the test harness are not unit tests, since the test harness sets up a running instance for you.
-- Dean On 2/17/12 1:53 PM , "Thorsten Möllers" <[email protected]> wrote: I did look at test/java/hudson/matrix, but the files there seem to be only unit tests. The modifications I did are not feasible for unit test, I think. But there seem to be some test jobs in /test/target. I will take a deeper look there later. Thanks, Thorsten On 17/02/12 17:01, domi wrote: did you have a look at the 'jenkins-test-harness'? its part of the core: https://github.com/jenkinsci/jenkins/tree/master/test /Domi On 17.02.2012, at 13:56, Thorsten Möllers wrote: Hi all, I'm new here, just started to develop my first Jenkins contributions this week. I implemented two features, because I need them badly. https://issues.jenkins-ci.org/browse/JENKINS-4960 (only one checkout per matrixa build, actually I only updated an existing patch) => https://github.com/jenkinsci/jenkins/pull/375 <https://github.com/jenkinsci/jenkins/pull/375/commits> https://issues.jenkins-ci.org/browse/JENKINS-12778 (multiple touchstones, this was my idea) => https://github.com/jenkinsci/jenkins/pull/377 Now, besides asking kindly for some feedback on these pull requests, I would also like to mention an issue that occurred to me when I was implementing JENKINS-12778: I had a hard time finding some good unit tests for my implementation (so I didn't implement any), but it was simple to create some job configurations to test the new functionality. Is there any framework available where I should add these configurations, so that they are executed as part of a test suite? Best regards, Thorsten Möllers
