skills.rest
influxdata
influxdataOFFICIAL
Explore all skills by this author →
Website𝕏@InfluxDBGitHub

cypress-e2e-testing

Run Cypress E2E tests against Hugo documentation pages on port 1315.

80|330|Updated Dec 13, 2018
Search Tags:#testing#docs#cypress#e2e-testing#hugo#qa-automation
One-click install
npx skills add https://github.com/influxdata/docs-v2 --skill cypress-e2e-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cypress-e2e-testing
Source: https://github.com/influxdata/docs-v2/tree/main/.claude/skills/cypress-e2e-testing
Command: npx skills add https://github.com/influxdata/docs-v2 --skill cypress-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the execution, validation, and failure analysis of Cypress E2E tests for the InfluxData documentation site.

Core Features & Use Cases

  • Automatically start Hugo server on port 1315, or reuse a running instance to speed up iterations.
  • Run Cypress E2E test suites against mapped content pages using the provided run-e2e-specs.js helper.
  • Analyze test results and failures with structured output and guidance for debugging.
  • Use case: Validate a new docs draft by running end-to-end tests and confirming pages and links render correctly.

Quick Start

Use the skill to run a content page test with the helper, e.g. node cypress/support/run-e2e-specs.js content/influxdb3/core/_index.md

Frequently Asked Questions about cypress-e2e-testing

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

FAQPage Schema
How do I run Cypress E2E tests for Hugo documentation sites?▼

To run Cypress E2E tests for Hugo documentation, use the run-e2e-specs.js helper to automatically start Hugo on port 1315, map content pages to URLs, and execute predefined test specs against the rendered pages.

Can I reuse a running Hugo server instance for Cypress E2E testing?▼

Yes, Cypress E2E testing can automatically start a Hugo server on port 1315 or reuse a running instance to speed up iterations. This optimizes QA workflows by avoiding redundant server restarts during test cycles.

Do I need Node.js to automate Cypress end-to-end testing for docs?▼

Yes, Node.js is required to automate Cypress E2E testing for docs. The testing process relies on Node.js to execute the run-e2e-specs.js helper, which coordinates the Hugo server and Cypress test suites.

How do I analyze Cypress E2E test failures for documentation pages?▼

You can analyze Cypress E2E test failures using the structured output and debugging guidance provided by the skill. This helps identify issues with documentation content, broken links, or UI behavior across different environments.

What's the best way to validate link integrity in InfluxData documentation?▼

The best way to validate link integrity in InfluxData documentation is by running Cypress E2E tests through the run-e2e-specs.js helper, which checks rendering and link behavior across mapped content pages and environments.

Why does my Cypress E2E test fail when mapping Hugo content to URLs?▼

Cypress E2E test failures during Hugo content to URL mapping may occur if the Hugo server is not running on port 1315 or if content pages are not correctly structured. The skill provides structured output to help debug these issues.

Related Skills

Explore More Software Engineering Skills→
jaydubya818jaydubya818

test-browser

Run end-to-end browser tests on routes affected by a PR or branch.

Community
Intermediate
bitovibitovi
46

debug-e2e-test

Diagnose Playwright E2E test failures by analyzing output, screenshots, and logs.

Official
Intermediate
unfinishablemapunfinishablemap
3

check-links

Crawl local Hugo sites and report broken internal links.

Community
Basic
kody-wkody-w

content-burst-publishing

Automate frame-by-frame content publishing cycles for static sites and documentation repositories.

Community
Intermediate