necessist

necessist copied to clipboard

This would benefit projects where (1) there are tests that are slow to run, and (2) those tests have no removal candidates. Syntax-wise, the option might be`--dry-run MODE`, with `MODE`...

smoelius

It has been suggested a few times that Necessist could incorporate coverage information. Specifically, Necessist could forgo removing statements and method calls that are never executed. This would reduce Necessist's...

smoelius

Output a slither like markdown checklist for easier analysis

3

tarunbhm

Currently Necessist dry runs each test file and then starts mutating it line by line to find surviving mutations. The dry run of the next file required an additional build...

tarunbhm

Incremental Testing based on `git-diff`

2

Hello @smoelius, @moodmosaic told me about [this](https://github.com/trailofbits/necessist/issues/935) and found it quite intriguing and a great complement to the concept of mutants! Currently, I'm focusing on incorporating mutation testing into Stacks....

ASuciuX

Number of test files is misleading

1

Necessist might say `0 candidates in 0 test files` when, in reality, test files _were_ actually scanned. The bug is that Necessist requires a test file to contain at least...

smoelius

At least with https://twitter.com/Montyly/status/1732749142663848056

montyly

Allow mutation of original source code, instead of tests

1

If I understand correctly, necessist will always mutate tests. However, we could also mutate the original source code and re-run the original tests to check if they pass. In that...

ggrieco-tob

E.g., it should look for `#[ignore]` in Rust tests, and `describe.skip` in Hardhat tests.

smoelius

Reduce removal of nonbuildable statements

2

I see a few examples of where the exception list could be refined, however some might require some static analysis. We could include exceptions for `.function` in `vm.function` and `abi.function`....

0xPhaze