tenfourfox/testing/web-platform/tests/webdriver
Cameron Kaiser c9b2922b70 hello FPR
2017-04-19 00:56:45 -07:00
..
command_contexts hello FPR 2017-04-19 00:56:45 -07:00
cookie hello FPR 2017-04-19 00:56:45 -07:00
ecmascript hello FPR 2017-04-19 00:56:45 -07:00
element_location hello FPR 2017-04-19 00:56:45 -07:00
element_state hello FPR 2017-04-19 00:56:45 -07:00
javascript hello FPR 2017-04-19 00:56:45 -07:00
modal hello FPR 2017-04-19 00:56:45 -07:00
navigation hello FPR 2017-04-19 00:56:45 -07:00
screenshot hello FPR 2017-04-19 00:56:45 -07:00
timeouts hello FPR 2017-04-19 00:56:45 -07:00
user_input hello FPR 2017-04-19 00:56:45 -07:00
windows hello FPR 2017-04-19 00:56:45 -07:00
base_test.py hello FPR 2017-04-19 00:56:45 -07:00
network.py hello FPR 2017-04-19 00:56:45 -07:00
README.md hello FPR 2017-04-19 00:56:45 -07:00
runtests_p0.py hello FPR 2017-04-19 00:56:45 -07:00
runtests.py hello FPR 2017-04-19 00:56:45 -07:00
webdriver.cfg hello FPR 2017-04-19 00:56:45 -07:00

W3C Browser Automation Specification Tests

This repository defines a set of conformance tests for the W3C web browser automation specification known as WebDriver. The purpose is for the different driver implementations to be tested to determine whether they meet the recognized standard.

How to run the tests

  1. Go to the WebDriver tests: cd _WEBDRIVER_TEST_ROOT_
  2. Run the tests: python runtests.py
  3. Run the test against a different config specified in webdriver.cfg: WD_BROWSER=chrome python runtests.py

To be run a specific test file you can just run python test_file.py

Similarly you can specify a different browser to run against if in webdriver.cfg: WD_BROWSER=chrome python ecmascript/ecmascript_test.py

Note: that you will need likely need to start the driver's server before running.

Updating configuration

The webdriver.cfg file holds any configuration that the tests might require. Change the value of browser to your needs. This will then be picked up by WebDriverBaseTest when tests are run.

Be sure not to commit your webdriver.cfg changes when your create or modify tests.

How to write tests

  1. Create a test file per section from the specification.
  2. For each test there needs to be one or more corresponding HTML files that will be used for testing. HTML files are not to be reused between tests. HTML files and other support files should be stored in a folder named 'res'.
  3. Test name should explain the intention of the test e.g. def test_navigate_and_return_title(self):