Update tests, update CHANGELOG.md

pkgs/native_assets_builder/CHANGELOG.md

@@ -14,6 +14,13 @@
 - **Breaking change**: Remove asset-type specific logic from `package:native_assets_builder`.
   Bundling tools have to now supply `supportedAssetTypes` and corresponding
   validation routines.
+- **Breaking change**: The `NativeAssetsBuildRunner.link()` command will now
+  produce a `LinkResult` containing all assets for the application (not just
+  those that happened to have a linker). This removes the need for a bundling
+  tool to combine parts of `BuildResult` and `LinkResult` and possibly checking
+  consistency of the sum of those parts. Effectively this means: Any asset that
+  doesn't have an explicit linker will get a NOP linker that emits as outputs
+  it's inputs.
 
 ## 0.8.3
 

pkgs/native_assets_builder/test/build_runner/conflicting_dylib_test.dart

@@ -72,14 +72,8 @@ void main() async {
         linkValidator: validateCodeAssetLinkOutput,
         applicationAssetValidator: validateCodeAssetsInApplication,
       );
-      expect(linkResult.success, isTrue);
-
-      final allAssets = [
-        ...buildResult.encodedAssets,
-        ...linkResult.encodedAssets
-      ].where((e) => e.type == CodeAsset.type).toList();
-      final validateResult = await validateCodeAssetsInApplication(allAssets);
-      expect(validateResult, isNotEmpty);
+      // Application validation error due to conflicting dylib name.
+      expect(linkResult.success, isFalse);
     });
   });
 }

pkgs/native_assets_builder/test/build_runner/link_test.dart

@@ -121,8 +121,8 @@ void main() async {
         );
         expect(linkResult.success, true);
 
-        expect(
-            _getNames(linkResult.encodedAssets), unorderedEquals(linkedAssets));
+        expect(_getNames(linkResult.encodedAssets),
+            unorderedEquals([...builtHelperAssets, ...linkedAssets]));
       });
     },
   );