ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Guillem Jover	bcab88a09d	TT#39401 Use List::Util in perl core instead of List::MoreUtils We can replace the apply usage with map plus a returning s///. This also fixes a hidden bug with the liblist-moreutils-perl dependency missing from debian/control, being indirectly pulled by some other dependency, while an implementation detail. Change-Id: Ibfc7b362ad77c4b202d93cf71774c40623503f14	7 years ago
Michael Prokop	1cd3fb497b	TT#17853 TT#21767 Use git version of Selenium::Remote::Driver Selenium::Remote::Driver v1.20 is the latest upstream release and is missing some patches/PRs that we need for selenium tests of ngcp-panel. Packaging the git version properly in the Debian way is hard because of the way upsteam handles releases with separate branches (one of them even being out-of-date, sigh). So instead let's use a tarball from their latest git version until we see a v.1.21 release. Symlinking the geckodriver binary to /usr/bin/geckodriver addresses: \| Unable to find the geckodriver binary in your $PATH. at /home/selenium/Selenium-Remote-Driver/lib/Selenium/CanStartBinary/FindBinary.pm line 66. Change-Id: I8ddf3c76a008ce5b0aa67b62154a9614f90cb659	8 years ago
Michael Prokop	2b9b5f8b61	TT#17853 selenium tests: update to geckodriver v0.18.0 Change-Id: I545f160d5dc1a0d60cd2e9dc4ad946989efd4f8c	8 years ago
Michael Prokop	67f2e54be6	TT#17853 Use Selenium::Remote::Driver with further patches to address bugs/incompatibilities This package update includes further patches to address Selenium test failures with geckodriver/Firefox: * move_to: `4d0b8e7255` * timeouts: `2c55f3dcb9` Change-Id: I587f32230ce7cc8d912e052a93fb7d31fd7c90c1	8 years ago
Michael Prokop	2b021efb56	TT#17853 Fix selenium related toolchain, replacing selenium with geckodriver An unintended docker image rebuild of ngcp-panel-tests-selenium-jessie resulted in failures with our selenium tests. A series of problems started: 1) Updating the Selenium version resulted in an error message by Selenium, requesting the geckodriver binary (https://github.com/mozilla/geckodriver - being a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers). So Selenium versions >=3 depend on geckodriver. 2) Recent versions of Selenium also depend on Java >=8, available only via backports for jessie. Since we avoid usage of backports as much as possible and we'd have to upgrade once anyway we decided to base our fresh docker image on stretch. 3) We have to backport Selenium::Remote::Driver (Debian package libselenium-remote-driver-perl) for stretch (since it's not available in Debian, even though there's an ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839569). It has a bug which prevents its usage for us: https://github.com/gempesaw/Selenium-Remote-Driver/issues/319 -> We fixed the problem via our own backport and submitted a PR towards upstream: https://github.com/gempesaw/Selenium-Remote-Driver/pull/321 4) Firefox from Debian/stretch (firefox-esr 52.2.0esr-1~deb9u1) fails with geckodriver e.g. in click events, the current Firefox version 54 works fine though. So instead install only the relevant runtime packages from Debian and use the Firefox version v54 from upstream. Resulting changes: * switch from Debian/jessie to Debian/stretch * no longer use selenium at all but only geckodriver instead (recent versions of selenium depend on geckodriver anyway) * do all package/file changes in /home/selenium/ (to clearly see what's from us/docker and what are actual temporary files) * testrunner related changes: - invoke vncserver with `-localhost no` option to accept VNC connections not only from localhost only - adjust vncserver process name for Xvnc4->Xtigervnc switch - start geckodriver instead of selenium * package related changes: - backported libtest-pretty-perl (v0.32) - backported libselenium-remote-driver-perl (v1.20) - add curl to package list since it's handy for debugging test failures, like e.g. `curl -X POST localhost:4444/session --data {}` - add procps to have pkill binary available inside testrunner - openjdk/java is no longer needed since we don't depend on selenium anymore - vnc4server is now a transitional package for tigervnc-standalone-server, so directly depend on it Change-Id: I607ffd4fce80f9e84b76c3c7a19824819ac4503c	8 years ago
Victor Seva	8994522f91	TT#17502 docker: fix relative path from new context * update Dockerfile documentation Change-Id: Ib1c2491118d1fc02cae0ed198fefe06ccd954660	8 years ago
Victor Seva	c6b51a136c	MT#17293 Switch Dockerfile files to use a sipwise-jessie image This way we get a Debian Jessie system with Sipwise mirrors and need not do any additional setup. Change-Id: I89e9acd846132508e135f7443482c0371c80d2b2	9 years ago
Michael Prokop	9b95f357d8	MT#8075 Refresh Dockerfile + set DOCKER_NAME for *-source-tests With the update to docker distribution v2.2.1 we need to push new images Change-Id: Ic9e10d4827fe836beeba7480bf2c17002400798d	9 years ago
Michael Prokop	a236b39bef	MT#15071 Jenkins<->docker integration support The jenkins_docker_run script is invoked from Jenkins when running the docker image. The testrunner script now takes two additional arguments to support sharing test results via another docker volume and to control output format ("pretty" as default but junit for usage on Jenkins). While at it fix some quoting issue identified by shellcheck. Change-Id: Ided716e0e0ca23751b0ee2961f3e301acb80128d	10 years ago
Gerhard Jungwirth	7f2076e8ab	MT#15071 some docker conveniences Change-Id: I901a6012ad00e5f318ac6eda5c107e5c4d1241b7	10 years ago
Michael Prokop	b17bc4da82	MT#14585 Docker setup for selenium tests This provides a setup to run ngcp-panel tests against selenium-server using docker. It's based on Debian/jessie and assumes are reachable NGCP system for running the tests against (e.g. via `vagrant up ce-trunk`). For usage instructions refer to the Dockerfile. NOTE: replacing 'jessie' with 'wheezy' in the Dockerfile provides a setup based on Debian/wheezy. Change-Id: I79ca4d44c3a7c454f99148889d4b0d075a79e82b	10 years ago

11 Commits (mr6.5)