flutter/dev/integration_tests/web/lib/framework_stack_trace.dart
Jackson Gardner 31209d04ff
flutter test --wasm support (#145347)
* Adds support for `flutter test --wasm`.
  * The test compilation flow is a bit different now, so that it supports compilers other than DDC. Specifically, when we run a set of unit tests, we generate a "switchboard" main function that imports each unit test and runs the main function for a specific one based off of a value set by the JS bootstrapping code. This way, there is one compile step and the same compile output is invoked for each unit test file.
* Also, removes all references to `dart:html` from flutter/flutter.
* Adds CI steps for running the framework unit tests with dart2wasm+skwasm
  * These steps are marked as `bringup: true`, so we don't know what kind of failures they will result in. Any failures they have will not block the tree at all yet while we're still in `bringup: true`. Once this PR is merged, I plan on looking at any failures and either fixing them or disabling them so we can get these CI steps running on presubmit.

This fixes https://github.com/flutter/flutter/issues/126692
2024-03-21 20:08:07 +00:00

101 lines
2.4 KiB
Dart

// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
import 'dart:js_interop';
import 'package:flutter/foundation.dart';
import 'package:flutter/widgets.dart';
import 'package:meta/dart2js.dart';
import 'package:web/web.dart' as web;
// Tests that the framework prints stack traces in all build modes.
//
// Regression test for https://github.com/flutter/flutter/issues/68616.
//
// See also `dev/integration_tests/web/lib/stack_trace.dart` that tests the
// framework's ability to parse stack traces in all build modes.
Future<void> main() async {
final StringBuffer errorMessage = StringBuffer();
debugPrint = (String? message, { int? wrapWidth }) {
errorMessage.writeln(message);
};
runApp(const ThrowingWidget());
// Let the framework flush error messages.
await Future<void>.delayed(Duration.zero);
final StringBuffer output = StringBuffer();
if (_errorMessageFormattedCorrectly(errorMessage.toString())) {
output.writeln('--- TEST SUCCEEDED ---');
} else {
output.writeln('--- UNEXPECTED ERROR MESSAGE FORMAT ---');
output.writeln(errorMessage);
output.writeln('--- TEST FAILED ---');
}
print(output);
web.window.fetch(
'/test-result'.toJS,
web.RequestInit(
method: 'POST',
body: '$output'.toJS,
)
);
}
bool _errorMessageFormattedCorrectly(String errorMessage) {
if (!errorMessage.contains('Test error message')) {
return false;
}
// In release mode symbols are minified. No sense testing the contents of the stack trace.
if (kReleaseMode) {
return true;
}
const List<String> expectedFunctions = <String>[
'topLevelFunction',
'secondLevelFunction',
'thirdLevelFunction',
];
return expectedFunctions.every(errorMessage.contains);
}
class ThrowingWidget extends StatefulWidget {
const ThrowingWidget({super.key});
@override
State<ThrowingWidget> createState() => _ThrowingWidgetState();
}
class _ThrowingWidgetState extends State<ThrowingWidget> {
@override
void initState() {
super.initState();
topLevelFunction();
}
@override
Widget build(BuildContext context) {
return Container();
}
}
@noInline
void topLevelFunction() {
secondLevelFunction();
}
@noInline
void secondLevelFunction() {
thirdLevelFunction();
}
@noInline
void thirdLevelFunction() {
throw Exception('Test error message');
}