-
Notifications
You must be signed in to change notification settings - Fork 340
Closed
Labels
in flutterRelates to running Flutter appsRelates to running Flutter appsin testingRelates to test execution of Dart/Flutter tests for end usersRelates to test execution of Dart/Flutter tests for end usersis bug
Milestone
Description
Describe the bug
When writing a test that is not inside /test folder, the output of a failing test is "═════..." (take a look at the screenshot)
the debug console displays the correct exception
To Reproduce
flutter create
enter the sample code into the test file integration_test/widget_test.dart
hint: the official flutter tutorial for integration tests also creates it inside /integration_test folder
https://docs.flutter.dev/testing/integration-tests#create-the-integration-test-files
and another hint, because this is a flutter vscode bug I was advised to open the issue here
flutter/flutter#159264
Expected behavior
Displaying the correct exception into the vscode ui
Code Sample
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
Future<void> main() async {
group(
"integration test",
() {
testWidgets("test1", (WidgetTester tester) async {
await tester.tap(find.byKey(Key("NotExistingKey")));
});
},
);
}Diagnostic Data
- Operating System and version: Linux Fedora 41 Gnome
- VS Code version: linux 1.95.3
- Dart extension version: 3.100.0
- Dart SDK version: 3.5.4
- Flutter SDK version: 3.24.5
Metadata
Metadata
Assignees
Labels
in flutterRelates to running Flutter appsRelates to running Flutter appsin testingRelates to test execution of Dart/Flutter tests for end usersRelates to test execution of Dart/Flutter tests for end usersis bug
