Webdriver-test-tools

Added optional parameter `wait_timeout` to the custom assertion methods in `WebDriverTestCase`. Also reorganized code in `webdriver.support` subpackage in a way that makes more sense and removes circular imports.

Details

Test Cases

- Added optional parameter `wait_timeout` to `WebDriverTestCase` assertion methods that wrap expected condition tests, allowing users to override the default time of 10 seconds for conditions that may take longer to occur

Expected Conditions

- Added expected condition classes for elements existing/not existing and enabled/disabled states

WebDriver Test Module

- Moved `element_exists()` and `is_scrolled_into_view()` out of `test` module. They're now "private" methods in the `expected_conditions` module
- Added expected condition test functions `existence_change_test()` and `enabled_state_change_test()` that use the new expected condition classes

Page Object Prototypes

- `ModalObject` and `NavObject` no longer use `test.element_exists()` and instead wrap calls to `self.find_element()` in a `try`/`except` that catches `NoSuchElementException` and uses that instead

wtt init` now creates submodule `data.py` instead of an entire `data` subpackage.

Reorganized internal modules related to the command line interface

init command

`wtt init` now takes optional arguments to skip prompts.


wtt init [<package_name>] [<"Project Title">] [--no-gitignore] [--no-readme]


If one or more positional arguments is specified, `wtt init` will attempt to skip input prompts and use values from command line arguments and default settings to generate a new test project.

new command

`<test_package> new` command now has prompts to walk through new file creation if `<type>`, `<module_name>`, or `<ClassName>` arguments are not provided.

Several updates to the command line interface for the framework and projects.

Command Syntax Changes

Framework

`wtt init` - Initialize a test project in the current directory

Test Projects

`<test_package> run` - Run the test suite
`<test_package> list` - Print a list of available tests and exit

**Note:** If no command is specified, will execute the `run` command by default, so old syntax for running tests is still valid.


New Commands

New test/page modules can be now generated using the `<test_package> new` command.

**Command Usage:**


python -m <test_package> new <type> <module_name> <ClassName> [-d <description>] [-f]


Where:

- `<type>` - the type of file to create (`test` or `page`)
- `<module_name>` - the name of the module to create
- `<ClassName>` - the name of the initial class created in the module
- `[-d <description>]` - optional description to use in the docstring for the new class
- `[-f]` - force overwrite if a module exists with the same name

New test projects generated with `wtt init` will no longer include the `<test_package>/templates/` directory as test/page module creation is now handled via the command line

Added `wtt` as a command line alias for `webdriver_test_tools`.