Cannot use "pytest test_*" (with wildchar filter) to collect cases on Windows 7 command line

[chenzx]

"pytest test_*" cmd lets me selectively run specific tests which are classified by filename prefixes
this works on my mac perfectly
but when i try the trick on a windows 7 machines, pytest cannot collect any cases.

[RonnyPfannschmidt]

at first glance i strongly suspect this is a shell issue
in mac its likely that bash (i hope thats correct, i use linux)just expands test_* to a number of filenames

im not aware about how the shells on windows manage it,
my understanding is, that on windows, the programs are supposed to expand wildcards, which pytest currently does not do

adding passed wild-card expansion would be a new feature,
if only support foor * expansion is added,
i believe it wouldn't be a breaking change

in that case its a help wanted item

[The-Compiler]

Pretty much what @RonnyPfannschmidt says - also see e.g. psf/black#1198 and pallets/click#1096.

Note that if pytest did that kind of expansion, it should be done on Windows only.

[RonnyPfannschmidt]

i believe support on all platforms is possibly sensible, as it would allow wildcard support in PYTEST_ADDOPTS and the addopts option

[Zac-HD]

The problem with expanding wildcards is that it's possible to have a file literally named test_* that you want to run pytest on, and then what?

Shells all have a way to disable wildcard expansion one-by-one for this reason, which I really don't want to duplicate in pytest.

[The-Compiler]

The problem with expanding wildcards is that it's possible to have a file literally named test_* that you want to run pytest on, and then what?

That isn't possible on Windows - hence my proposal to only do the expansion on Windows. Yes, that means there's no way to use wildcards in PYTEST_ADDOPTS and addopts, but I can't think of a good reason to use them there to be honest.

[RonnyPfannschmidt]

Good point, we should have a option to control the behaviour with sane defaults for posix vs windows

[harishkesavarao]

@RonnyPfannschmidt @The-Compiler Has this been fixed via #1830?

[RonnyPfannschmidt]

The linked issue it's about raises?