Standardize end-to-end test naming, workflows, and environment annotations.
npx skills add https://github.com/alibaba/loongcollector --skill e2e-manual
Please help me install this Agent Skill. Skill: e2e-manual Source: https://github.com/alibaba/loongcollector/tree/main/.cursor/skills/e2e-manual Command: npx skills add https://github.com/alibaba/loongcollector --skill e2e-manual
End-to-end testing often lacks standardization, leading to inconsistent test quality and longer feedback loops. This guide defines a centralized, repeatable approach to E2E tests, covering naming conventions, workflows, and environment annotations to improve maintainability.
Follow the E2E Testing Standards Guide to implement and run standardized end-to-end test workflows.
High-intent search queries and answers about installing and using this skill.
Standardize E2E testing by applying consistent workflows, test naming conventions, environment annotations, and verification steps across host, kubernetes, and docker-compose scenarios. This ensures repeatable test execution and reduces inconsistent test quality.
Effective naming conventions for end-to-end tests standardize test case identification across projects. Applying consistent test naming alongside environment annotations improves test maintainability and ensures reliable verification steps across host, k8s, and docker-compose workflows.
Set up environment annotations by applying standardized workflow templates that tag test execution contexts for host, kubernetes, and docker-compose scenarios. This provides clear environment tracking and consistent logging for reliable end-to-end verification.
Yes, standardized E2E testing templates support consistent test workflows across host, k8s, and docker-compose scenarios. By defining repeatable operational instructions and logging steps, the templates ensure reliable test execution and verification regardless of the deployment target.
End-to-end testing lacks consistency when it lacks standardization across projects. Implementing a centralized approach with standardized test naming, workflow templates, and environment annotations establishes a repeatable structure that improves overall test quality and maintainability.
Yes, defining E2E testing standards requires a SKILL.md file containing a YAML frontmatter with name and description. The Markdown body provides the operational instructions needed to standardize test naming, workflows, and verification steps.
amhuppertCreate and refine Claude Skill units with YAML frontmatter and Markdown instructions.
kilburnRun and debug backend and frontend tests inside Docker containers.
4lermanDetect repository stacks and generate CI/CD pipeline templates for GitHub Actions and GitLab CI.
vignesh2027Manage OpenClaw test selection, debugging, CI checks, and Docker E2E lane verification.
