-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Closed
Labels
a: assetsPackaging, accessing, or using assetsPackaging, accessing, or using assetsa: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.toolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
Its kind of a no-brainer that you might want to validate your assets in some way. Especially when you have multiple people working on the same project (not all of them developers). Furthermore its common to want to test the code that processes those assets, without having to hardcode versions of the assets in the tests, that might not match up with the live assets as they change through time. Finally of course, there is testing widgets that use the asset bundle, and need valid assets from it to behave properly.
#8490 seems to confirm that reading assets during test is not possible.
victoraldir, kentcb, vaughandroid, allandaleho, zoechi and 26 more
Metadata
Metadata
Assignees
Labels
a: assetsPackaging, accessing, or using assetsPackaging, accessing, or using assetsa: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.toolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.