Skip to main content
OnPageIQ Documentation

Test Environment & Accounts

Seeders, demo credentials, and commands to reset local QA data.

User goal

Get a predictable org with features enabled for manual and Playwright testing.

Tier
QA / dev only
Nav label
N/A
Route
/docs/test-environment
Gates
—

Prerequisites

  • Database migrated (php artisan migrate)

QA focus

  • Never use production credentials
  • Re-seed after schema changes

Overview

Use dedicated seeders instead of manual clicks so local QA stays predictable after migrate or schema changes.

What you get

  • Platform Docs Demo: enterprise org with most Pennant flags on and live demo URLs
  • Screenshot Addon Demo: rich screenshot fixtures (full, empty, partial)
  • docs:prepare / capture / docs:publish flow for platform-doc images

How it works

  • Prefer seeder commands over hand-building orgs; re-seed after schema changes
  • Log in with the seeded demo credentials listed in the steps below
  • Never use production credentials; flush Pennant cache in tests after toggling flags

Common issues & false alarms

  • Pennant cache: run Feature::flushCache() in tests after toggling flags
  • Stale public/platform-doc-images after capture — run docs:publish

Interactive guide

Step of

All steps (reference)

  1. Step 1. Platform Docs Demo org

    Enterprise org with live demo URLs (VYVGART Hytrulo + Okta). Scans are real — not seeded fake issues.

    What to do: php artisan docs:prepare --sync

    Where: Login: platform-docs@onpageiq.test / password

    Expected (pass)

    • Org slug: platform-docs-demo
    • Project “Platform Docs Demo” with vyvgarthcp.com and okta.com URLs
    • Completed scans show real issues from live pages

  2. Step 2. Screenshot Addon Demo org

    Three projects: full gallery, empty, partial viewport — for screenshot QA.

    What to do: php artisan db:seed --class=ScreenshotAddonDemoSeeder

    Where: Login: qa-screenshot@onpageiq.test / password

    Expected (pass)

    • Showcase project has 27 URLs with screenshots
    • Empty project shows no-scans state

  3. Step 3. Capture & publish doc screenshots

    Playwright browser tests write PNGs next to documentation source.

    What to do: php artisan test tests/Browser/Docs && php artisan docs:publish

    Expected (pass)

    • PNGs under docs/platform/images/{slug}/
    • Published to public/platform-doc-images/

Related guides

QA Handbook

How to test OnPageIQ: smoke checklist, regression rules, job queues, and what to file as bugs.

Getting Started

First-run orientation: log in, create a project, run a content scan, and read results.