Skip to main content
Start with a browser test against an existing URL. Add service twins when you need safe, repeatable external-service state.

​
Run your first browser test

1

Install and authenticate the CLI

2

Start a Test Run

Point Arga at a deployed application URL and describe the flow to test:
Arga opens a browser, executes the flow, and records events, screenshots, and editable test blocks.
3

Inspect the result

Use the run ID printed by the CLI:
You can also open app.argalabs.com/test-runs to watch runs and inspect their results.

​
Test an authenticated flow

Provide credentials for a test account in your application:
Both --email and --password are required when either flag is present. These are credentials for the application under test, not your Arga account.

​
Add service twins

Use a Twin Run when your software needs to act on Slack, Stripe, GitHub, Gmail, Google Calendar, or another supported service without touching the real provider.
1

Provision the twins

Run arga previews twins list to see the current catalog.
2

Point your app at the returned endpoints

The ready response includes a base URL and environment variables for each twin. Apply those values to the app or agent you are testing, then start it normally.If you want Arga to detect provider variables and update a local .env file, run:
The wizard creates .env.arga-backup before changing the file.
3

Test and reset

Exercise the app manually or run a browser Test Run against its reachable URL. Reset the twins to their original seed state before repeating the test:
For reusable state, create a Scenario and pass its ID when you provision the twins.

​
Next steps

Twin Runs

Manage twin URLs, state, access, TTL, reset, and teardown.

Test workflows

Save browser flows and configure PR Test Runs.

Scenarios

Define repeatable twin data with a prompt or explicit JSON.

Integrations

Create scenarios from selected production data.