Krow/Krow-workspace
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

maestra testcases

Browse Source
This commit is contained in:
Suriya
2026-02-25 22:06:22 +05:30
parent b85a83b446
commit 165fe5b66b
14 changed files with 363 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/research/flutter-testing-tools.md
View File

@@ -68,11 +68,17 @@ Semantics(
)
```
### Phase 2: Repository Structure
Tests will be localized within the respective app directories to maintain modularity:
### Phase 2: Repository Structure (Implemented)
Maestro flows are co-located with each app:
* `apps/mobile/apps/client/maestro/`
* `apps/mobile/apps/staff/maestro/`
* `apps/mobile/apps/client/maestro/login.yaml` — Client login
* `apps/mobile/apps/client/maestro/signup.yaml` — Client signup
* `apps/mobile/apps/staff/maestro/login.yaml` — Staff login (phone + OTP)
* `apps/mobile/apps/staff/maestro/signup.yaml` — Staff signup (phone + OTP)
Each directory has a README with run instructions.
**Marionette MCP:** `marionette_flutter` is added to both apps; `MarionetteBinding` is initialized in debug mode. See [marionette-spike-usage.md](marionette-spike-usage.md) for prompts and workflow.
### Phase 3: CI/CD Integration
The Maestro CLI will be added to our **GitHub Actions** workflow to automate quality gates.