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

Use of the mutation in continuous integration tools (Jenkins) by calling the mutation directly #7

Open
timijntema opened this issue Jun 6, 2019 · 0 comments

Comments

@timijntema
Copy link

This is not really a bug, more a question. I was wondering if it is possible to call the python mutation code directly. This way it could be integrated with build tools by calling the mutation code and running ctest in the pipeline stages. If that is done, the results could be put into a file/artifact, just like it would be with JUnit output. In order to get a report about the results, it would be nice to have a Jenkins plugin that creates a table, showing the results.

This is just an idea that could be used to improve this tool. Maybe a python run-manually file could be created that takes a folder with multiple source files, which then grabs a random file and performs the mutation, runs a make tool and runs the tests. If this is done an N number of times, the mutation testing could be run automatically.

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

No branches or pull requests

1 participant