test

You can apply it to all of them at once, but it might be better to do COVERAGE first to reduce the number.

Since it is obvious that mutations in the untested range will not be detected by the test

Over 300 detections were made in mutmut, and information flooding

Rather than looking at individual mutations and thinking about how to cover them, it would be better to first take a quick look at what areas are not covered by the coverage html.

→ down to 16 pieces.

The -t option on the command line is used to test the test mechanism, but the argparse part is included in the coverage and the test is rewritten with the values of the various options.

Interesting detection

I used to fix random.seed for test repeatability when I used to use random.choice, but now I don't use random numbers anymore. mutmut pointed out to me that "changing the random seed makes no difference in test results!"

# pragma: no mutate

---