STAMP-project / pitmp-maven-plugin

Maven plugin to handle multi module projects for PiTest
GNU Lesser General Public License v3.0
46 stars 14 forks source link

Selection pattern for source classes and test classes #31

Open nrainer opened 6 years ago

nrainer commented 6 years ago

I am wondering if there is a reason why PmpContext#getClassesInternal creates patterns for packages. Is this optimization needed? Patterns using the full path to the Java files might be more precise for projects in which the package does not start with the name of the project (so that packages with the same name can exist in multiple projects).

nrainer commented 6 years ago

If there is no reason against it, I think this is sensible and can reduce unnecessary analysis efforts. For example, in the project Achilles, integration tests of different modules reside in the same package so that they would be executed in each integration test module, causing a large overhead. (https://github.com/doanduyhai/Achilles)

nrainer commented 6 years ago

I created a pull request: https://github.com/STAMP-project/pitmp-maven-plugin/pull/32

Cael35 commented 6 years ago

Because it is what PIT does.