| .. | ||
| command_contexts | ||
| cookie | ||
| ecmascript | ||
| element_location | ||
| element_state | ||
| javascript | ||
| modal | ||
| navigation | ||
| screenshot | ||
| timeouts | ||
| user_input | ||
| windows | ||
| base_test.py | ||
| network.py | ||
| README.md | ||
| runtests.py | ||
| runtests_p0.py | ||
| webdriver.cfg | ||
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
- Go to the WebDriver tests:
cd _WEBDRIVER_TEST_ROOT_ - Run the tests:
python runtests.py - 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
- Create a test file per section from the specification.
- 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'.
- Test name should explain the intention of the test e.g.
def test_navigate_and_return_title(self):