Migrate from Mabl

npm install -g testerarmy
ta auth

# Plan: Checkout regression (staging, https://staging.shop.example.com)

## Test: Guest checkout

- Visit home page
- Search for "running shoes"
- Open the first product
- Add to cart
- Check out as guest with a valid US address
- Assert: order confirmation page shows an order number

## Flow used by multiple tests: Login

- Visit /login
- Sign in as standard user

Migrate my Mabl tests to TesterArmy using the TesterArmy CLI (`ta`). The
Mabl inventory is in mabl-export.md. Verify auth first with
`ta status --json`, and use `ta --help` plus subcommand help to discover
commands. Prefer --json output.

1. Read mabl-export.md. Each "Test" becomes one TesterArmy test. Plans
   indicate grouping and target environment URLs.

2. Create a TesterArmy project (skip if one exists in `ta projects list`):
   echo '{"name":"<app name>","url":"<primary environment URL>","projectType":"web"}' | ta projects create --json

3. Convert each shared Mabl flow into a project memory so every test run
   knows about it (category site_structure, importance high), e.g. "Login
   is at /login; standard users land on /dashboard after signing in."
   echo '{"category":"site_structure","title":"...","content":"...","importance":"high"}' | ta memories create --project <projectId> --json

4. Convert each Mabl test into a TesterArmy test:
   - Recorded interactions -> steps with type "act"
   - Mabl assertions (including visual assertions) -> steps with type "assert"
   - Login flows -> one step with type "login"
   - Where DataTables supplied values, write one test with representative
     data described in plain English; flag remaining permutations for me
     to review instead of generating dozens of near-duplicates.
   - Keep tests focused: 3-10 steps.
   Create each test:
   echo '{"title":"<test name>","description":"Migrated from Mabl plan <plan>","steps":[{"title":"Visit the home page","type":"act"},{"title":"Order confirmation shows an order number","type":"assert"}]}' | ta tests create --project <projectId> --json
   Step types: act, assert, login, files, screenshot, javascript, microphone.

5. Never hardcode passwords in test steps. List the Mabl credentials each
   test relied on and I will add them with:
   echo '{"kind":"login","label":"...","username":"...","password":"..."}' | ta projects credentials-create <projectId> --json

6. Verify: save a cloud-reachable preview or tunnel URL with
   ta projects environments-create <projectId> --name Verification --url <url> --json
   Then run each migrated test in TesterArmy cloud with
   `ta tests run <testId> --env verification --wait --json` and report
   results. Exit code 0 = pass, 1 = fail.

7. Report a summary table: Mabl test -> TesterArmy test ID -> run result,
   plus anything you skipped (API tests, extra DataTable rows) and why.