mirror of
https://github.com/encounter/engine.git
synced 2026-03-30 11:09:55 -07:00
333a8058c6
* changes to add firefox as one of the browser options to test_platform and test_runner * Creating a supported_browsers file to put all the different browser related maps and utilities * Remove accidentaly forgotten commented out lines. Clear imports * fix error in screenshot handler * Addressing PR comments. * addressing PR comments part 2:
147 lines
5.1 KiB
Dart
147 lines
5.1 KiB
Dart
// Copyright 2013 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:async';
|
|
import 'dart:convert';
|
|
import 'dart:io';
|
|
|
|
import 'package:pedantic/pedantic.dart';
|
|
import 'package:stack_trace/stack_trace.dart';
|
|
import 'package:typed_data/typed_buffers.dart';
|
|
|
|
import 'package:test_api/src/utils.dart';
|
|
|
|
import 'common.dart'; // ignore: implementation_imports
|
|
|
|
/// An interface for running browser instances.
|
|
///
|
|
/// This is intentionally coarse-grained: browsers are controlled primary from
|
|
/// inside a single tab. Thus this interface only provides support for closing
|
|
/// the browser and seeing if it closes itself.
|
|
///
|
|
/// Any errors starting or running the browser process are reported through
|
|
/// [onExit].
|
|
abstract class Browser {
|
|
String get name;
|
|
|
|
/// The Observatory URL for this browser.
|
|
///
|
|
/// This will return `null` for browsers that aren't running the Dart VM, or
|
|
/// if the Observatory URL can't be found.
|
|
Future<Uri> get observatoryUrl => null;
|
|
|
|
/// The remote debugger URL for this browser.
|
|
///
|
|
/// This will return `null` for browsers that don't support remote debugging,
|
|
/// or if the remote debugging URL can't be found.
|
|
Future<Uri> get remoteDebuggerUrl => null;
|
|
|
|
/// The underlying process.
|
|
///
|
|
/// This will fire once the process has started successfully.
|
|
Future<Process> get _process => _processCompleter.future;
|
|
final _processCompleter = Completer<Process>();
|
|
|
|
/// Whether [close] has been called.
|
|
var _closed = false;
|
|
|
|
/// A future that completes when the browser exits.
|
|
///
|
|
/// If there's a problem starting or running the browser, this will complete
|
|
/// with an error.
|
|
Future get onExit => _onExitCompleter.future;
|
|
final _onExitCompleter = Completer();
|
|
|
|
/// Standard IO streams for the underlying browser process.
|
|
final _ioSubscriptions = <StreamSubscription>[];
|
|
|
|
/// Creates a new browser.
|
|
///
|
|
/// This is intended to be called by subclasses. They pass in [startBrowser],
|
|
/// which asynchronously returns the browser process. Any errors in
|
|
/// [startBrowser] (even those raised asynchronously after it returns) are
|
|
/// piped to [onExit] and will cause the browser to be killed.
|
|
Browser(Future<Process> startBrowser()) {
|
|
// Don't return a Future here because there's no need for the caller to wait
|
|
// for the process to actually start. They should just wait for the HTTP
|
|
// request instead.
|
|
runZoned(() async {
|
|
var process = await startBrowser();
|
|
_processCompleter.complete(process);
|
|
|
|
var output = Uint8Buffer();
|
|
drainOutput(Stream<List<int>> stream) {
|
|
try {
|
|
_ioSubscriptions
|
|
.add(stream.listen(output.addAll, cancelOnError: true));
|
|
} on StateError catch (_) {}
|
|
}
|
|
|
|
// If we don't drain the stdout and stderr the process can hang.
|
|
drainOutput(process.stdout);
|
|
drainOutput(process.stderr);
|
|
|
|
var exitCode = await process.exitCode;
|
|
|
|
// This hack dodges an otherwise intractable race condition. When the user
|
|
// presses Control-C, the signal is sent to the browser and the test
|
|
// runner at the same time. It's possible for the browser to exit before
|
|
// the [Browser.close] is called, which would trigger the error below.
|
|
//
|
|
// A negative exit code signals that the process exited due to a signal.
|
|
// However, it's possible that this signal didn't come from the user's
|
|
// Control-C, in which case we do want to throw the error. The only way to
|
|
// resolve the ambiguity is to wait a brief amount of time and see if this
|
|
// browser is actually closed.
|
|
if (!_closed && exitCode < 0) {
|
|
await Future.delayed(Duration(milliseconds: 200));
|
|
}
|
|
|
|
if (!_closed && exitCode != 0) {
|
|
var outputString = utf8.decode(output);
|
|
var message = '$name failed with exit code $exitCode.';
|
|
if (outputString.isNotEmpty) {
|
|
message += '\nStandard output:\n$outputString';
|
|
}
|
|
|
|
throw Exception(message);
|
|
}
|
|
|
|
_onExitCompleter.complete();
|
|
}, onError: (error, StackTrace stackTrace) {
|
|
// Ignore any errors after the browser has been closed.
|
|
if (_closed) return;
|
|
|
|
// Make sure the process dies even if the error wasn't fatal.
|
|
_process.then((process) => process.kill());
|
|
|
|
if (stackTrace == null) stackTrace = Trace.current();
|
|
if (_onExitCompleter.isCompleted) return;
|
|
_onExitCompleter.completeError(
|
|
Exception('Failed to run $name: ${getErrorMessage(error)}.'),
|
|
stackTrace);
|
|
});
|
|
}
|
|
|
|
/// Kills the browser process.
|
|
///
|
|
/// Returns the same [Future] as [onExit], except that it won't emit
|
|
/// exceptions.
|
|
Future close() async {
|
|
_closed = true;
|
|
|
|
// If we don't manually close the stream the test runner can hang.
|
|
// For example this happens with Chrome Headless.
|
|
// See SDK issue: https://github.com/dart-lang/sdk/issues/31264
|
|
for (var stream in _ioSubscriptions) {
|
|
unawaited(stream.cancel());
|
|
}
|
|
|
|
(await _process).kill();
|
|
|
|
// Swallow exceptions. The user should explicitly use [onExit] for these.
|
|
return onExit.catchError((_) {});
|
|
}
|
|
}
|