All Projects → jimpriest → robotframework-preso

jimpriest / robotframework-preso

Licence: Unlicense license
Introduction to Robot Framework - TriTAUG Presentation

Programming Languages

RobotFramework
109 projects
shell
77523 projects
Dockerfile
14818 projects

Projects that are alternatives of or similar to robotframework-preso

page-modeller
⚙️ Browser DevTools extension for modelling web pages for automation.
Stars: ✭ 66 (+312.5%)
Mutual labels:  selenium, robot-framework
Edge Selenium Tools
An updated EdgeDriver implementation for Selenium 3 with newly-added support for Microsoft Edge (Chromium).
Stars: ✭ 41 (+156.25%)
Mutual labels:  selenium, chromium
gcf-packs
Library packs for google cloud functions
Stars: ✭ 48 (+200%)
Mutual labels:  selenium, chromium
Pychromeless
Python Lambda Chrome Automation (naming pending)
Stars: ✭ 219 (+1268.75%)
Mutual labels:  selenium, chromium
robotframework-seleniumtestability
Extension for SeleniumLibrary that provides manual and automatic waiting for asyncronous events like fetch, xhr, etc.
Stars: ✭ 34 (+112.5%)
Mutual labels:  selenium, robot-framework
docker-selenium-lambda
The simplest demo of chrome automation by python and selenium in AWS Lambda
Stars: ✭ 172 (+975%)
Mutual labels:  selenium, chromium
Playwright Go
Playwright for Go a browser automation library to control Chromium, Firefox and WebKit with a single API.
Stars: ✭ 272 (+1600%)
Mutual labels:  selenium, chromium
Cdp4j
cdp4j - Chrome DevTools Protocol for Java
Stars: ✭ 232 (+1350%)
Mutual labels:  selenium, chromium
Lambdium
headless chrome + selenium webdriver in AWS Lambda using the serverless application model
Stars: ✭ 246 (+1437.5%)
Mutual labels:  selenium, chromium
RobotEyes
Image comparison for Robot Framework
Stars: ✭ 62 (+287.5%)
Mutual labels:  selenium, robot-framework
throughout
🎪 End-to-end testing made simple (using Jest and Puppeteer)
Stars: ✭ 16 (+0%)
Mutual labels:  selenium, chromium
yt-videos-list
Create and **automatically** update a list of all videos on a YouTube channel (in txt/csv/md form) via YouTube bot with end-to-end web scraping - no API tokens required. Multi-threaded support for YouTube videos list updates.
Stars: ✭ 64 (+300%)
Mutual labels:  selenium
Google-DSC-Platform-Extension
Hello DSC Leads, Automate your process of adding attendees manually.
Stars: ✭ 16 (+0%)
Mutual labels:  selenium
SWET
Selenium WebDriver Page Test / workflow recorder (successor to SWD recorder)
Stars: ✭ 34 (+112.5%)
Mutual labels:  selenium
Mobilenium
Mobilenium allows you to use Selenium and have access to status codes and HTTP headers, without the need for manual labor.
Stars: ✭ 22 (+37.5%)
Mutual labels:  selenium
rfswarm
Robot Framework Swarm
Stars: ✭ 68 (+325%)
Mutual labels:  robot-framework
TinySeleniumVBA
A tiny Selenium wrapper written in pure VBA
Stars: ✭ 29 (+81.25%)
Mutual labels:  selenium
InstagramLocationScraper
No description or website provided.
Stars: ✭ 13 (-18.75%)
Mutual labels:  selenium
jupyter-django
Using Jupyter Notebook with Django: a presentation
Stars: ✭ 42 (+162.5%)
Mutual labels:  presentation
callisto
Callisto is an open-source Kubernetes-native implementation of Selenium Grid.
Stars: ✭ 83 (+418.75%)
Mutual labels:  selenium

README

Lightweight Alpine Docker container that runs Robot Framework using Selenium Chrome (Chromium) driver in native headless mode (no Xvfb required).

What is this repository for?

This repository has a Dockerfile that creates a container to run Robot Framework scripts locally, avoiding the hassles of setting up Python and Robot Framework locally.

Versioning

  • robotframework: latest
  • robotframework-seleniumlibrary: latest
  • robotframework-faker: latest
  • Chrome webdriver: latest
  • Chromium browser: latest

Pre-requisites

Docker should be already installed and running.

Assumptions

All of the helper scripts here are written for Mac/Linux in bash. It should be possible to translate these over to a Windows equivilant or possibly use WSL (Windows Subsystem For Linux) to run these.

Setup

1) Create docker image and shared volume:

./build

This creates an image based on the Dockerfile and creates a container running Robot Framework.

2) Set test path

Open robot.sh and set the TEST_PATH to point to the directory where your Robot tests live. By default the example tests in /test will be run. Note: Changes made to robot.sh do not require rebuilding as it runs locally.

3) Run Robot tests:

./robot.sh

This creates a new container, it will run any Robot Suite that is defined in your test directory (defined in step 2).

Test results (logs, reports and screenshots) will be stored in a /results directory. --outputdir is configured in robot.sh.

You should see results in the console:

./robot.sh 
==============================================================================
Robot                                                                         
==============================================================================
Robot.Test                                                                    
==============================================================================
Robot.Test.Open                                                               
==============================================================================
Open Site                                                             | PASS |
------------------------------------------------------------------------------
Robot.Test.Open                                                       | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==============================================================================
Robot.Test                                                            | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==============================================================================
Robot                                                                 | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==============================================================================
Output:  /robot/results/output.xml
Log:     /robot/results/log.html
Report:  /robot/results/report.html

Maintenance

Remove any containers and images related to this Dockerfile! After running this you will need to rebuild your image.

./remove

This will cleanup files from /results. Handy to run between tests.

./cleanup

Note each time you run a test a new container is created. To clean these up simply run:

docker container prune

Sending additional arguments to Robot

You can send parameters as part of Robot.sh script

e.g.

./robot.sh -v URL:https://www.amazon.com 

This is sent to the container like this:

robot -v URL:https://www.amazon.com 

Running Sample Tests

Pass a suite directory to Robot command:

 ./robot.sh --suite a-simple

Examine the /results directory after running tests to see logs, results and screenshots.

Credits

This was original forked and heavily modified from: https://github.com/cgowez/robot-docker

Found a work around for Chrome error in headless mode here which eliminates the '--no-sandbox' option: https://github.com/Zenika/alpine-chrome

Suggested VSCode Extensions

Disclaimer

  • I built this for my own personal use. YMMV.
  • It works on my system :)
  • It is pitch black. You are likely to be eaten by a grue.

License

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to http://unlicense.org

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].