skills.rest
xixiU
xixiUCOMMUNITY
Explore all skills by this author →
GitHub

testing

Automate end-to-end CI/CD QA pipelines from code commit to delivery.

Updated Jun 19, 2020
Search Tags:#automation#deployment#qa#pipeline#sso#ci#cd
One-click install
npx skills add https://github.com/xixiU/yu_config --skill testing-xixiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/xixiU/yu_config/tree/main/claude/skills/sdd-skills/testing
Command: npx skills add https://github.com/xixiU/yu_config --skill testing-xixiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

从代码到验证的完整交付闭环的自动化，显著减少手动干预与重复劳动，提升交付速度与一致性。

Core Features & Use Cases

  • Five-phase automated workflow: 代码提交/PR → 构建部署（依赖排序+版本传播）→ 自动化测试 → 结果报告 → 交付归档。
  • SSO 自动化登录：通过 IFLYTEK_SSO_USERNAME / IFLYTEK_SSO_PASSWORD 环境变量进行统一认证，确保安全接入。
  • 基于规范的执行：spec、contracts、testcases 以任务驱动，构建顺序受依赖关系约束，变更时仅构建有变更的组件。
  • 产出可追溯：提供报告、测试结果 JSON、截图收集、交付记录等证据，便于回溯与审计。
  • 快速起步与独立模式：独立执行 Phase 2/Phase 3，或整条流水线；支持在工作区读取前置文件与知识库。

Quick Start

输入 /testing 启动从提交到交付归档的全流程自动化。

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate a CI/CD pipeline from code commit to delivery?▼

Automate a CI/CD pipeline from code commit to delivery by triggering a five-phase workflow that handles dependency-driven build order, automated testing, consolidated reporting, and delivery archiving with minimal manual intervention.

How does dependency-driven build order work for multi-repository deployments?▼

Dependency-driven build order for multi-repository deployments ensures deterministic builds by analyzing component relationships and propagating API versions, so only changed components are built and validated during the pipeline execution.

How do I handle SSO authentication credentials in an automated QA pipeline?▼

Handle SSO authentication credentials in an automated QA pipeline by configuring environment variables like IFLYTEK_SSO_USERNAME and IFLYTEK_SSO_PASSWORD for secure, unified access during automated testing and deployment phases.

Can I run automated testing independently without executing the full CI/CD workflow?▼

You can run automated testing independently by executing Phase 2 or Phase 3 separately, or by running the entire continuous delivery loop based on spec-driven inputs like testcases.md, contracts.md, and tasks.md.

How do I ensure traceable evidence for CI/CD automated testing results?▼

Ensure traceable evidence for CI/CD automated testing results by generating consolidated reports, test result JSON files, screenshot collections, and delivery records that provide full auditability and retrospective validation.

What are hard gates in a CI/CD pipeline and when do I need them?▼

Hard gates in a CI/CD pipeline are strict validation checkpoints implemented during the build and test phases to ensure only properly validated, changed components proceed to delivery and archiving.

Related Skills

Explore More Software Engineering Skills→
miyamo2miyamo2

kiro-spec-batch

Generate spec.json, requirements.md, design.md, and tasks.md for roadmap features.

Community
Advanced
cmb-sycmb-sy
1

trace-report

Analyze trace.jsonl logs to generate pipeline retrospective markdown reports.

Community
Advanced
KaiserWhoLearnsKaiserWhoLearns

maven-dependency-management

Centralize Maven dependency versions in a parent POM for repeatable builds.

Community
Advanced
onesmartguyonesmartguy
2

gitlab-ci-patterns

Automate GitLab CI/CD pipelines for build, test, and deployment workflows.

Community
Advanced