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

Tips on running across a project? #57

Open
leason opened this issue Mar 11, 2020 · 0 comments
Open

Tips on running across a project? #57

leason opened this issue Mar 11, 2020 · 0 comments

Comments

@leason
Copy link

leason commented Mar 11, 2020

I'm new to mutation testing and I'm trying to apply this to a real project. The project has lots of unit test files testing lots of modules. Are there patterns or approaches for applying MutPy to a larger project like this? One thought I had was to write a script that would read in from a CSV with a set of Target and Unit Tests listed out. The script could create a new report directory for each run, but that seems like it would be tedious to comb through.

Any tricks on running a bunch of these and generating a higher level report?

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