|author||Daniel Erat <email@example.com>||Fri Mar 08 03:07:01 2019|
|committer||chrome-bot <firstname.lastname@example.org>||Sat Mar 09 05:21:11 2019|
tast-tests: Make chrome.Chrome use WebSocket for browser. Update chrome.Chrome to use a WebSocket connection to communicate with the browser instead of using the Chrome DevTools Protocol's HTTP endpoints. There was formerly a weird mix where chrome.Conn used WebSocket connections to manipulate pages (including closing them), but chrome.Chrome used HTTP to create and enumerate targets. I'm not too optimistic that this will fix the "websocket: bad handshake" errors that seem occasionally happen when creating a new target after closing another target, since it now seems like the issue is that the target isn't even being created. But this at least makes the code more consistent and increases what we can try in the future (e.g. watching for targets being created or destroyed). I'm also removing Chrome.reconnect, which doesn't appear to help at all, and fixing some OOBE connection leaks that I just noticed. BUG=chromium:925703 TEST=ran tests using chrome.LoggedIn precondition in a loop for hours Change-Id: I31a64f6d7a5baa8293ac0d903933de6a017ea174 Reviewed-on: https://chromium-review.googlesource.com/1510713 Commit-Ready: Dan Erat <email@example.com> Tested-by: Dan Erat <firstname.lastname@example.org> Reviewed-by: Dan Erat <email@example.com>
This repository contains integration tests that are run by Tast.
local/- Code related to local (i.e. on-device or “client”) tests.
remote/- Code related to remote (i.e. off-device or “server”) tests.
Shared code, the main
tast executable, the
remote_test_runner executables responsible for running bundles, and documentation are located in the tast repository.