Source: yarf Section: devel Priority: optional Maintainer: Debian Python Team Uploaders: Nadzeya Hutsko , Build-Depends: debhelper-compat (= 14), dh-sequence-python3, dh-sequence-single-binary, pybuild-plugin-pyproject, python3-all, python3-dateutil, python3-hatchling, python3-keysymdef, python3-numpy, python3-onnxruntime, python3-opencv, python3-owasp-logger, python3-packaging, python3-pil, python3-pil.imagetk, python3-prompt-toolkit, python3-pyfakefs , python3-pygments, python3-pyperclip, python3-pytesseract, python3-pytest , python3-pytest-asyncio , python3-pywayland, python3-rapidfuzz, python3-requests, python3-robot, python3-tk, python3-xkbcommon, Standards-Version: 4.7.4 Testsuite: autopkgtest-pkg-pybuild Homepage: https://github.com/canonical/yarf Vcs-Browser: https://salsa.debian.org/python-team/packages/yarf Vcs-Git: https://salsa.debian.org/python-team/packages/yarf.git Package: yarf Architecture: all Depends: python3-dateutil, python3-keysymdef, python3-numpy, python3-onnxruntime, python3-opencv, python3-owasp-logger, python3-packaging, python3-pil, python3-pil.imagetk, python3-prompt-toolkit, python3-pygments, python3-pyperclip, python3-pytesseract, python3-pywayland, python3-rapidfuzz, python3-requests, python3-robot, python3-tk, python3-xkbcommon, ${misc:Depends}, ${python3:Depends}, Recommends: tesseract-ocr, Description: visual test automation tool built on Robot Framework YARF (Yet Another Robot Framework) extends the Robot Framework with keyword libraries for driving and verifying graphical user interfaces. Tests are written in the usual Robot Framework syntax, but interact with the system under test through screenshots, template image matching and optical character recognition instead of through application specific APIs. This makes it possible to test installers, desktop images and embedded interfaces that expose no automation hooks of their own. . Input injection and screen capture are provided by pluggable platforms. Mir and other Wayland compositors are driven through the virtual-keyboard, virtual-pointer and screencopy protocols, while remote or virtualised systems are reached over VNC. . An interactive mode lets developers explore a running system and assemble a scenario keyword by keyword, so that the same test can later be replayed unattended in continuous integration.