Bob Nystrom
6c757957db
DDC's codegen test copies those files to a local "gen" directory so that it can do stuff like splitting out the multitests before it compiles them to JS. I left all of that alone, so the rest of DDC's test infrastructure is unchanged. The very first step that builds the "gen" directory just copies from sdk/tests/..._strong/... instead and the rest is good to go. I did not move not_yet_strong_tests.dart somewhere more accessible yet because I'm not sure if kernel needs it or where it should go. I did not create any status files because DDC doesn't need them and there are no test suites for the new directories for the other platforms.
23 lines
742 B
HTML
23 lines
742 B
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
|
<meta name="dart.unittest" content="full-stack-traces">
|
|
<title> custom_element_method_clash_test </title>
|
|
<style>
|
|
.unittest-table { font-family:monospace; border:1px; }
|
|
.unittest-pass { background: #6b3;}
|
|
.unittest-fail { background: #d55;}
|
|
.unittest-error { background: #a11;}
|
|
</style>
|
|
<script src="/packages/web_components/webcomponents.js"></script>
|
|
<script src="/packages/web_components/dart_support.js"></script>
|
|
</head>
|
|
<body>
|
|
<h1> Running custom_element_method_clash_test </h1>
|
|
<script type="text/javascript"
|
|
src="/root_dart/tools/testing/dart/test_controller.js"></script>
|
|
%TEST_SCRIPTS%
|
|
</body>
|
|
</html>
|