Yst

Integration test scenarios executor - PoC ;)

What am I looking at? :o

Under the hood we're spawning a browser (PhantomJS 2.1+) in "WebDriver" mode. This way we take full control over a headless browser, to perform site integration testing.

Currently the PoC code logins to Silk backend playground and performs some read only checks (existence of text patterns or site elements).

Requirements

0. macOS 10.11+ or Linux
1. Elixir 1.7+
2. Erlang OTP 19+
3. tmux (phantomjs is spawned under tmux session by default)

How to run

• Yst reads environment variables from .env file located in this repository.

YS_URL    # Default url of tested site
YS_LOGIN  # Login used to get to the Silk panel
YS_PASS   # Password used to get to the Silk panel

• Edit your .env file and put missing value of YS_PASS there.

• Run production escript (:prod env):

bin/run

• Run under iex REPL (:dev env:

bin/console

then just:

Yst.run

to start main supervisor and launch checks.

Example results (YS_PASS is NOT set):

Example results (YS_PASS is set):

• Currently tests do internal testing. To test scenarios, go back to Yst.run part. (For details about internal tests look here: yst_test.exs):

bin/test

License

BSD/MIT