It’s related to this thread:
The xxx.xxx are for files in the tests folder.
tests.test_1
tests.test_2
etc.
This is part of a Jenkins job. After the code is built, it gets unit tested (using tox), then it is scanned by sonar. The analysis logs spams 8000+ WARNING messages as I believe they are correspond to the unit tested. I have other jobs that is also having this issue.
Are any of my exclusion patterns correct? If so, the sonar-scanner should not scan the tests directory, or is there something else I am missing?
Thanks