Development

Source layout, harnesses, and test entry points for contributors working on cua-driver.

cua-driver lives under libs/cua-driver in the repository. The hosted docs describe the public interface; contributor details live next to the code so they stay close to implementation changes.

Source Map#

Path	Purpose
`libs/cua-driver/rust`	Rust workspace for the daemon, platform crates, testkit, and helper crates
`libs/cua-driver/python`	Python package wrapper around the driver binary
`libs/cua-driver/tests/fixtures`	Source-built GUI harness apps and shared fixtures
`libs/cua-driver/rust/crates/cua-driver/tests`	Rust integration tests for the driver and GUI harnesses
`libs/cua-driver/scripts`	Install, uninstall, local build, and VM sync helpers

Contributor Entry Points#

libs/cua-driver/README.md gives the repo-local overview.
libs/cua-driver/rust/README.md maps the Cargo workspace and test classes.
libs/cua-driver/rust/crates/cua-driver/tests/README.md explains Rust test naming and ignored GUI lanes.
libs/cua-driver/tests/fixtures/README.md explains source-built harness apps and staged outputs.
libs/cua-driver/rust/crates/cua-driver/tests/README.md explains Rust test naming and ignored GUI lanes.
libs/cua-driver/scripts/README.md explains install and VM sync helpers.

Build artifacts, VM logs, and local verification journals should stay out of git unless they have been promoted into a stable fixture or contributor doc.