Sigmund Cherem
25bc18c3b3
* Introduce steps to execute tests in AOT (using gen-kernel,
dart2bytecode, and aot compiler)
* Accept using filesystem-scheme to provide dynamic_interfaces.yaml input
* Accept empty dynamic_interfaces.yaml
* Make temporary test changes to get them running:
* include core types in dynamic_interfaces that we may want to have
by default
* rename entrypoint to `main`
Most existing test pass, the two tests that validate that a library
cannot be defined twice fail (expectation is to throw, bytecode ignores
the second definition).
To run locally:
```
./tool/build.py -m release --dart-dynamic-modules create_sdk
DART_CONFIGURATION=ReleaseX64 out/ReleaseX64/dart-sdk/bin/dart pkg/dynamic_modules/test/runner/main.dart -r aot
```
Tested: CL adds additional test coverage, currently ran manually, integrated in CI in child CL
Change-Id: I4868e765855d9951bff160c18b846aa628f5e0b4
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/383928
Reviewed-by: Alexander Markov <alexmarkov@google.com>
Commit-Queue: Sigmund Cherem <sigmund@google.com>
Tests for Dart dynamic modules
This folder contains tests for an experiment of implementing dynamic modules in Dart. All tests are written in the style of the language end-to-end tests.
Folder structure
Each folder consists of a single test scenario. You'll find 4 kinds of files:
-
main.dart: the host application that will later load dynamic modules. This will be the core driver of the test. -
shared/: folder containing multiple libraries with code that can be used by both the host application and dynamic modules. -
modules/: folder containing code private to dynamic modules. It includes libraries with common code as well as an entrypoint file per dynamic module. Entrypoint files are namedentryN.dartand must define an exported dynamic module entrypoint. Note: semantics limit that two dynamic modules can't share code unless they are compiled in a chained fashion, currently the test harness focuses on compiling modules in isolation and ensuring conflicts don't arise. -
dynamic_interface.yaml: a contract specifying what parts of the host application and libraries inshared/are visible to dynamic modules.
Execution
We've build a test framework that frontloads compilation, so that execution of the test can be streamlined. This means that:
-
The host app will be compiled first, using
dynamic_interface.yamlas a specification for AOT compilers. -
Each and every dynamic module entrypoint in
modules/will be compiled to create a dynamic module artifact. -
Finally an execution environment will be launched that will in turn load each dynamic module as prompted by the test logic.
Commands to drive the loading and execution of each dynamic module are
controlled by a helper library in ../common/testing.dart, which
uses the Dart SDK API and abstracts away differences between platforms.
Example
Refer to update_top_level. This is one of the simplest tests that illustrates
the utilities and concepts in this framework.