<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maja Frydrychowicz</title>
    <description/>
    <link>https://speakerdeck.com/mjzffr</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/mjzffr.rss"/>
    <lastBuildDate>2017-06-25 18:08:37 -0400</lastBuildDate>
    <item>
      <title>Remotely Control this Browser: WebDriver and the Path to an Interoperable Web</title>
      <description>Notes: http://www.erranderr.com/blog/presentations/webdriver_osb2017

Session: http://opensourcebridge.org/sessions/1997

You can write simple code to automate your browser and simulate user interaction. Moreover, thanks to the people behind a W3C standard called WebDriver, some day soon you can expect to write just one script in your favourite programming language to automate all major browsers in the same way.

The WebDriver protocol can be used for testing web applications, reporting and reproducing web-compatibility bugs, gathering browser data and whatever else you can think to do with browser automation. It’s closely tied to Selenium, a well-known, open-source browser automation tool.

This talk explains why WebDriver is becoming a standard and how you can work on it with us. Using Firefox as our example, we explore why browser automation is tricky to get right. How do WebDriver commands get to Firefox? How does the browser figure out the correct response? What does “correct” even mean here?

Today, all major browsers work with WebDriver to varying degrees. As part of our mission to make the web interoperable, Mozilla is leading the way to fully implementing the WebDriver standard and we welcome your contributions.</description>
      <media:content url="https://files.speakerdeck.com/presentations/3dbe6b3fd48647f7947d8522513a602e/preview_slide_0.jpg?8210158" type="image/jpeg" medium="image"/>
      <content:encoded>Notes: http://www.erranderr.com/blog/presentations/webdriver_osb2017

Session: http://opensourcebridge.org/sessions/1997

You can write simple code to automate your browser and simulate user interaction. Moreover, thanks to the people behind a W3C standard called WebDriver, some day soon you can expect to write just one script in your favourite programming language to automate all major browsers in the same way.

The WebDriver protocol can be used for testing web applications, reporting and reproducing web-compatibility bugs, gathering browser data and whatever else you can think to do with browser automation. It’s closely tied to Selenium, a well-known, open-source browser automation tool.

This talk explains why WebDriver is becoming a standard and how you can work on it with us. Using Firefox as our example, we explore why browser automation is tricky to get right. How do WebDriver commands get to Firefox? How does the browser figure out the correct response? What does “correct” even mean here?

Today, all major browsers work with WebDriver to varying degrees. As part of our mission to make the web interoperable, Mozilla is leading the way to fully implementing the WebDriver standard and we welcome your contributions.</content:encoded>
      <pubDate>Wed, 21 Jun 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/mjzffr/remotely-control-this-browser-webdriver-and-the-path-to-an-interoperable-web</link>
      <guid>https://speakerdeck.com/mjzffr/remotely-control-this-browser-webdriver-and-the-path-to-an-interoperable-web</guid>
    </item>
  </channel>
</rss>
