STAMP-project / pitest-descartes

Descartes supports developers to improve their test suites by reporting weak spots in covered code
https://hal.archives-ouvertes.fr/hal-01870976/document
GNU Lesser General Public License v3.0
126 stars 21 forks source link

develop a job that runs descartes on a change #59

Open bbaudry opened 6 years ago

bbaudry commented 6 years ago

Create a task that

nicolabertazzo commented 6 years ago

My proposal to this task (for jenkins pipeline projects ) is:

  1. In Jenkins, from the current build, get the list of [change set](http://hudson-ci.org/javadoc/hudson/model/AbstractBuild.html#getChangeSet()) (the files changed from the previous build)
  2. from the change set get the list of the test file changed (the files stored in a specified folder)
  3. Execute the mutaion only to the test classes that are changed

We can develop and distribute this feature as a Jenkins Shared libraries that for each build return the list of test changed in the change set. This list can be used as targetClasses pit parameter.

To develop this feature we can use these Jenkins functionalities:

bbaudry commented 6 years ago

in step 2. I suggest to consider 3 different situations

bbaudry commented 6 years ago

Do you think that this task can be developed independently of Jenkins? This way we could reuse it in a scenario based on pull-requests