Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

develop a job that runs descartes on a change #59

Open
3 tasks
bbaudry opened this issue May 3, 2018 · 3 comments
Open
3 tasks

develop a job that runs descartes on a change #59

bbaudry opened this issue May 3, 2018 · 3 comments

Comments

@bbaudry
Copy link
Contributor

bbaudry commented May 3, 2018

Create a task that

  • detects the nature of the change: change in the test suite or in the app code or in both.
  • identifies the part of the code that should be mutated
  • identifies the set of test cases that need to be executed
@nicolabertazzo
Copy link
Contributor

nicolabertazzo commented May 7, 2018

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

  1. In Jenkins, from the current build, get the list of change set (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
Copy link
Contributor Author

bbaudry commented May 8, 2018

in step 2. I suggest to consider 3 different situations

  • change in test classes
  • change in app code classes
  • change in both

@bbaudry
Copy link
Contributor Author

bbaudry commented May 8, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants