New issue
Advanced search Search tips

Issue 902215 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 902658
issue 841556
issue 887538



Sign in to add a comment

Integration tests for proxy API

Project Member Reported by ntfschr@chromium.org, Nov 6

Issue description

I can't find any integration tests for the new proxy API. Although this got unit tested in the relevant CLs, this doesn't cover the integration with WebView (and that code could therefore break).

Specifically, the proxy code doesn't currently work with the network service, yet this isn't visible in our test filter: https://cs.chromium.org/chromium/src/testing/buildbot/filters/mojo.fyi.network_webview_instrumentation_test_apk.filter

Can we add integration tests?
 
Right, I thought there were some CTS-style tests for this?
Nate by integration do you mean CTS / instrumentation or both? (the filter is integration tests only).
Looks like indeed we would need some fixes to make it work with NS.

We're gonna have tests in the support library and CTS when it's implemented in the framework. Do we need any additional tests?
The issue is that chromium developers aren't generally aware of CTS or AndroidX. Chromium-side integration tests offer more visibility to these developers (so, they know if they break our code). Another advantage to integration tests is that they run on CQ (presubmit) where CTS runs on a separate bot (postsubmit).
Blocking: 902658
Labels: Hotlist-KnownIssue
Status: Started (was: Assigned)
Labels: Proj-Servicification
(Bulk edit to add component)

Comment 9 by laisminchillo@chromium.org, Jan 16 (6 days ago)

Status: Fixed (was: Started)

Sign in to add a comment