<div dir="ltr"><br><div>I've put in place a REUSE_BROWSER option for some of the tests in VisualEditor, that Nik put in place for the CirrusSearch tests, that I guess was first mentioned by Alister Scott in his blog, they all look pretty similar. Take a look at line 126 or so of <a href="https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/62800f99ec350c345bdff86af4d2ed353d79270f/modules%2Fve-mw%2Ftest%2Fbrowser%2Ffeatures%2Fsupport%2Fenv.rb">https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/62800f99ec350c345bdff86af4d2ed353d79270f/modules%2Fve-mw%2Ftest%2Fbrowser%2Ffeatures%2Fsupport%2Fenv.rb</a> </div>
<div><br></div><div>-Chris </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 10, 2013 at 3:20 PM, Tomislav Plavcic <span dir="ltr"><<a href="mailto:tplavcic@gmail.com" target="_blank">tplavcic@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did see the KEEP_BROWSER_OPEN variable in the readme file but I<br>
thought that the browser then stays open after one scenario (which it<br>
does) and runs the next scenario in the same window (which it<br>
doesn't). I tried it now and see that it opens different browser<br>
instances for each scenario and all stay open...<br>
<br>
Thank you Zeljko and Chris!<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Oct 10, 2013 at 3:48 PM, Chris McMahon <<a href="mailto:cmcmahon@wikimedia.org">cmcmahon@wikimedia.org</a>> wrote:<br>
><br>
><br>
><br>
> On Thu, Oct 10, 2013 at 3:18 AM, Željko Filipin <<a href="mailto:zfilipin@wikimedia.org">zfilipin@wikimedia.org</a>><br>
> wrote:<br>
>><br>
>> Hi Tomislav,<br>
>> On Tue, Oct 8, 2013 at 1:05 AM, Tomislav Plavcic <<a href="mailto:tplavcic@gmail.com">tplavcic@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> #2<br>
>>><br>
>>> When a test fails maybe it would be good that it prints a url visited<br>
>>> so I can check a tested page manually -<br>
><br>
><br>
> If you just need it for temporary debugging, you can always add a 'puts'<br>
> line inside the steps file at the appropriate place:<br>
><br>
> puts @browser.url<br>
><br>
> will print the current url to the terminal.<br>
><br>
> -Chris<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> QA mailing list<br>
> <a href="mailto:QA@lists.wikimedia.org">QA@lists.wikimedia.org</a><br>
> <a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
><br>
<br>
<br>
<br>
--<br>
Tomislav Plavcic<br>
Theoretically, if I cut costs enough we'll be profitable without<br>
selling any products... Dilbert<br>
<br>
_______________________________________________<br>
QA mailing list<br>
<a href="mailto:QA@lists.wikimedia.org">QA@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
</div></div></blockquote></div><br></div>