-
Notifications
You must be signed in to change notification settings - Fork 189
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
spike: Wrong test suite identified when running "very_good test" with optimization #401
Comments
This needs dedicated research time to identify the core issue before it can be fixed. |
Not sure if this helps with the solution but: I was experiencing the same problem when trying to use Basically the fix was:
After that, I just needed to do some |
If you have a simple Bloc test, and the test fails... the assertion is in the package instead of your code |
Description
As described here, when running
very_good test
with optmization, the internal tooling will identify<cwd>/test/.test_runner.dart
as the suite of tests.Steps To Reproduce
very_good test
without--no-optimization
<cwd>/test/.test_runner.dart
as output.Expected Behavior
Outputs should show the real test suite,
Additional Context
As
<cwd>/test/.test_runner.dart
is a temporary file generated by mason, it is expecetd to somehow proxy the real suite or somehow allow its recover from some other field (group name without snake case?).It is important that we are bound to the information passable via the JSON Reporter Protocol.
The text was updated successfully, but these errors were encountered: