Skip to main content
The Arga web app separates service setup from test execution.

​
Test Runs

Use Test Runs when your application is already reachable at an HTTP or HTTPS URL.
  1. Open Test Runs in the sidebar.
  2. Enter the starting URL and describe the flow.
  3. Start the run and watch the browser frame and event stream.
  4. Review the generated blocks, parameters, screenshots, and summary.
  5. Edit and rerun the flow, or save it as a reusable test.
Test blocks can navigate, click, type, press a key, wait, assert visible state, or ask for user input.

​
Saved Tests

Use Saved Tests to keep a browser flow after a successful Test Run. A saved test stores its prompt, starting URL, blocks, parameters, assertions, and optional encrypted credentials. From Saved Tests, you can:
  • edit blocks and parameters;
  • change the starting URL or repository association;
  • choose whether a repository’s PR Test Runs may select the test;
  • rerun or delete the test.

​
Twin Runs

Use Twin Runs to provision service twins without deploying application code.
  1. Open Twin Runs in the sidebar.
  2. Select one or more services.
  3. Choose an empty state, a saved Scenario, or a natural-language seed description.
  4. Choose a short-lived or persistent session.
  5. Start the run and copy the returned URLs or environment variables into your app.
Short-lived runs can be reset, extended within your plan limit, locked from public access, or torn down. Persistent twin environments are attached to saved Scenarios and can be reseeded later.

​
Scenarios

Use Scenarios to save seed data for one or more twins. You can create a Scenario from a prompt, explicit JSON, selected production data, or the current state of a twin dashboard. Scenarios do not run browser tests. They define the baseline used when a Twin Run starts or when a persistent twin environment is reseeded. See Scenarios for the schema and creation methods.

​
PR Test Runs

Use PR Test Runs to trigger repository tests when a pull request changes or a configured branch receives a commit.
  1. Install the Arga GitHub App on the repository.
  2. Choose Pull requests or Commits to branch.
  3. Add optional repository-specific instructions and PR comments.
  4. In Saved Tests, let Arga choose relevant tests or pin selected tests to the repository.
  5. Review the Arga Validation check in GitHub or open the run from Arga.
PR Test Runs exercise the application URL configured for the repository. They do not deploy the changed application into a per-PR Arga environment. See PR Test Runs for setup details.