# Cicd Testing Integration

> Integrate automated tests into CI/CD pipelines for continuous testing, including pipeline configuration, test automation strategies, reporting, and DevOps collaboration.

- **Type:** Skill
- **Install:** `agentstack add skill-javalenciacai-qaskills-cicd-testing-integration`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [javalenciacai](https://agentstack.voostack.com/s/javalenciacai)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [javalenciacai](https://github.com/javalenciacai)
- **Source:** https://github.com/javalenciacai/QASkills/tree/main/.agents/skills/cicd-testing-integration

## Install

```sh
agentstack add skill-javalenciacai-qaskills-cicd-testing-integration
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# CI/CD Testing Integration

Expert skill for integrating automated testing into CI/CD pipelines and enabling continuous quality feedback.

## When to Use

Use this skill when you need to:
- Set up test automation in CI/CD pipelines
- Configure automated test execution
- Implement continuous testing strategy
- Create test reporting dashboards
- Optimize pipeline performance
- Enable shift-left testing

## CI/CD Testing Strategy

### Test Pyramid for CI/CD

```
        /\
       /UI\         10% - E2E/UI Tests (slow, brittle)
      /────\
     /  API \       30% - Integration/API Tests
    /────────\
   /   UNIT   \     60% - Unit Tests (fast, stable)
  /────────────\
```

**Principle**: More fast tests at bottom, fewer slow tests at top

### Continuous Testing Stages

```
1. Pre-Commit
   - Unit tests (developer runs)
   - Linting/static analysis
   
2. Commit Stage (Fast -  30 minutes → Optimize
- Code coverage decreased → Review
- Flaky test detected → Investigate
```

## Optimization Strategies

### Parallel Execution

```yaml
# Parallelize test suites
jobs:
  test:
    strategy:
      matrix:
        shard: [1, 2, 3, 4]
    steps:
      - run: npm run test:e2e -- --shard=${{ matrix.shard }}/4
```

### Caching Dependencies

```yaml
- name: Cache dependencies
  uses: actions/cache@v3
  with:
    path: ~/.npm
    key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
```

### Smart Test Selection

```bash
# Only run tests affected by changes
changed_files=$(git diff --name-only HEAD~1)
npm run test:selective --files="$changed_files"
```

### Docker Layer Caching

```dockerfile
# Optimize Docker builds
FROM node:18
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
# Dependencies cached here
```

## Environment Management

### Test Environments

```
Development → Integration → QA → Staging → Production
     ↓            ↓          ↓       ↓          ↓
  Unit Tests   API Tests  E2E Tests  Smoke    Monitoring
```

### Configuration Management

```javascript
// config/test.env.js
module.exports = {
  qa: {
    apiUrl: 'https://api-qa.company.com',
    dbHost: 'db-qa.company.com'
  },
  staging: {
    apiUrl: 'https://api-staging.company.com',
    dbHost: 'db-staging.company.com'
  }
};
```

## Integration Patterns

### 1. Pull Request Validation
```
PR Created → Run unit & integration tests
          → Pass? Merge allowed : Block merge
```

### 2. Continuous Deployment
```
Commit → Build → Test → Deploy QA → E2E Tests → Deploy Staging
```

### 3. Nightly Regression
```
Scheduled: 2 AM → Full test suite → Report to team
```

### 4. On-Demand Testing
```
Manual Trigger → Select test suite → Run → Report results
```

## Monitoring & Maintenance

### Pipeline Health

Monitor:
- Build failure trends
- Test execution time trends
- Infrastructure costs
- Resource utilization

### Test Maintenance

Regular activities:
- Remove obsolete tests
- Update flaky tests
- Optimize slow tests
- Review test coverage
- Update test data

## Best Practices

- ✓ Keep pipelines fast (< 10 min for commit stage)
- ✓ Fail fast (run fastest tests first)
- ✓ Run tests in parallel when possible
- ✓ Use containers for consistency
- ✓ Version control everything (code, tests, configs)
- ✓ Secure secrets and credentials
- ✓ Monitor and optimize continuously
- ✓ Make failures visible and actionable
- ✓ Automate as much as possible
- ✓ Collaborate with DevOps team

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [javalenciacai](https://github.com/javalenciacai)
- **Source:** [javalenciacai/QASkills](https://github.com/javalenciacai/QASkills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-javalenciacai-qaskills-cicd-testing-integration
- Seller: https://agentstack.voostack.com/s/javalenciacai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
