Fix dart2wasm tests with custom HTML files (#2626) When running tests with `dart2wasm` and a custom HTML file, the JS bootstrap file `run_wasm_chrome.js` failed because it tried to read `dataset` from a DOM element with ID `WasmBootstrapInfo`, which is not present in custom HTML files. This commit updates `run_wasm_chrome.js` to fallback to inferring the `.wasm` and `.mjs` URLs from `document.currentScript.src` if the `WasmBootstrapInfo` element is not found. Added a regression test to verify the fix. Fixes #2625
Welcome! package:test is the standard testing library for Dart and Flutter. If you have questions about Dart testing, please see the docs for package:test. package:test_api and package:test_core are implementation details and generally not user-facing.
package:checks is a relatively new library for expressing test expectations. It's a more modern version of package:matcher and features a literate API.
| Package | Description | Issues | Version |
|---|---|---|---|
| checks | A framework for checking values against expectations and building custom expectations. |  |  |
| fake_async | Fake asynchronous events such as timers and microtasks for deterministic testing. | |  |
| matcher | Support for specifying test expectations via an extensible Matcher class. Also includes a number of built-in Matcher implementations for common cases. | |  |
| test | A full featured library for writing and running Dart tests across platforms. | |  |
| test_api | The user facing API for structuring Dart tests and checking expectations. |  | |
| test_core | A basic library for writing tests and running them on the VM. |  | |
| test_descriptor | An API for defining and verifying files and directory structures. | |  |
| test_process | Test processes: starting; validating stdout and stderr; checking exit code. | |  |