
I'm working on fixing up all tests that rely on fs.currentDirectory to allow us to run concurrently. This one proved to be really tricky because it calls a lot of code and spawns multiple processes that have a mix of absolute and relative paths passed to them. I managed to handle some of it with a ChrootFileSystem, but the paths passed to the external processes were wrong. The functionality here is covered by all of the integration tests that use flutter_tester that were added after this, including flutter_run_test.dart, lifetime_test.dart etc. in this same folder but because they're run through `flutter run` as a separate process they get to set their own working directories without affecting other tests if run concurrently.
Integration tests
These tests are not hermetic, and use actual Flutter SDK.
While they don't require actual devices, they run flutter_tester
to test
Dart VM and Flutter integration.
Some of these tests change the current directory for the process, so only one test can be run at a time. Use this command to run:
../../bin/cache/dart-sdk/bin/pub run test -j1