extension-live-testing

Validate CUNYAutoLogin extension behavior against live CUNY SSO pages.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/AlexCMarty/CUNYAutoLogin --skill extension-live-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extension-live-testing
Source: https://github.com/AlexCMarty/CUNYAutoLogin/tree/main/.claude/skills/extension-live-testing
Command: npx skills add https://github.com/AlexCMarty/CUNYAutoLogin --skill extension-live-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the gap between unit/E2E test results and real-world CUNYAutoLogin extension behavior, which often only appears when interacting with live CUNY SSO pages, real credentials, and actual browser environments instead of mocked fixtures.

Core Features & Use Cases

  • Live Behavioral Verification: Confirm or refute concrete claims about extension behavior (e.g. invalid credential handling, TOTP autofill accuracy) against real CUNY login flows.
  • Visual QA & Documentation: Capture screenshots of sidebar layouts, onboarding screens, and edge case states to update project documentation or catch CSS regressions.
  • Edge Case Exploration: Probe rare flows like five-factor 2FA limits, Verify Later enrollment paths, and session resume behavior that are hard to replicate in automated test suites. Use Case: A developer fixing a login regression can use this Skill to verify that the extension correctly rejects an invalid CUNY password without advancing past the password entry screen, and capture a screenshot of the error state for the changelog.

Quick Start

Use the extension-live-testing skill to verify that the extension correctly autofills your valid CUNY credentials and TOTP code on the live login page, then capture a screenshot of the post-authentication sidebar for your documentation.

Frequently Asked Questions about extension-live-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a Chrome extension against live SSO pages instead of mocked fixtures?▼

To test a Chrome extension against live SSO pages, you can use MCP-driven browser automation to interact with real CUNY login flows, inspect DOM state, and verify actual extension behavior rather than relying on mocked test fixtures.

What is the best way to automate TOTP autofill testing for a browser extension?▼

The best way to automate TOTP autofill testing is using credential-safe TOTP generation during live browser automation to verify that the extension accurately autofills valid credentials and TOTP codes on real login pages.

How do I capture screenshots of extension sidebar layouts for visual QA?▼

You capture screenshots of extension sidebar layouts by running MCP browser automation against live pages, documenting onboarding screens and edge case states to catch CSS regressions or update project documentation.

Can I use browser automation to explore 2FA enrollment edge cases?▼

Yes, you can use browser automation to explore 2FA enrollment edge cases by probing rare flows like five-factor 2FA limits and Verify Later paths that are difficult to replicate in standard automated test suites.

Why does my extension pass E2E tests but fail on real CUNY login pages?▼

Extensions pass E2E tests but fail on real CUNY login pages because mocked fixtures cannot replicate the actual DOM state, real credential handling, and live SSO environments where real-world extension behavior actually occurs.