Cristiano Salerno
Cristiano Salerno
Oh and btw you can also use `pyzw` extension (same result as you do with `pyw`)
Probably same problem found as #863
Hi @johannesn, thank you for your reply, but unfortunately even with your suggestion (adding hamcrest-core to the dependencies) PIT didn't find the other tests
Thanks to your edit, I could see what's going on under the hood; it seems that the classpaths of classes and tests got mixed, because while searching for testclasses, the...
Some edit: With this little edit, I was able to see how the test finder **skips** the tests that contains inner classes. ``` 16.26.21 PIT >> INFO : MINION :...
Update: I tried to change my test classes glob with this - `org.apache.commons.lang.time.*Test` - and decided to follow the execution flow, until I got this report. ``` 9.46.48 PIT >>...
Finally found the problem, that is the method `isJUnitThreeSuiteMethodNotForOwnClass` inside the class `org.pitest.junit.JUnitCustomRunnerTestUnitFinder`. In the same class, there are two other methods, `findTestUnits` and `isNotARunnableTest`. The first create a Runner...
Via a proprietary enterprise tool, so some shenanigans are happening with paths. However running `python3 -m venv .venv` works correctly, shouldn't `uv` run the same command?
Isn't possible to implement a fallback in case of custom python installations?
Hi, is there any update regarding this issue?