Christer Eliasi-Swahn
Christer Eliasi-Swahn
Hi @kawa1214! This is a useful tool for us but this issue stops us from using it in CI. Any progress on this?
This issue should be high priority to fix, it unfortunately makes melos unreliable to use in any scripting including CI. Are you adressing it? It seems the culprit is in...
I made a fork of your repo to see if it was a difficult fix or not, but the test suite failed out of the box (formatting checking tests it...
> What OS are you on? The test suite passes for me, but I know it does have some flaky/broken tests in the CI too unfortunately (#724). > EDIT: also...
I made a first PR to fix the failing test cases. If this is approved and merged I could go ahead and look at this actual issue. https://github.com/invertase/melos/pull/799
> The name of the directory is how the lint is currently deciding that it _is_ a test. This is consistent with the package layout conventions documented on https://dart.dev/tools/pub/package-layout. For...
> > only uses `_test.dart` to know if a file is a test > > That's also fragile. If you have a test split into multiple libraries, perhaps some code...
Having `integration_tests` (and `testing`) be clearly documented is all well and good! It would still be valuable to have a more flexible support for the analyzer recognizing it is in...
These tests are differentiated on needing different harnesses / setups. They can’t run with the same ’dart test’ invocation. The regular ’test’ folder is reserved for tests that don’t need...
This is a quite old issue but the bug is still there. Can this be bumped?