UI tests
Use the UI track when you want Ogoron to generate and maintain browser-based tests for your product UI.
What you need
Before working with UI tests, make sure the machine can run the Python UI workspace:
- Python
3.11+ - a working browser runtime for Playwright
- access to install Python dependencies into
.ogoron/tests/.venv
Ogoron also collects Allure-compatible results for the UI track. The Python dependency is installed automatically in the workspace. The Allure CLI is optional and is only needed when you want to render or browse HTML reports locally.
Typical flow
From the project root:
ogoron analyze business
ogoron prepare ui-workspace
ogoron generate test-cases --by-text "Describe the feature and what must be tested"
ogoron generate autotests
ogoron run smoke
ogoron run ui-tests
When generated UI tests fail and you want a diagnosis-and-repair workflow:
ogoron heal ui-tests
What each command does
ogoron prepare ui-workspacecreates the Python UI workspace under.ogoron/tests, prepares its runtime, and can populate the initial support layer.ogoron generate test-casescreates UI test case artifacts that drive UI autotest generation.ogoron generate autotestsgenerates executable UI tests and supporting code for the workspace.ogoron run smokeruns fast workspace-level smoke checks for the UI track.ogoron run ui-testsruns generated UI tests from.ogoron/tests/tests/ui/generated.ogoron heal ui-testsruns generated UI tests and produces a UI-focused healing workflow.
Runtime inputs
The UI track commonly uses:
.ogoron/configs/sut_topology.ymlfor UI environment wiring.ogoron/tests/test.envfor local runtime overridesOGORON_UI_BASE_URLwhen the base URL must be forced explicitly
If your project needs a custom environment layout, start from the SUT topology template:
What to commit
Commit the parts of the UI workspace that represent source or configuration:
.ogoron/keep-git/**.ogoron/tests/ogoron_ui/**.ogoron/tests/tests/ui/generated/**.ogoron/tests/pytest.ini.ogoron/tests/pyproject.toml.ogoron/tests/conftest.py.ogoron/tests/test.env.example.ogoron/configs/sut_topology.ymlwhen your project uses it
What not to commit
Do not commit temporary runtime state or local artifacts:
.ogoron/.meta/**.ogoron/for-human/**.ogoron/tests/.venv/**.ogoron/tests/test-results/**.ogoron/tests/test.env- caches such as
__pycache__,.pytest_cache,.ruff_cache