| commit | 99e8a9fba50d86cfbc5857ff162b49adf7814f50 | [log] [tgz] |
|---|---|---|
| author | Robert Nystrom <rnystrom@google.com> | Fri Jun 14 23:35:10 2019 +0000 |
| committer | commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jun 14 23:35:10 2019 +0000 |
| tree | fd07ec59398d0c4329778042b91c8f8a7813933f | |
| parent | 3bacc84c1e33860a43e64da5d4aabeb6ba84f919 [diff] |
Move the test runner (i.e. "test.dart"/"test.py") to pkg/. This makes it an actual Pub package like most other code inside the SDK repo. The main goal is to make it easier to write tests for the test runner itself. This change: - Moves all of the code from tools/testing/dart/ over to pkg/test_runner. Most of it ends up under test_runner/lib/src. - Move tools/testing/dart/main.dart to pkg/test_runner/bin/test_runner.dart. - Move standalone_2/io/test_runner_test.dart to pkg/test_runner/test/test_runner_test.dart. I don't think it currently works, but it wasn't being run in its old location either. - Add test_runner to the analysis-server bot. This ensures the test_runner package is static error clean. - Remove standalone_2/io/test_runner_analyze_test.dart which used to attempt to do the above and is no longer needed. - Update test.py to look for the test runner at its new location. - Add test_runner to the repo .packages file and remove the weird test_dart pseudo-package. (I think this fixes #35279.) - Remove status file entries for the removed standalone_2 tests. There are no code changes to the test runner itself aside from fixing up import paths. Change-Id: I3d05d50d222b291848fa5a30de2846e803bc81e6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/105821 Commit-Queue: Bob Nystrom <rnystrom@google.com> Reviewed-by: Jonas Termansen <sortie@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web
Dart has flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
Visit the dart.dev to learn more about the language, tools, getting started, and more.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.