QA Roadmap

Skill/technology roadmap for the QA track, in the style of roadmap.sh. See reference/mermaid-conventions.md for the diagram conventions used below.

Legend

• 🟦 Essential
• 🟧 Recommended
• ⬜ Optional

Diagram

flowchart TD
    classDef essential fill:#4C6EF5,color:#fff,stroke:#333;
    classDef recommended fill:#F5A623,color:#000,stroke:#333;
    classDef optional fill:#eee,color:#000,stroke:#999,stroke-dasharray: 3 3;

    subgraph Fundamentals
        A[Test strategy & planning]:::essential --> B[Playwright<br/>end-to-end]:::essential
        B --> C[Lighthouse CI<br/>performance]:::essential
        C --> D[axe<br/>accessibility]:::essential
    end
    subgraph "Going Further"
        D --> E[Visual regression testing]:::recommended
        D --> F[Contract testing<br/>API]:::recommended
        D --> G[Load/performance testing<br/>k6 or equivalent]:::optional
    end

    D --> AEMT
    D --> AEMEDS
    D --> OPTLY
    D --> CTFL

    subgraph AEMT["AEM Traditional"]
        H[JUnit, Mockito]:::essential
        I[AEM Mocks<br/>wcm.io]:::essential
    end
    subgraph AEMEDS["AEM EDS"]
        J[Lighthouse CI<br/>as primary metric]:::essential
    end
    subgraph OPTLY["Optimizely Cloud"]
        K[xUnit/NUnit]:::essential
    end
    subgraph CTFL["Contentful"]
        L[Jest/Vitest +<br/>Testing Library]:::essential
    end

Notes

Fundamentals and Specializations are drawn from roles/qa.md’s Must have and By CMS lists. “Going Further” is proposed from general QA industry practice, not from the team’s own stated preferences (roles/qa.md’s Nice to have is still empty) — revise freely.