-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Support generative tests in @cleanup. #5809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Rebased #5785 onto this, just to show that this implementation works. |
👍 that is way simpler than I expected it to be! |
Hum... I am pretty sure that the |
Huh, good catch. I will try to take a look at that tomorrow. |
Thanks. We were just talking about this in #5718. |
I do not have a clear memory of writing that test (but git blame tells me I did!). Sometimes I work in a tdd style where I just run the tests to check things so that test may have never worked. For expediency of getting this merged, maybe throw a KnownFail on this create an issue telling me to fix the test. |
Done. By the way, why was the previous AppVeyor build successful even though the test suite failed? (I am a bit confused.) |
I am even more confused by the new test failure. Anyone wants to take over this PR? (TBH I have little interest in investigating this.) |
Did you run these locally? That error is what happens if the test module is not importable. |
Turns out the fix is trivial, there is just an extra |
I am going to do some local git merging to:
|
Actually, I am having issues getting this to pass locally and am getting a large number of file not closed warnings, see anntzer#1 |
One too many assertions Closes #1
Actually my original patch was wrong... can you see why? It's fixed now. |
Support generative tests in @cleanup.
Support generative tests in @cleanup.
backported to v2.x as 80be853 |
Support generative tests in @cleanup.
All's in the title.