Parrot lets you record mouse clicks, keyboard input, and navigation paths through any X11 GUI application, then replay those interactions automatically. It is designed for benchmarking and testing desktop applications in a reproducible, sandboxed environment.
Everything runs inside Docker, so there are no security implications for the host system and results are fully reproducible across machines.
- Record β Interact with any X application through a browser-based VNC viewer. Parrot captures every mouse movement, click, and keystroke. It also takes care of setting the screen and application size correctly.
- Replay β Play back the recorded session against the same application. Parrot finds the correct window, replays each action with correct timing, and optionally asserts on screenshots.
- Benchmark β Plug the replay into the Green Metrics Tool via a
usage_scenario.ymlto measure energy and performance.
| Application | Path |
|---|---|
| Firefox | applications/firefox/ |
| LibreOffice Calc | applications/calc/ |
| VLC | applications/vlc/ |
| Okular (PDF viewer) | applications/pdf_viewers/okular/ |
Each application directory contains the recorded .π¦ macro file and a usage_scenario.yml for use with the Green Metrics Tool.
Every application ships with a Docker Compose file (or uses the shared ribalba/xwindow-server image). To bring up Firefox:
docker compose -f applications/firefox/usage_scenario.yml up --buildOpen the GUI in your browser at http://localhost:6080/vnc.html.
./record-macro.py applications/firefox/usage_scenario.yml- Interact with the application in the browser-based VNC viewer.
- Press
Pauseto stop recording. - Press
Scroll Lockat any point to capture a reference screenshot (inserts aCheckassertion into the macro). - Pass
--script path/to/script.mdto attach one note per checkpoint; trimmed blank lines and lines starting with#are ignored. - When a script is provided, recording shows a live checklist and highlights the next pending item in green.
Override the hotkeys if your browser intercepts them:
STOP_KEYSYM=F9 CHECK_KEYSYM=F3 ./record-macro.py applications/firefox/usage_scenario.ymlOutput files are written to recordings/<app-name>/:
recordings/firefox/firefox.π¦
recordings/firefox/firefox-check-001.png
./replay.py applications/firefox/usage_scenario.ymlOptional speed multiplier:
REPLAY_SPEED=2.0 ./replay.py applications/firefox/usage_scenario.yml # faster
REPLAY_SPEED=0.5 ./replay.py applications/firefox/usage_scenario.yml # slowerReplay finds the application window by class/title metadata embedded in the macro, focuses it, and plays back every action. Any Check line triggers a screenshot comparison against the saved reference image. A failed check exits non-zero.
Parrot is not limited to the bundled applications. You can record interactions with any X11 GUI application by supplying the relevant metadata at record time:
APP_STARTCOMMAND='xterm' \
APP_WINDOW_TITLE='xterm' \
APP_WINDOW_CLASS='xterm' \
./record-macro.py <your-compose-file.yml>Metadata is embedded into the .π¦ macro file and used by replay to locate and focus the correct window.
Recorded macros (.π¦ files) contain:
#APPmetadata lines β window class, title, and optional start command- Timed xmacro events β
MotionNotify,ButtonPress,KeyStrPress, etc. #WAIT_SEC <seconds>β timing gaps between eventsCheck <path>.pngβ screenshot assertion lineslog <text>β note lines emitted to stdout during replay as<timestamp_microseconds> <text>
Example header:
#APP startcommand='firefox https://browserbench.org/Speedometer3.1/'
#APP windowtitle=Firefox
#APP windowclass=firefox
Press Scroll Lock during recording to insert a checkpoint. During replay, Parrot compares the current window screenshot to the saved reference using RMSE.
Tune the comparison:
# Loosen the threshold
CHECK_MAX_RMSE=0.02 ./replay.py applications/firefox/usage_scenario.yml
# Ignore dynamic regions (e.g. toolbars, clocks) β format: x,y,width,height
CHECK_IGNORE_RECT=0,0,420,40 ./replay.py applications/firefox/usage_scenario.yml
# Multiple regions (semicolon-separated)
CHECK_IGNORE_RECT="0,0,420,40;300,580,120,30" ./replay.py applications/firefox/usage_scenario.ymlParrot has native support for the Green Metrics Tool. Each application includes a usage_scenario.yml that defines the container setup and the replay command:
name: Parrot Firefox
author: Didi <didi@green-coding.io>
description: Benchmarks Firefox using Parrot
services:
window-container:
image: ribalba/xwindow-server
environment:
DEBUG: 0
setup-commands:
- command: bash /tmp/repo/applications/firefox/install.sh
- command: bash /usr/local/bin/entrypoint.sh
flow:
- name: Run Benchmark
container: window-container
commands:
- type: console
command: python3 /usr/local/bin/replay.py /tmp/repo/applications/firefox/firefox.π¦Point the Green Metrics Tool at the repository and it will set up the container, run the replay, and collect energy and performance metrics automatically.
To keep click coordinates and screenshots stable across runs, configure fixed window geometry in the compose environment:
| Variable | Description |
|---|---|
AUTO_POSITION |
1 to enable, 0 to disable |
WINDOW_X / WINDOW_Y |
Window position |
WINDOW_WIDTH / WINDOW_HEIGHT |
Window size |
APP_WINDOW_CLASS |
xdotool window class matcher |
APP_WINDOW_TITLE |
xdotool window title matcher |
- Stop key not working in browser β set
STOP_KEYSYMto another key, e.g.F9. - Check hotkey affects the app β
Scroll Lockis the default; if your keyboard or environment handles it poorly, choose another key viaCHECK_KEYSYM. - Screenshot checks fail due to minor UI variation β increase
CHECK_MAX_RMSEslightly or mask dynamic regions withCHECK_IGNORE_RECT. - Click coordinates are off β rebuild/restart the container and re-record; window geometry may have shifted.