Community
Participate
Working Groups
In order to facilitate the build and limit the number of dependencies, I am currently moving the tests inside the plugins (ex: core plugin) into separate hosted fragments. I used fragments, so the developer still has access to the code inside the host plugin, it will be still possible to test internal packages and private methods. Papyrus will not depend on JUnit plugins anymore, this will remove also the source folder named "test".
-1 I do not agree with that. I am not sure that it is a best programming practice. Having the tests in a separate plugins will not inforce programmer to update the tests or simply to execute them. If they are in separate plugins, programmer will not take them, and not use them anymore. The tests should be in the same plugins. The build process should simply not compile the tests folder, and thus do not need to depend on JUnit.
(In reply to comment #1) > -1 > > I do not agree with that. I am not sure that it is a best programming practice. > > Having the tests in a separate plugins will not inforce programmer to update > the tests or simply to execute them. > If they are in separate plugins, programmer will not take them, and not use > them anymore. > The tests should be in the same plugins. > > The build process should simply not compile the tests folder, and thus do not > need to depend on JUnit. This is the first step to have a separate feature for tests in Papyrus, and those tests will be run on the hudson server each time Papyrus is build, so the tests will be run each night for the nightly build, for example. It will be even better than the actual case, where launching the tests depends on the good will of the developers. Testing and content of the plugins are 2 separate concerns in order of distribution, there is no reason to put them in the same area. Moreover, what happens on the build server is the same as what happens in your workspace. If I remove test folder from the compiled area of the plugin, this will remove the refactoring abilities of the jdt tool. That means that the test won't be updated more than if you put them in a separate fragment. The solution of adding locally to the build will provoke some bad commits, where people will forget not to commit the build.properties modified file.
This has been fixed; I close the task
