Generate mutations in header files (hpp) but not in tests (cpp)

[correaa]

I have a header-only library that is a bunch of .hpp files.
The tests are .cpp files of course.

When mull frontend generates the mutations for each .cpp, it seems to generate mutations in the .cpp test files as well.

Generating mutations in the .cpp test files is ok in principle.
But given that one has finite time and mutation testing is very time consuming, I would like to prioritize the mutations in the actual library, not in the test code.

Is this possible? can I pass a pattern of files (in this case headers, mylib/include/*.hpp) in which mutations are allowed?

Does it make sense?
If it is not possible now, can it be a good feature request?

[AlexDenisov]

It's possible, we have some file path filters includePaths/excludePaths, here is an example https://mull.readthedocs.io/en/0.24.0/tutorials/ControlMutationsTutorial.html#file-path-filters

[correaa]

so, if I have a structure like this

• mylib
  • mull.yml
  • include
    • mylib.hpp
  • test
    • test1.cpp
    • test2.cpp
  • build

Is this enough?

excludePaths:
  - test*

[AlexDenisov]

I think

excludePaths:
  - .*test.*

should do, but there it only one way to find out 😄