-
Danny Tuppeny authored
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.
Name |
Last commit
|
Last update |
---|---|---|
.github | ||
bin | ||
dev | ||
examples | ||
packages | ||
.cirrus.yml | ||
.gitattributes | ||
.gitignore | ||
AUTHORS | ||
CONTRIBUTING.md | ||
LICENSE | ||
PATENTS | ||
README.md | ||
analysis_options.yaml | ||
appveyor.yml | ||
flutter_console.bat |