Automated Testing in CI/CD

Automate test execution and gating in CI/CD pipelines for medical devices.

26|6|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/AminAlam/meddev-agent-skills --skill automated-testing-in-ci-cd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Automated Testing in CI/CD
Source: https://github.com/AminAlam/meddev-agent-skills/tree/main/ci-cd/automated-testing
Command: npx skills add https://github.com/AminAlam/meddev-agent-skills --skill automated-testing-in-ci-cd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of integrating automated testing into Continuous Integration and Continuous Deployment (CI/CD) pipelines, ensuring code quality and preventing regressions in medical device software.

Core Features & Use Cases

  • Automated Test Execution: Integrates unit, integration, and system/HIL (or simulator) tests into CI/CD pipelines.
  • Pipeline Gating: Configures pipelines to fail on test failures, preventing unverified code from progressing.
  • Artifact Management: Ensures test results, logs, and coverage reports are captured and retained for auditability.
  • Flaky Test Handling: Provides mechanisms to detect, track, and address flaky tests.
  • Use Case: Automatically run all unit tests on every code commit, fail the build if any test fails, and store the test results as artifacts for review.

Quick Start

Integrate automated testing into your CI/CD pipeline by adding the provided test script to your pipeline configuration.

Frequently Asked Questions about Automated Testing in CI/CD

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

FAQPage Schema
How do I gate a CI/CD pipeline to block unverified code from progressing?

Pipeline gating blocks code progression by configuring CI/CD pipelines to fail on test failures. This ensures unverified code cannot advance, maintaining software quality and preventing regressions in medical device software.

How do I handle flaky tests in automated CI/CD pipelines?

Flaky test handling in CI/CD pipelines provides mechanisms to detect, track, and address flaky tests. This prevents intermittent failures from disrupting automated testing and maintains pipeline reliability for medical device software.

Can I use automated testing in CI/CD for hardware-in-the-loop test scheduling?

Automated testing in CI/CD supports hardware test scheduling, including HIL and simulator tests. It integrates unit, integration, and system tests into pipelines, ensuring safety-related modules are covered for medical devices.

What is the best way to manage test artifacts and coverage reports for medical device software auditing?

Artifact management in CI/CD pipelines captures and retains test results, logs, and coverage reports for auditability. This ensures medical device software testing outputs are stored securely and remain available for regulatory review.

Does automated testing in CI/CD require integrating unit and integration tests separately?

Automated testing in CI/CD integrates unit, integration, and system tests into pipelines simultaneously. This comprehensive test scope ensures safety-related modules are covered without requiring separate configurations for each test type.

Why does my CI/CD pipeline need flake detection for medical device software?

Flake detection is needed in CI/CD pipelines to identify and track flaky tests that produce intermittent failures. This maintains automated testing reliability and ensures consistent pipeline gating for medical device software safety.