Autotester

Autotester is Chrome extension that allows to develop and run automation tests right in browser.
Tests are written in Javascript and can be executed over another tab of the same Chrome or any remote browser.

Tested in:

Demo
Features
Project status
Installation
Getting started
Usage
Roadmap
Contribution
FAQ
Links
License

Demo

Features

Zero setup
The setup is just drag-n-drop extension in chrome. No other stuff like Selenium, Node.js or Chromedriver is needed.
Convenient development
Developing tests right in browser has some advantages. You can edit tests in first tab and check results in second. You can easily run particular test to debug. You can keep tab open after tests to inspect with devtools.
Selenium compatible syntax
Tests syntax is compatible with Selenium Javascript API so it can be executed ether in nodejs and visa-versa (except custom commands).
Custom commands
Because tests are executed via extension all of rich chrome extensions API are available. You can define custom commands to work with cookies, downloads, tabs, history etc and use it in your tests.
Capture network requests
Capturing network requests is working out of box. You can capture page loads, resources (img, script, etc), xhr/fetch requests and new tabs. No proxy needed. Please see example.
Load tests from anywhere
Tests can be stored right in browser, local directory or loaded from any local/remote http server (for example GitHub).
Run tests on remote servers
Besides running tests in the same chrome instance it is possible to route commands to any selenium server. It can be localhost, Sauce Labs, BrowserStack, etc.
Test other chrome extensions
With Autotester it is possible to attach to other extensions background pages for testing. Please see example.

Project status

Autotester is under active development now. Not all webdriver commands are supported. Yet. And there can be bugs. But feel free to try it and share your feedback or ideas in issues - help us to make it better!

Installation

Download and unpack latest autotester.zip
Drag-n-drop unpacked autotester directory on chrome://extensions page

Getting started

Click extension button A in browser panel to open Autotester app. Select google_search in dropdown and press Run to execute test. Look at the report. Next, you can change test code or create new file and re-run again.

Usage

Autotester supports Selenium Javascript API for writing tests. Have a look on Autotester self tests.
Also there are some pre-defined globals available in tests for conveniency:

Driver
By
until
Key
webdriver
console
require

More detailed tutorial is coming..

How does Autotester work?

When executing tests in the another tab of the same browser Autotester is utilizing Chrome Debugging Protocol available via chrome.debugger.* extensions API. It intercepts http requests going from Selenium Javascript package to W3C Webdriver endpoints and loops them back to browser.
When executing tests over remote browser Autotester does not intercept http requests letting them reach remote Selenium Server and waits for the results.

Roadmap

There are many directions to grow. The current plan is following:

implement rest of webdriver commands
improve docs and tutorials
add capabilities manager to visually configure targets
integrate with other webdriver implementations (webdriverio, nightwatchjs, codeceptJS, spectron)
integrate with Appium
run tests in parallel
improve tests editor: autocomplete, breakpoints, etc
create tests automatically via recording user actions
...your idea?

Contribution

If you have an idea how to fix bug or implement new feature - you are welcome to contribute.
Please see CONTRIBUTING.md. Thanks for your support!

FAQ

What if I get error "Unsupported route command"?

This error means that some Webdriver command is not implemented in Autotester yet. The workaround sometimes can be using `driver.executeScript` to achive the goal directly. For example, if `driver.getTitle()` is not implemented, you can retrieve title as: driver.executeScript(() => document.title); Also please search issues for the same unsupported route and vote or create new one to let us know which commands you need most of all.

Where to store tests?

1. You can create as many tests as you like and store them right in browser as snippets. This is the easiest way but less reliable: if you occasionally remove extension tests will be lost. 2. For more serious things it is recommended to serve tests from local or remote http server and keep them under version control. 3. The third option is to load tests from local directory without http server. For that you should create tests inside `/tests` directory of unpacked extension.

License

MIT @ Vitaliy Potapov

vitalets / autotester

readme