feat: merge milestone 4 #83
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make sure `--use-generated-mutants` cannot be used with `--coverage`, `--downsampling-ratio-percentage`, `--mutate-functions` and `--mutate-modules`. Add a `--downsampling-ratio-percentage` option to both `move-spec-test` and `move-mutation-test` tools.
If we have a single mutant, fetching rayon thread won't work, since rayon won't even be used in such a case. Do not try to fetch the rayon thread when there is a single mutant present.
- use `fs_extra` instead of handmade `CopyAllDir` function - run original package on the max number of threads, while use a single-thread test execution for all mutants within all rayon threads (this increases the overall execution time) - add additional benchmark for `executing_original_package` - change formula for calculating average mutant execution time - move manifest rewriting to `mutator-common` crate so that `move-mutotor` can use `mutator-common` without causing circular dependency - ensure move-mutator doesn't use the original package path
Allow users to display the mutation testing summary from the report.
Short CLI args are not used in aptos-core, so our tooling should align. Also: use the `package-dir` (which is more common in `aptos-core`) instead of the `package-path` option.
There are two fixes here: - fix for parallel mutant generation (using indexed file can cause file name collisions, so we are using hash of the mutant in the mutant file name instead) - disabling process's ability to generate coverage report as by doing that we configure TRACING_ENABLED flag deep within MoveVM which is a statically configured flag that cannot be reset anymore. From now on, we will ask users to generate `aptos move test --coverage`
Mutator file configuration is a deprecated feature since it's never been used nor there is a need for it to be used since the tool is too slow to be used on the whole project.
We recently merged a PR in aptos-core to improve their `merge_span` function, and now we can use their implememntation: aptos-labs/aptos-core#15120
- How-to-use doc should be used as a quick introduction document to Move developers.
vineethk
reviewed
Dec 17, 2024
- clean the main readme and move the showcase tutorial inside - add installation instructions to child readmes
vineethk
reviewed
Dec 19, 2024
The update is required after the simple project has been recently updated (removed spec blocks from the Sum module).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is included here:
display-report summarycommand