Open GoogleCodeExporter opened 8 years ago
Original comment by phil.boo...@gtempaccount.com
on 21 Sep 2009 at 3:09
Unstarting this issue, as spending time automating the test suite for Safari
has been
deemed less crucial than getting the tests to pass in Safari at the current
time.
Fwiw, Safari can basically use the same buildbot target as Firefox does
currently.
Just a couple more things need parameterising (path to the browser obviously,
maybe a
couple of other bits too). The thing that stopped me being able to commit right
away
was Selenium's close=true parameter not working out of the box on Safari, not
sure
why at this point. However, one thing I did spot during my hunt was that we're
using
quite an old version of Selenium (0.8 vs. 1.0 at time of writing), so upgrading
may
be worth investigating. Also, the newer version looks to have much richer
remote
testing tools (see: Remote Control and Grid).
Original comment by phil.boo...@gtempaccount.com
on 22 Sep 2009 at 9:22
Original comment by phil.boo...@gtempaccount.com
on 22 Sep 2009 at 1:51
Original issue reported on code.google.com by
phil.boo...@gtempaccount.com
on 21 Sep 2009 at 3:08