Files
sdk/tests
Vyacheslav Egorov 03d2a819e4 Make --abort_on_assertion_errors more selective.
Only abort() if we detect that we have likely encountered internal Dart2JS
compiler error.

This flag was added in attempt to gather more information on buildbots but
it turns out that always aborting on type/assertion errors does not scale:
some dart2js tests actually test that an error was thrown.

BUG=http://dartbug.com/25753
R=srdjan@google.com, whesse@google.com

Review URL: https://codereview.chromium.org/1691443002 .
2016-02-10 18:49:10 +01:00
..
2016-02-10 15:28:03 +01:00

Run Existing Tests
==================

See the output of

  ../tools/test.py --help

for how to run tests.

See also

  https://code.google.com/p/dart/wiki/Building#Testing

for detailed examples.

Create New Tests
================

See comments above

  factory StandardTestSuite.forDirectory

in

  ../tools/testing/dart/test_suite.dart

for the default test directory layout. By default test-file names must
end in "_test.dart", but some test suites, such as ./co19, subclass
StandardTestSuite and override this default.

See comments at the beginning of

  ../tools/testing/dart/multitest.dart

for how to create tests that pass by failing with a known error. For
example,

  ...
  int x = "not an int"; /// 01: static type warning
  ...

as part of a test will only pass the "--compiler dart2analyzer" test if
the assignment generates a static type warning.