* the subject image is now being rebuilt less frequently so note that in the README.md * [skip ci] |
||
|---|---|---|
| .drone.yml | ||
| .gitignore | ||
| docs | ||
| LICENSE | ||
| m-test00.robot | ||
| m-test01.robot | ||
| m-test02.robot | ||
| m-test03.robot | ||
| m-test04.robot | ||
| m-test05.robot | ||
| m-test06.robot | ||
| m-test07.robot | ||
| m-test08.robot | ||
| m-test09.robot | ||
| m-test10.robot | ||
| m-test11.robot | ||
| m-test12.robot | ||
| m-test13.robot | ||
| m-test14.robot | ||
| m-test15.robot | ||
| m-test16.robot | ||
| m-test17.robot | ||
| m-test18.robot | ||
| m-test19.robot | ||
| README.md | ||
| runtests.plz.sh | ||
| silly.windows.bat.trololol.bat | ||
| test00.robot | ||
| test01.robot | ||
| test02.robot | ||
| test03.robot | ||
| test04.robot | ||
| test05.robot | ||
| test06.robot | ||
| test07.robot | ||
| test08.robot | ||
| test09.robot | ||
| test10.robot | ||
| test11.robot | ||
| test12.robot | ||
| test13.robot | ||
| test14.robot | ||
| test15.robot | ||
| test16.robot | ||
| test17.robot | ||
| test18.robot | ||
| test19.robot | ||
| test_hierarchy.mermaid.js | ||
| test_hierarchy.png | ||
TSO-SW
this repo holds the sawce files for the TSO semestral work
hierarchy
preferred workflow
- using a container image with
robotframework,selenium,chromiumandchromedriverpreinstalled, such asalpine-rforarchlinux-rf
Note: you may need to run some of the following commands as root. You can as well learn how not to here.
get a container and run it
fetch an image from a central container repository (by default it's DockerHub) using
docker pull immawanderer/alpine-rf:latest
the alpine-rf image is being rebuilt on an hourly on a daily basis, so I recommend updating frequently.
run the container in interactive mode, mounting user's $PWD into container's /testing folder, removing the container after exiting (so that it doesn't take up space) while preserving the work done (saved on the shared volume)
docker run --rm -it -v $PWD:/testing immawanderer/alpine-rf:latest
run robot tests
as the WORKDIR of the image used in this example is set to the /testing folder, all that's left is to prepare a results directory inside there
❄ root@alpine-rf /testing
➜ mkdir -p /testing/results
then simply run the test(s)
❄ root@alpine-rf /testing
➜ robot -T -d results test00.robot
or (when using the alpine-rf image) run all of the above as a designated test user rf (uid=1000) instead of root
❄ root@alpine-rf /testing
➜ su rf
/testing $ mkdir -pv results
/testing $ robot -T -d results test00.robot
mermaid.js
the diagram under hierarchy was generated using this mermaid.js code
