drive.quit is causing build breaks [1] so there is no point using it.
other option is to wrap it with try-catch.
https://wso2.org/jenkins/job/product-ues/601/
On Mon, Dec 14, 2015 at 9:46 AM, Rajeenthini Satkunam
wrote:
> Adding [ wso2Dev,Krishantha,Nuwan,Irham ]
>
> Hi nipuna,
>
> IMHO driver.quit() will make sure that we properly terminates the test
> class and quit all the driver instance and running the the next test class
> with a new instance of driver.
>
> On Fri, Dec 11, 2015 at 5:30 PM, Nipuna Chandradasa
> wrote:
>
>> Hi rajeenthini
>>
>> If this is the case why don't we close the opened extra browser windows
>> within each test. If we do this we will end up having one browser window at
>> the end of the test case
>>
>> I will look in to this as I refactoring the braking tests.
>>
>> Regards
>> On 11 Dec 2015 5:13 p.m., "Rajeenthini Satkunam"
>> wrote:
>>
>>> Hi all,
>>>
>>> I have search through the web above $subject.The way I understand is we
>>> can refine our test code since we are handle multiple browser window or
>>> single browser window.If we are handle one and only one window we don't
>>> need to explicitly do driver.quit() , But In case of multiple windows we
>>> should use driver.quit() because driver.close will close only the window it
>>> has focused.
>>>
>>> Please find references.
>>> [1] - http://www.testingdiaries.com/driver-close-and-driver-quit/
>>> [2] - https://www.youtube.com/watch?v=3vxBBlvxcKE
>>>
>>> Correct me if I am wrong.
>>>
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823> *
>>>
>>>
>
>
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823> *
>
>
--
With regards,
*Manu*ranga Perera.
phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
