Contribution is really appreciated. Please follow the instructions below.
As Autotester is testing tool it can test itself.
Exactly for that there are two instances of Autotester loaded in browser during development:
- from
dist/unpacked-dev
- this is instance that runs tests - from
dist/unpacked
- this is instance to be tested
Both instances are updated simultaneously when code changes.
-
Fork the repo and clone it:
git clone https://github.com/<your_name>/autotester.git
-
Install npm dependencies:
cd autotester npm i
-
Install selenium standalone server:
selenium-standalone install
-
Run dev watcher (in separate terminal window):
npm run dev
-
Run local selenium hub (in separate terminal window):
npm run hub
-
Launch chrome and open
chrome://extensions
page -
Enable developer mode checkbox
-
Load 2 unpacked extensions from
dist/unpacked-dev
anddist/unpacked
-
Enable chrome flag to allow debug of extensions:
chrome://flags/#extensions-on-chrome-urls
.
Relaunch Chrome. Don't care about warning: You are using an unsupported command-line flag -
You are done! Now you can make changes in files and reload extensions to see the result