Robert Nystrom
99e8a9fba5
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>
Testing of source maps
This folder contains two types of tests for validating sourcemaps: the debugging behavior and the stacktrace behavior.
For both there are 2 suits: One for (legacy) DDC and one for DDC with kernel (DDK).
Running the tests likely requires the compilation of the correct targets. DDK currently also
requires ddc_sdk.dill inside
{sdkroot}/{out,xcodebuild}/ReleaseX64/gen/utils/dartdevc/kernel/ddc_sdk.dill.
Except for that, running them should simply be a matter of executing the *_suite.dart files.
All tests are plain Dart files and goes in "testfiles" (debugging tests) or "stacktrace_testfiles" (stacktrace tests). They are automatically picked up by the testing framework.
Debugging tests (step tests)
See README.md in pkg/sourcemap_testing.
Debugging a test
One can filter which tests are run by running (from the sourcemap folder):
dart sourcemaps_ddc_suite.dart -- sourcemaps_ddc//printing_class_fields
One can additionally get debug output for failing tests (i.e. tests with different outcome than expected), e.g.:
dart sourcemaps_ddc_suite.dart -Ddebug=true -- sourcemaps_ddc//printing_class_fields
The latter is also useful in combination with /*fail*/ when adding new tests to see all the places
where the debugger stopped (both in JS positions and translated to dart positions).
For instance -Ddebug=true -- sourcemaps_ddk//next_through_catch_test with a /*fail*/
currently gives output like the following:
Stop #1
test.main = function() { | main() {
try { | try {
let value = /*STOP*/"world"; | var value = /*STOP*/"world";
dart.throw(dart.str`Hello, ${value}`); | // Comment
} catch (e) { | throw "Hello, $value";
Stop #2
try { | var value = "world";
let value = "world"; | // Comment
/*STOP*/dart.throw(dart.str`Hello, ${value}`); | /*STOP*/throw "Hello, $value";
} catch (e) { | }
let st = dart.stackTrace(e); | // Comment
Stop #3
dart.throw(dart.str`Hello, ${value}`); | }
} catch (e) { | // Comment
let st = /*STOP*/dart.stackTrace(e); | catch (e, /*STOP*/st) {
{ | print(e);
core.print(e); | print(st);
[...]