SG/Send QA

Living documentation and automated test results for SG/Send — the encrypted file sharing platform by SGraph AI.

What is SG/Send?

SG/Send is a secure, encrypted file sharing platform that enables controlled distribution of sensitive documents. Key security features include:

• Beta Access gate — users must present a valid token before accessing any functionality
• Token-based authentication — each sharing session is scoped to a unique access token
• Encrypted file transfers — files are protected in transit and at rest
• Audit trail — all access attempts (including invalid tokens) are logged

What is This Site?

This documentation is automatically generated from Playwright browser tests that run against the live SG/Send platform. Every page documents a real user workflow, captured as screenshots and verified by automated assertions.

flowchart LR
    A["Playwright\nBrowser Tests"] -->|capture| B["Screenshots\n(1280x720)"]
    B -->|generate| C["Markdown\nDocumentation"]
    C -->|build| D["Jekyll\nStatic Site"]
    D -->|deploy| E["qa.send.sgraph.ai"]

Each test produces two outputs: a pass/fail result and a set of annotated screenshots that become the documentation you are reading now.

Use Cases

These are the user workflows currently tested and documented:

Architecture

Test Pipeline

The QA pipeline runs on every push. Tests exercise the real SG/Send UI via headless Chromium, capture screenshots, generate documentation, and deploy to this site.

┌─────────────────────────────────────────────────────────────┐
│                     CI Pipeline                             │
│                                                             │
│  ┌───────────┐     ┌──────────────┐     ┌───────────────┐  │
│  │  pytest +  │────▶│  Screenshot  │────▶│  Markdown     │  │
│  │ Playwright │     │  Capture     │     │  Generator    │  │
│  └───────────┘     └──────────────┘     └───────────────┘  │
│       │                   │                     │           │
│       ▼                   ▼                     ▼           │
│  ┌───────────┐     ┌──────────────┐     ┌───────────────┐  │
│  │  Pass/Fail │     │ Visual Diff  │     │ Jekyll Build  │  │
│  │  Results   │     │ (noise gate) │     │ + Deploy      │  │
│  └───────────┘     └──────────────┘     └───────────────┘  │
└─────────────────────────────────────────────────────────────┘

Visual Diff Noise Gate

Screenshots are compared pixel-by-pixel against their previous versions. Changes below a 1% threshold are reverted — this filters out anti-aliasing jitter, sub-pixel rendering differences, and font hinting variations that would otherwise create noise commits.

flowchart TD
    A[New Screenshot] --> B{Pixel diff vs HEAD}
    B -->|"> 1% changed"| C[KEEP — real UI change]
    B -->|"≤ 1% changed"| D[REVERT — rendering noise]
    C --> E[Commit to repo]
    D --> F[Restore HEAD version]

Content Bundle Structure

Each use case is a self-contained directory with its documentation and screenshots co-located:

sg_send_qa__site/pages/use-cases/
├── landing_page_loads/
│   ├── landing_page_loads.md      ← documentation page
│   └── screenshots/
│       └── 01_landing.png         ← captured during test
├── landing_page_has_access_gate/
│   ├── ...md + screenshots/
└── invalid_token_rejected/
    ├── ...md + screenshots/

Test Targets

Stack