d55adbed81
The new test is specifically for `dart2js --generic-method-syntax ..`, executed programmatically using 'memory_compiler.dart'. It verifies that each method type variable is treated as if it had been an alias for `dynamic` (so the static analysis allows almost all usages of these type variables, silently). Note that this behavior is unlikely to be available with any other tools, and even `dart2js` will behave differently when generic methods are implemented fully. Hence, the new test will only be useful as-is during a transitional period. R=johnniwinther@google.com Review URL: https://codereview.chromium.org/1939053002 .
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.