This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
Releases: zalando/zalenium
Releases · zalando/zalenium
2.53.1n
3.0.1b
2.53.1m
- TestingBot integrated to Zalenium
- Adding Docker Compose examples
3.0.1a
3.0.0a
2.53.1l
- Adding Sauce Connect and BrowserStackLocal to enable local testing when using these cloud testing platforms. You just need to add
--startTunnel true
when using Sauce Labs and/or BrowserStack. - Fixing #42 and adding tests to avoid breaking it again.
- Preparing for Selenium 3 migration
- Removing an url dependency on Selenium when shutting down the node
/selenium-server/driver/?cmd=shutDownSeleniumServer
was removed in Selenium 3, now usingdocker stop
.
2.53.1k
-
BrowserStack has been integrated, it works in a similar way as Sauce Labs. Example command:
export BROWSER_STACK_USER=<your BrowserStack username> export BROWSER_STACK_KEY=<your BrowserStack access key> docker run --rm -ti --name zalenium -p 4444:4444 -p 5555:5555 \ -e SAUCE_USERNAME -e SAUCE_ACCESS_KEY \ -e BROWSER_STACK_USER -e BROWSER_STACK_KEY \ -v /tmp/videos:/home/seluser/videos \ -v /var/run/docker.sock:/var/run/docker.sock \ dosel/zalenium start --browserStackEnabled true
-
Now the default value for
--browserStackEnabled
and--sauceLabsEnabled
is false, since the Google Analytics data shows that not so many people use this option.
2.53.1j
New features:
- It is possible to use the capability
name
for the recorded video file. The output will look like: testName_browser_containerPort_timeStamp.mkv - You can now use "latest" for browser version when the test will be executed in Sauce Labs.
Bug fixes:
- Specific browser versions are now forwarded to Sauce Labs as well.
2.53.1i
2.53.1h
- Node shutdown was improved, it is done when the client sends a STOP_SESSION event, which makes life easier for frameworks/utilities that take screenshots for test failures.
- Removing the hardcoded "localhost" in the VNC live preview. Now you can run Zalenium in a different machine and check the tests running from your own machine
- Just change
localhost
in http://localhost:4444/grid/admin/live to the machine's name or IP where Zalenium is running.
- Just change