Stop using bazel to build and test library. (#147)

* Stop using bazel to build and test library.

- Refactor tests to use interface libraries.
- Re-enable html tests.

* Update travis.yml.

* Fix travis.sh script.

* Add travis-setup script.

* Set script to be executable.

* Disable most html tests (they are not working).
81 files changed
tree: 8724481a19fbc0b51d9b745b7a2336359469dda4
  1. lib/
  2. test/
  3. tool/
  4. .gitignore
  5. .travis.yml
  6. analysis_options.yaml
  7. AUTHORS
  8. CHANGELOG.md
  9. CONTRIBUTING.md
  10. LICENSE
  11. pubspec.yaml
  12. README.md
README.md

webdriver

Build Status pub package

Provides WebDriver bindings for Dart. These use the WebDriver JSON interface, and as such, require the use of the WebDriver remote server.

Installing

  1. Depend on it

    Add this to your package's pubspec.yaml file:

    dependencies:
      webdriver: any
    

    If your package is an application package you should use any as the version constraint.

  2. Install it

    If you're using the Dart Editor, choose:

    Menu > Tools > Pub Install
    

    Or if you want to install from the command line, run:

    $ pub install
    
  3. Import it

    Now in your Dart code, you can use:

    import 'package:webdriver/io.dart';
    
    WebDriver driver = createDriver(...);
    

Testing

You can run the tests either with bazel (only supported on Linux).


bazel test ...