@loadmill/droid-cua 2.31.0 → 2.32.0

package/README.md

@@ -97,7 +97,7 @@ Desktop app support:
 - **Setup guidance** - Configure API access and platform prerequisites in the app
 - **Device and simulator connection** - Connect Android targets and iOS simulators
 - **Natural-language test creation** - Describe flows in plain English
-- **Test management** - Create, edit, save, and rerun reusable scripts
+- **Test management** - Create, edit, save, and rerun reusable scripts, including tests organized in nested project folders
 - **Live execution logs** - Watch actions and progress as tests run
 - **Reports and history** - Review past runs from a project results folder inside the desktop app
 - **JUnit XML output** - Write standard test reports for CI systems and external tooling
@@ -128,6 +128,8 @@ For CI, scripting, or advanced workflows, `droid-cua` also includes a CLI for ru
 
 Desktop projects can also keep run reports in a results folder, including JUnit XML output that the app can read back as project history.
 
+When a desktop project contains nested folders, the app discovers `.dcua` files recursively and displays their directory structure in the project tree. You can create tests in nested folders, open those folders in Finder, drag tests between project roots and nested folders, run an individual test, run a nested folder and all its descendants, or run the entire project. Nested tests use the configured project folder's `context.md`, `test-data.md`, `.secrets`, results folder, and desktop execution settings.
+
 The recommended workflow is:
 - design and debug tests in the desktop app,
 - commit the `.dcua` file plus a headless CLI config file,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loadmill/droid-cua",
-  "version": "2.31.0",
+  "version": "2.32.0",
   "description": "AI-powered Android testing agent using OpenAI's computer-use model and ADB",
   "main": "build/index.js",
   "type": "module",