firka/flutter
firka/flutter
4
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
flutter/packages/flutter_tools/test/commands.shard
History
includecmath f1013e6873
[flutter_tools] According to AnalysisSeverity return exit code detailed proposal (#61589) 
No matter what level(error, warning, info) issues flutter analyze always return fatal exit code(1). CI/CD environment receive 1(!0). This may leads to e.g. Jenkins Build step 'Execute shell' marked build as failure.
I propose according to AnalysisSeverity level return fatal(1) or success(0) exit code.
2020-10-01 18:50:33 -07:00
..
hermetic
Replace MockArtifacts with Artifacts.test() (#67012)
2020-09-30 16:25:29 -07:00
permeable
[flutter_tools] According to AnalysisSeverity return exit code detailed proposal (#61589)
2020-10-01 18:50:33 -07:00
README.md
…

README.md

This directory contains tests for specific flutter commands.

Tests that are self-contained unit tests should go in hermetic/.

Tests that are more end-to-end, e.g. that involve actually running subprocesses, should go in permeable/.

The ../../tool/coverage_tool.dart script (which is used to collect coverage for the tool) runs only the tests in the hermetic directory when collecting coverage.