-
Notifications
You must be signed in to change notification settings - Fork 213
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
top-level expect
throws nSM when not using runner
#132
Comments
Aha, naturally as soon as I file this I figure out what's going on. So it seems we have some code that runs It might be good to support top-level expect (or at least not NoSuchMethodError) but way lower priority |
expect
throws nSM when not using runner
dart_style becomes a dev_dependency, and remove the ability to auto-run it from dart backend, instead use the test formatter migrate to package:test, which has a few tricky bits: * expect can only appear inside a test now (dart-lang/test#132) * mirrors is needed to get the test folder (dart-lang/test#110) * test `main` can't take arguments. not sure what's up there, but not a big deal for us either. [email protected] Review URL: https://codereview.chromium.org/1166683005
dart_style becomes a dev_dependency, and remove the ability to auto-run it from dart backend, instead use the test formatter migrate to package:test, which has a few tricky bits: * expect can only appear inside a test now (dart-lang/test#132) * mirrors is needed to get the test folder (dart-lang/test#110) * test `main` can't take arguments. not sure what's up there, but not a big deal for us either. [email protected] Review URL: https://codereview.chromium.org/1166683005
EDIT: see comment #132 (comment), this only affects top-level
expect
statements.running
results in
Seems to happen in 0.12.2 as well as master.
According to docs:
Context: I'm trying to migrate some existing code from unittest, and easiest thing to do was to leave our various scripts running the test files directly. That was also a really nice way to debug tests by launching them from WebStorm. Not sure if/how the debugger can attach to "pub run test". At first glance I wasn't sure what the workaround would be, as it doesn't look like I can create an Invoker or a runner environment without depending on "src" (don't worry, I won't do that :) ). So at the moment I'm stuck on older unittest.
The text was updated successfully, but these errors were encountered: