One-liner in bandit config to skip B101 assert_used in files matching a filter

Currently you can exclude a directory and you can skip certain tests across all scanned files. It would be very handy to be able to exclude test_* pytest files from the B101 assert test with a simple one liner in the .bandit config file.

This is a feature request for something like:

In .bandit

[bandit]
pytest_filter: test_* #excludes B101 in files matching test_*

Excluding all B101 is not a good solution, because I want to know about B101 in non-test modules.

Also, I’d like to be able to exclude on file filter like test_* rather than directory test/ because that filter works better across projects I have seen where test directory might not be named consistently, but all the pytests are generally named a special way e.g. test_*

This will allow a more general (across projects) config file to be set up.

[diegovalenzuelaiturra]

Hi, the following may be helpful to configure bandit to avoid raising B101 assert_used warnings on python tests.

• https://github.com/PyCQA/bandit/issues/603#issuecomment-971057519

[loikein]

Does this not work anymore?