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

Clarify that --mutantDir must exist if specified #22

Open
sambacha opened this issue Jul 16, 2023 · 4 comments
Open

Clarify that --mutantDir must exist if specified #22

sambacha opened this issue Jul 16, 2023 · 4 comments
Assignees

Comments

@sambacha
Copy link

mutator will crash if a valid mutation is found and --mutantDir has a value for a nonexistent directory.

Clarifying that may help in the CLI. I Would be happy to submit some clarifications to the --help output.

Thanks for the tooling, it is much appreciated!

@agroce
Copy link
Owner

agroce commented Jul 17, 2023

@sambacha -- would it better to just have it create the directory? That seems equally easy, and unless people are somehow relying on the current behavior, more user friendly. I've thought about doing that minor change many times, but never got around to it (professors alas aren't ideal lead maintainers)... Let me know your pref/agreement and I'll fix shortly.

@agroce agroce self-assigned this Jul 17, 2023
@agroce
Copy link
Owner

agroce commented Jul 19, 2023

@sambacha -- and improvements to help/doc would be highly appreciated!

@sambacha
Copy link
Author

@sambacha -- and improvements to help/doc would be highly appreciated!

Placebo mutation case

Will do, we are formulating some ideas actually that go beyond this, namely we would like to first do a preflight check so to speak to know if there are any configuration issues. if This would be like a 'placebo mutation' that is to say an artificial mutation that is valid that can be used to increase confidence in the setup and configuration of the mutation process (i.e. a smoke test) for our engineers. Would you have any recommendations as to this?

Also for generating mutations:

Solidity Mutation

Flatten vs Normal contracts, we have noticed different results in the mutation output.

Targeting specific mutation subtypes, e.g. Inheritance hierarchies.

  • Import order and change of import syntax (i.e. going from named to naked).

Gas profiling with Mutation Cases

We are trying to utilize gas snapshot results to inform the generation process. So far tying the lineo of the mutation and the gas snapshot delta is not very ergonomic.

Tracking Mutation

We are saving process runtime for the time it takes to generate mutation cases of:

  • no valid,
  • at least one valid
  • total valid cases
  • runtime for all the above

Thanks for responding to my issue, and more than willing to do paid compensation for any advice/consulting on this stuff.

Cheers,

Sam

@agroce
Copy link
Owner

agroce commented Jul 20, 2023

@sambacha this all sounds very interesting, and I think I can likely be of help on several of these items. Rather than hash out here, perhaps we should just schedule a meeting soon-ish, via email?

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

2 participants