Properly initialize WebStates in unit tests
Those tests trigger code path that access the toolbar if there is an active WebState in the WebStateList. This requires that the WebState returns non-null BrowserState and NavigationManager so set the corresponding property on the TestWebState. Bug: none Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ic950a706b31ac153cdfb71b510681c09886c3da0 Reviewed-on: https://chromium-review.googlesource.com/1106176Reviewed-by:Gauthier Ambard <gambard@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#569228}
Showing
Please register or sign in to comment