Skip to main content
Browser Testing Push a PR → Morph tests your preview → posts video to PR.

​
Setup

1

Connect GitHub

Install the GitHub App and select your repositories.
2

Connect Vercel

If you’re on Vercel Pro/Enterprise, Deployment Protection blocks external access to previews by default.
  1. Click Connect Vercel in your Morph dashboard
  2. Select which team to install the integration into
  3. Click Connect account
Bypass secrets are automatically populated for your projects.

​
Options

OptionDescription
Browser profiles ⭐Sign into test accounts using a real browser. Sessions persist across tests. Best for OAuth, SSO, and most apps.
Site LoginSimple username/password for apps with basic login forms. Use x_user/x_pass in prompts.
Path filtersOnly test PRs touching specific paths
Check runsBlock merges until tests pass
Configure in the integrations dashboard.

​
FAQ

We recommend using Browser Profiles for most authentication scenarios.Best for: OAuth, SSO, Google/GitHub login, complex login flows, or any app where you need to stay logged in.
  1. Expand your repo in the integrations dashboard
  2. Click + new profile in the Browser Profiles section
  3. A browser opens — sign into your test account normally
  4. Click Save Profile when done
The authenticated session persists across all future test runs. You can create multiple profiles and set one as active.

​
Site Login (Simple auth)

Best for: Apps with a simple username/password login form (no OAuth, no SSO).
  1. Connect Vercel in the integrations dashboard
  2. Expand a project and configure Site Login
  3. Enter your test account credentials
  4. In your test prompts, use x_user and x_pass — Morph substitutes the real values
Site Login only works for simple form-based login. If your app uses OAuth (Google, GitHub, etc.) or SSO, use Browser Profiles instead.
Vercel Deployment Protection is blocking access. Make sure you’ve connected Vercel through the integrations dashboard—bypass secrets are added automatically.
This typically happens when your preview environment is using production environment variables. OAuth providers (Google, GitHub, etc.) require redirect URIs to be whitelisted, and production tokens only allow production URLs.Solution: Configure your deployment platform to use development/staging tokens for preview environments:
  • Vercel: Use Environment Variable Scopes to set different OAuth credentials for Preview vs Production
  • Other platforms: Create separate environment variable configs for preview deployments
Make sure your OAuth provider has your preview URL patterns (e.g., *.vercel.app) added to the allowed redirect URIs.
Yes. Use the GitHub Action for custom deployments:
- uses: morphllm/preview-test-action@v1
  with:
    api-key: ${{ secrets.MORPH_API_KEY }}
    preview-url: ${{ steps.deploy.outputs.url }}
See full action docs below.

​
GitHub Action

For non-Vercel deployments: 
name: Preview Test
on: pull_request

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Deploy
        id: deploy
        run: echo "url=https://pr-${{ github.event.number }}.example.com" >> $GITHUB_OUTPUT

      - uses: morphllm/preview-test-action@v1
        with:
          api-key: ${{ secrets.MORPH_API_KEY }}
          preview-url: ${{ steps.deploy.outputs.url }}
          instructions: Test login and checkout flow  # optional
Requires the GitHub App installed and MORPH_API_KEY in repo secrets.

Browser Automation

Direct control, live sessions, recordings

Browser as Agent Tool

Add browser to your AI agents