refactor test setups towards fixtures and hinting#968
refactor test setups towards fixtures and hinting#968BoboTiG merged 17 commits intogorakhargosh:masterfrom
Conversation
|
Well, that's a great job :) |
|
FTR if it's too time consuming, it's also OK to skip Mypy in tests. It's up to you :) |
|
Yes, they are expected to move to |
|
Fully agree 👍🏻 |
|
It seems there are regressions in macOS tests. FTR:
|
|
I think we could just skip pypy tests on Windows, they never make it (enven if it's temporary, maybe someone later will find some time/motivation to dig into that problem). And now that I see soo many PRs (💪🏻) the release job being run every time may not be a good idea finally, WDYT? |
I guess we could also document testing status and plans in a dedicated issue instead of email as I had initiated. Either way. |
Personally, I wouldn't. I don't want to find that broken when I'm trying to make a release. But, I haven't really looked into that one to see what's going on there. |
|
I'll open issues for the tests 👍🏻 |
|
To be clear, I meant that for general test work. Regressions here I'll just look at here. |
|
Yup, I got it :) |
|
I do expect to put some time into the state of the tests, but figured I'd wait until I heard something about the status. Even if that is 'they are having trouble and someone needs to do the research as to what they need because we don't know yet'. |
|
Ready to merge on my end. |
|
Should I add more xfails or flake retries for these tests? But, I'm not aware of anything else to be done here. |
|
It's OK then. Those tests are "pure randoms" if I may. |
|
That's an impressive job, thanks a lot @altendky 🍾 |
This is an attempt to switch to well hinted pytest fixtures that mypy and flake8 will understand with as little change to the actual tests as possible. This does not necessarily represent the pattern I might normally apply. That can come later, if at all.
Draft for: