ppodgorsek/docker-robot-framework

Robot Framework in Docker

docker-robot-framework's Issues

Update Chromium to version 60.0

60.0.3112.90-1.fc26 is the latest version available.

Update Firefox to version 59.0

The version has to be updated in the Dockerfile and the README file.

Update the Gecko driver to the latest version

The latest version is 0.19.1
See https://github.com/mozilla/geckodriver/releases

Update the base image to Fedora 28

SimpleTest with chrome failed ?

Hi,

I'm testing your docker image with a simple ROBOT test like Simple.robot.txt

But i get error: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally

Robot debug do not help very much:
debug.txt

And inside image chrome log file, i get a lot of:
DevTools Request: 127.0.0.1:12585/json/version. DevTools request failed

Can you help me or send me a simple working robot test sample ?

thanks !

Update Robot Framework to version 3.0.4

Release notes can be found on their GitHub project.

Spelling mistakes in README

The "Testing this project" section of the README contains several mistakes which have to be fixed.

Chromedriver has the wrong version?

Hey Paul, thanks for this docker, I'm trying to install it in a Bitbucket Pipeline but it always fails when it tries to "Open Browser" in my tests. I have a feeling it's the chromedriver version you're using..? I'm looking all over the internet and it says chromedriver is on version '2.35' and you're using '63.0' just like chromium, could it be a typo?

Upgrade Firefox and Chrome to their latest versions

A new version of Firefox is available, it should be used in the image.

Upgrade Robot Framework to version 3.0.2

The latest version should be used.

Ignore IntelliJ files

The following files must be ignored by git:

• .idea/
• *.iml

Provide usage example

The README should explain how the provided test case can be run.

Update Chromium to version 66.0

Update Chromium to latest version

The latest version is 61.0.3163.100-1.fc26

Allow to define the screen resolution as an environment variable

The screen resolution is currently forced at 1920x1080x24 when Xvfb starts.
It should be possible to override it via an environment variable.

When building image '/opt/robotframework/drivers/': No such file or directory

when I try to start docker build with :
sudo docker build -t selenium-ci .

it failed with :
mkdir: cannot create directory '/opt/robotframework/drivers/': No such file or directory

maybe pip should install robot framework in /opt/robotframework and it's not the case anymore ?

Error: Suite 'Tests' contains no tests.

Hi,

When I try to run a test I get [Error] Suite 'Tests' contains no tests.
I've downloaded sources from GitHub and I'm in "C:\DockerTests\docker-robot-framework-master" folder and I run following command:
docker run
-v ${PWD}/reports:/opt/robotframework/reports:Z
-v ${PWD}/test:/opt/robotframework/tests:Z
-e BROWSER=chrome
ppodgorsek/robot-framework:latest

Any hint?

BR
Jakub

Update versions in README

The versions of Firefox and Chrome are outdated in the README file, they should be updated.

Make dependency resolution more flexible

Currently, all packages which are installed have a specific version. This makes the build break often, as those versions quickly become outdated and replaced by new releases.
The installed packages should therefore be declared in a more flexible manner.

Upgrade SeleniumLibrary to version 3.0.1

Ideally, it should also be made reverse-compatible with test suites which are still using Selenium2Library.

Improve project community & collaboration

The README file should contain information about how to contribute to the project and open defects / change requests.

Create simple test

The repository should include a simple test in order to check that the project is always working.

Update Firefox to version 61.0

Update Firefox to version 58.0

[ ERROR ] Suite 'Tests' contains no tests

Getting [ ERROR ] Suite 'Tests' contains no tests when trying to run the image and when specifying either browser.

Running Docker toolbox:
command:
docker run -v /Users/dthmacpro/Documents/robotfw/reports:/opt/robotframework/reports -v /Users/dthmacpro/Documents/robotfw/test_suites:/opt/robotframework/tests -e BROWSER=firefox ppodgorsek/robot-framework:latest
[ ERROR ] Suite 'Tests' contains no tests.

not sure why it's not seeing the Tests... please assist, thanks!

Document how to switch browsers

It would be useful to have more information about how to switch browsers in test suites, by only setting the browser on the command-line.

Add support for Opera

A Linux version can be fetched from the official website.

Allow passing Robot options via an environment variable

This would allow users to benefit from all Robot options.

Set up automated build of pull requests

All pull requests should be built automatically before being merged to the master branch.
The master branch should always remain stable, as it built on the Docker Hub.

Update the base image to the latest Fedora version

Fedora is now available in version 26.

Update the Selenium Library to version 3.0.0

See https://github.com/robotframework/SeleniumLibrary/releases/tag/v3.0.0

Outdated Chromium causes Docker build to fail

Complete!
Last metadata expiration check: 0:00:57 ago on Tue Apr 3 08:35:14 2018.
No match for argument: chromedriver-63.0.*
No match for argument: chromium-63.0.*
Error: Unable to find a match
The command '/bin/sh -c dnf upgrade -y && dnf install -y chromedriver-$CHROMIUM_VERSION chromium-$CHROMIUM_VERSION firefox-$FIREFOX_VERSION python2-pip-9.0.1-* xauth xorg-x11-server-Xvfb-1.19.* which wget && dnf clean all' returned a non-zero code: 1

Reorganise the README file's sections

All sections are on the same level, there could be some improvement, especially regarding "browser switch" which could be under "how to run".

Update Chromium to version 65.0

Update Firefox to version 55.0

55.0.1-1.fc26 is the latest version available.

Add parallel execution support

pabot should be added to the toolchain of this chart. This would allow users to launch tests in parallel whenever it is required.

This can be done by passing environment variables to the docker container and invoking a bash script whenever required.

Internally we are currently using the following bash script:

#!/bin/sh

set -e

# Install parallel executor "pabot"
pip install --upgrade --quiet robotframework-pabot

# Set number of threads for parallel execution
RF_THREADS=4

# Launch Robot Framework instances
xvfb-run \
    --server-args="-screen 0 ${SCREEN_WIDTH}x${SCREEN_HEIGHT}x${SCREEN_COLOUR_DEPTH} -ac" \
    pabot \
        --verbose \
        --processes $RF_THREADS \
        --outputdir /opt/robotframework/reports \
        ${ROBOT_OPTIONS} \
        /opt/robotframework/tests

exit 0

Add support for Chrome

Currently, only Firefox is included in the Docker image, Chrome should be too.

dnf install -y chromedriver-66.0.* Failed, No match for arguments.

Complete!
Non-fatal scriptlet failure in rpm package libgcc
Non-fatal scriptlet failure in rpm package libgcc
Last metadata expiration check: 0:01:38 ago on Wed Jun 27 21:59:23 2018.
No match for argument: chromedriver-66.0.*
No match for argument: chromium-66.0.*
Error: Unable to find a match

cannot build the project

I ran command docker build -t robot-framework . and got the error below.

Error: Unable to find a match
The command '/bin/sh -c dnf upgrade -y	&& dnf install -y		chromedriver-63.0.*		
chromium-63.0.*		firefox-58.0-*python2-pip-9.0.1-*		xorg-x11-server-Xvfb-1.19.*	&& dnf 
clean all' returned a non-zero code: 1

My docker version as below.

docker version
Client:
 Version:	17.12.0-ce
 API version:	1.35
 Go version:	go1.9.2
 Git commit:	c97c6d6
 Built:	Wed Dec 27 20:03:51 2017
 OS/Arch:	darwin/amd64

Server:
 Engine:
  Version:	17.12.0-ce
  API version:	1.35 (minimum version 1.12)
  Go version:	go1.9.2
  Git commit:	c97c6d6
  Built:	Wed Dec 27 20:12:29 2017
  OS/Arch:	linux/amd64
  Experimental:	true

Update SeleniumLibrary to version 3.1.1

More information can be found on the official GitHub project

Explain why this project uses SeleniumLibrary instead of Selenium2Library

It is important to note that this is not a regression and should be explained in the README file.
As stated by the official GitHub project:

Starting from version 3.0, Selenium2Library is renamed to SeleniumLibrary and this project exists mainly to help with transitioning.

See https://github.com/robotframework/Selenium2Library

Missing drivers

I'm not sure how is this supposed to work, since it doesn't contain selenium drivers?

WebDriverException: Message: 'chromedriver' executable needs to be in PATH. Please see https://sites.google.com/a/chromium.org/chromedriver/home

WebDriverException: Message: 'geckodriver' executable needs to be in PATH.

Am I missing something obvious?

Update Firefox to latest version

The latest version is 57.0-2.fc26

Automated update of dependencies in Dockerfile

Investigate if Travis could also be used to update the versions of all dependencies and to commit an updated Dockerfile whenever it is possible (merged to master via an automated pull request merge).

This would allow to regularly push updated Docker images without the need for a manual intervention.

Update Firefox to version 52.0

This is the latest update available.

Add info about accessing the logs to troubleshoot

This will be helpful for everyone, especially when Chromium crashes (this is the most problematic of both browsers).

Update the base image version

The latest version of Fedora is 27.

Automated build including tests with different resolutions

The automated build currently doesn't check if the change of resolution works or not, it should include such tests.

Common resolutions which can be used:

• 800 x 600
• 1024 x 768
• 1280 x 1024
• 2560 x 1440
• 3840 x 2160

Update Firefox to version 60.0

Add simple tests for the Faker library

This will allow to check whether the plugin is working correctly or not.