Repository navigation
Centralized location for test file output #17259
Description
If we had the notion of a test output folder, tests would have the flexibility to not only write to stdout and stderr, but to write more helpful info, like the contents of adb logs, screenshots, etc.
Proposal
During flutter test, we have The Flutter tool create a temp folder before running any tests. For each test in the suite, the test harness will create a subfolder dedicated to that test and set the path of that subfolder into an environment variable (e.g. TEST_OUTPUT_DIR) before spawning the test.
When each test is done running, if it did not output anything into its folder, the test harness will delete the empty directory. When all tests are done running, if none of the tests wrote any output files, it'll delete the temp directory.
If any files were written during any of the tests, the Flutter tool will keep the temp directory intact and print a message to the caller that "test outputs are available at ..."
Activity
[-]Allow centralized place where tests can output files[/-][+]Centralized location for test file output[/+]tvolkert commentedon Jul 17, 2020
Noting that as of July 2020, this would still be nice to have.
tvolkert commentedon Oct 22, 2021
Triaging all the bugs I've ever created. As of Oct 2021, this would still be nice to have.
flutter-triage-bot commentedon Jul 9, 2023
This issue is assigned but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
github-actions commentedon Jul 11, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.