Skip to content

test/coverage excluded pattern #201

@cchris28

Description

@cchris28

I frequently use unit tests in vscode as a debug and investigative tool and the results while useful are not really unit tests. So I want to put them in a separate folder that is not run automatically.

The current invocation of pytest searches all directories in the project for the test pattern name and runs them both for testing and coverage.

I suggest we have a convention for the --ignore= argument to pytest for test like code that can be run manually but not automatically.

I have been using --ignore=tests/private which makes it show up in vscode as a set of tests (useful for development) and get ignored by pre-commit. Note that pre-commit quiets everything so you normally do not notice that it is picking up ALL files that match the test string.

Possibly we should restrict it to src tests since those are the only source directories we have.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationgood first issueGood for newcomers

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions