Re: Controlling the browser environment/settings

Btw, we don't use the remote debugger anymore for Marionette, and it can 
operate without a network; it just needs to be able to have a socket 
open on the device. We do similar testing to this on Firefox OS devices, 
so I don't see this as difficult to implement in the browser.
On 2014-03-27, 11:33 AM, David Burns wrote:
> I have never tried it but I fully expect WebDriver to get a little 
> upset by this (note I havent tried this). With WebDriver, from the OSS 
> world and from Marionette, we expect there to be a network so that we 
> can speak to the browser (with FirefoxDriver we need to communicate 
> with httpd.js and with Marionette we go in via the remote debugger).
>
> David
>
> On 27/03/2014 12:24, James Graham wrote:
>> For testing certain kinds of things it is very useful to be able to 
>> put the browser into unusual modes which cannot be activated via 
>> normal web apis. The particular example that I have in mind is 
>> offline mode; being able to simulate the browser disconnecting and 
>> reconnecting to the network is very useful for testing technologies 
>> such as AppCache / Service Worker and web applications using these 
>> features to provide offline support.
>>
>> Since this is something that can't be provided as a DOM API (except 
>> in some hypothetical debug mode) and that is very useful both for 
>> testing browsers and for testing web applications, it seems like 
>> WebDriver would be the natural home for such a feature. Is it already 
>> supported in some way that I missed? If not is it something that 
>> could be added?
>>
>
>

-- 
Malini Das

Received on Tuesday, 1 April 2014 07:18:34 UTC