-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remove Expectations defexpect implicit expect support? #15
Comments
Do you want |
Yes, I think they're valuable as a migration tool -- from the You could make it fail to force folks to correct it, but I suspect the universe of Expectations users that a) use the implicit form and b) are migrating to LazyTest is extremely close to empty (i.e., it's just me). Do you have a diagnostic if a test suite has no tests? That would catch it, I think? |
Throwing a warning or a test failure if a suite has no children would be a good solution, good idea. |
And to be clear, the only reason Anyone migrating from |
I think this was a mistake in Expectations:
I think you should not support it in LazyTest.
You only recently added
defexpect
so I doubt anyone is relying on this behavior (I'm actively removing it from the "legacy" tests at work, and none of the nses I've converted to LazyTest rely on this).The text was updated successfully, but these errors were encountered: