Maksim Sadym
Maksim Sadym
can be related to https://github.com/GoogleChromeLabs/chromium-bidi/issues/1717
Historically, the strict assertions were done in order to be aware of any protocol changes. This was reasonable when the amount of e2e tests was relatively low and the protocol...
Note that [there is a mechanism for `
Log: [2024-01-18T13-20-00.261Z.log](https://github.com/GoogleChromeLabs/chromium-bidi/files/14521054/2024-01-18T13-20-00.261Z.log) Output: ``` ==================================== ERRORS ==================================== _ ERROR at setup of test_subscribeToNestedContext_subscribesToTopLevelContext[websocket0] _ event_loop = request = kwargs = {'_websocket_connection': } setup = @functools.wraps(fixture) def _async_fixture_wrapper( --- Logging error...
https://github.com/GoogleChromeLabs/chromium-bidi/issues/2056
> @sadym-chromium There seems to be a regression with the latest changes in test runner. I can't see CDP logs for the E2E failures when I download the logs. Could...
> What do we do in these situations? In general there are 3 options: 1. Implement in CDP. 1. Implement on top of existing CDP functionality + some extra logic....
> > 1. Implement in CDP. > > How can we do so? This was also suggested by @whimboo on [web-platform-tests/wpt#38931 (comment)](https://github.com/web-platform-tests/wpt/pull/38931#issuecomment-1468350079) > > Could you give me a pointer...