Async::WebDriver
Provides a client implementation of the W3C WebDriver specification with support for Chrome and Firefox.
Motivation
In the past, I've used selenium-webdriver for testing web applications. However, I found it to be slow. I wanted to improve the performance of my tests, so I decided to write a new implementation from scratch. The W3C WebDriver specification is quite simple, so it wasn't too difficult to implement, and I was able to get a significant performance improvement, between 2x-10x depending on the usage. Specifically, most test suites can take advantage of pre-warmed sessions, which can minimise the overhead of each test running in a new session. Additionally, I'd like to explore reusing sessions between tests, which could provide even more performance improvements.
In addition, building on top of async allows us to take advantage of async-http and run the web server in the same reactor as the test itself, which can provide a performance improvement over capybara which usually needs to start a separate server process. This also makes it possible to share a single database transaction between the client and server, which can significantly reduce the overhead of "cleaning" the database after each test, and improve the opportunity for parallelisation.
Usage
Please browse the source code index or refer to the guides below.
Getting Started
This guide explains how to use async-webdriver for controlling a browser.
GitHub Actions Integrations
This guide explains how to use async-webdriver with GitHub Actions.
Sus Integration
This guide will show you how to integrate async-webdriver with the sus test framework.
See Also
- sus-fixtures-async-webdriver - Standard fixtures for testing web applications with
async-webdriver.
Contributing
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
Developer Certificate of Origin
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
Community Guidelines
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.