What is Reflex?
This page explains what Reflex is and which part to start with.
Reflex runs test and task automation written in Lua or Python: browser and API tests, Excel and mail processes, SFTP file exchanges. You plan and watch the work in a web UI. Agents run it close to the systems you test.
The pieces
Section titled “The pieces”- Server: the web UI. It holds projects, schedules, secrets, roles and run history. It never runs scripts itself.
- Agent: runs your scripts and streams the steps and output back. Run one wherever it can reach your systems.
- Project: your scripts plus their agents, secrets, members, jobs and suites.
- Script: a Lua or Python file with the libraries already loaded. Nothing to import.
- Job: a script on a cron schedule. A finished job can start the next one.
- Suite: all scripts with certain tags, run in parallel. The result is a score: the percentage of scripts that passed.
- Run: one execution, with its steps, output, files and duration. Debug a failed run in the browser.
Where do you start?
Section titled “Where do you start?”- You have recurring checks or processes a team should watch. Run the server, then follow the Quick start.
- Your acceptance tests live in FitNesse. Add the Reflex fixtures.
- Tests must run in your Java build. Use TestNG: annotate a test with
@LuaScriptand let Maven run it. - You work from a terminal or an AI coding tool. Use the CLI or connect your AI client through MCP.
All four use the same libraries. A script you build with the CLI runs unchanged as a server job, in FitNesse or under TestNG.
- Quick start: from download to a scheduled script.
- Write scripts and copy from the examples.
- Schedule jobs and suites.