<< All versions

Skill v1.0.0

currentAutomated scan100/100
aj-geddes/useful-ai-prompts/continuous-testing
──Details
PublishedOctober 1, 2026 at 12:21 AM
Content Hashsha256:7d8416ba5b866899...
Git SHA3f5182cfd739
──Files
Files (1 file, 2.7 KB)
SKILL.md2.7 KBactive
SKILL.md · 104 lines · 2.7 KB

version: "1.0.0" name: continuous-testing description: > Integrate automated testing into CI/CD pipelines for continuous quality feedback. Use for continuous testing, CI testing, automated testing pipelines, test orchestration, and DevOps quality practices.


Continuous Testing

Table of Contents

Overview

Continuous testing integrates automated testing throughout the software development lifecycle, providing rapid feedback on quality at every stage. It shifts testing left in the development process and ensures that code changes are validated automatically before reaching production.

When to Use

  • Setting up CI/CD pipelines
  • Automating test execution on commits
  • Implementing shift-left testing
  • Running tests in parallel
  • Creating test gates for deployments
  • Monitoring test health
  • Optimizing test execution time
  • Establishing quality gates

Quick Start

Minimal working example:

yaml
# .github/workflows/ci.yml
name: Continuous Testing
on:
push:
branches: [main, develop]
pull_request:
branches: [main, develop]
env:
NODE_VERSION: "18"
jobs:
# Unit tests - Fast feedback
unit-tests:
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- uses: actions/checkout@v3
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: ${{ env.NODE_VERSION }}
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
GitHub Actions CI PipelineGitHub Actions CI Pipeline
GitLab CI PipelineGitLab CI Pipeline
Jenkins PipelineJenkins Pipeline
Test Selection StrategyTest Selection Strategy
Flaky Test DetectionFlaky Test Detection
Test Metrics DashboardTest Metrics Dashboard

Best Practices

✅ DO

  • Run fast tests first (unit → integration → E2E)
  • Parallelize test execution
  • Cache dependencies
  • Set appropriate timeouts
  • Monitor test health and flakiness
  • Implement quality gates
  • Use test selection strategies
  • Generate comprehensive reports

❌ DON'T

  • Run all tests sequentially
  • Ignore flaky tests
  • Skip test maintenance
  • Allow tests to depend on each other
  • Run slow tests on every commit
  • Deploy with failing tests
  • Ignore test execution time
  • Skip security scanning
All versions