New issue
Advanced search Search tips

Issue 894495 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Need end-to-end test coverage for NavigableContents embedding

Project Member Reported by roc...@chromium.org, Oct 11

Issue description

We currently have no test coverage verifying that an embedded content view is actually displayed in the UI when it's supposed to be. There are three cases that need coverage:

a) The client and the service are running in the same (browser) process
b) [chrome os only] The client is running in the ws process
c) [chrome os only] The client is running in neither the browser nor the ws process

Recently case (c) was broken without being caught by tests.
 
Also quoth sky@ for some insight into possible testing strategy for the Chrome OS cases:

"There is a testing interface (WindowServerTest) that checks if something has painted. Ideally we would write a test using that. It may not be rich enough for your particular case, but it would be worth expanding it to ensure it can cover [these cases]."
Owner: rockot@google.com

Sign in to add a comment