Skip to content

Latest commit

 

History

History
48 lines (38 loc) · 1.4 KB

CONTRIBUTING.md

File metadata and controls

48 lines (38 loc) · 1.4 KB

Contributing

Contribution is really appreciated. Please follow the instructions below.

Self testing

As Autotester is testing tool it can test itself.
Exactly for that there are two instances of Autotester loaded in browser during development:

  1. from dist/unpacked-dev - this is instance that runs tests
  2. from dist/unpacked - this is instance to be tested

Both instances are updated simultaneously when code changes.

Development setup

  1. Install git and node.js >= 6

  2. Fork the repo and clone it:

    git clone https://github.com/<your_name>/autotester.git
  3. Install npm dependencies:

    cd autotester
    npm i
  4. Install selenium standalone server:

    selenium-standalone install
  5. Run dev watcher (in separate terminal window):

    npm run dev
  6. Run local selenium hub (in separate terminal window):

    npm run hub
  7. Launch chrome and open chrome://extensions page

  8. Enable developer mode checkbox

  9. Load 2 unpacked extensions from dist/unpacked-dev and dist/unpacked

  10. 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

  11. You are done! Now you can make changes in files and reload extensions to see the result