Difference between revisions of "Testing/Test Framework TF/WebDriver"

From W3C Wiki
Jump to: navigation, search
m (Created page with "== Proposed architecture == # Device visits the test server. If it is identified as being WebDriver-compatible (how do you do this identification still tba), the user is asked t…")
 
m (Proposed architecture)
Line 1: Line 1:
 
== Proposed architecture ==
 
== Proposed architecture ==
  
# Device visits the test server. If it is identified as being WebDriver-compatible (how do you do this identification still tba), the user is asked to enable WebDriver (how you do this seems device specific and potentially painful) and provide the remote's IP address via an input field.
+
# Device visits the test server. If it is identified as being WebDriver-compatible (how do you do this identification still tba), the user is asked to enable WebDriver (how you do this seems device specific and potentially painful) and provide the remote's IP address (via an form input field?).
 
# The test server connect to the device using the provided IP address.
 
# The test server connect to the device using the provided IP address.
 
# The test server instructs the device to navigate to each test page it needs to run.
 
# The test server instructs the device to navigate to each test page it needs to run.

Revision as of 07:44, 15 March 2013

Proposed architecture

  1. Device visits the test server. If it is identified as being WebDriver-compatible (how do you do this identification still tba), the user is asked to enable WebDriver (how you do this seems device specific and potentially painful) and provide the remote's IP address (via an form input field?).
  2. The test server connect to the device using the provided IP address.
  3. The test server instructs the device to navigate to each test page it needs to run.
    • if the test page uses testharness.js, the results are sent back to the test server via the JSON protocol.
    • if the test page is a ref test, a screenshot is sent back to the test server and compared to the reference image there.
  4. Once the tests are all run, the test server compiles the results and navigates the browser to the results page.

Current native implementations

Mozilla