-
Notifications
You must be signed in to change notification settings - Fork 218
Explanation of why no tests ran #651
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
Comments
Agreed. This is my favorite:
Um... yay! |
I believe the particular issue is due to a bug or SDK incompatibility that should go away when you |
The error still exist in my open project. My project structure When I run |
@alexZaicev This is because you need to follow the naming conventions, by default the test runner only considers files ending in So in this case it would be nice if we printed something like |
@jakemac53 Thanks for the info, I`ll change my file names accordingly. Can this be added to the documentation? Under section 'Writing Tests' |
It's under the We probably should add it to the Writing Tests section as well. |
An excerpt of email by @chalin (emphasis mine):
As I assume it is never the intention of the author to use
pub run test
to run no tests, can test recover and explain why no tests were run? In this particular case it was because all tests were filtered out since the default platform is VM, and all of Patrice's tests were browser based.I'd like to see:
The text was updated successfully, but these errors were encountered: