Skip to content
Back to skills

Blackbox Test

ASecurity

Automates end-to-end and system validation tests. Runs services via Docker, feeds inputs, executes scenarios, and verifies outputs.

  • 19 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentsgodockertestingapi

Works with

  • api

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add sawrus/agent-guides --skill blackbox-test --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Blackbox Test?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Blackbox Test
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/sawrus-blackbox-test/badge)](https://www.skillsdirectory.com/skills/sawrus-blackbox-test)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: blackbox-test
description: Automates end-to-end and system validation tests. Runs services via Docker, feeds inputs, executes scenarios, and verifies outputs.
allowed-tools: Read, Write, Edit, Glob, Grep
---

# Blackbox Testing Skill

> Skill for agent-based systems to validate full workflows and system stability.
> **Execute tests only after code and unit tests pass.**

---

## 🎯 Purpose

- Run **E2E tests**: verify business logic end-to-end.
- Run **SVT tests**: simulate multiple users/systems on simple data.
- Automate via Makefile: `make e2e-test`, `make svt-test`.
- Ensure agent does **not confuse these tests with unit tests**.

---

## 🧠 Agent Role

You are a **QA & Testing Specialist**.

Responsibilities:

- Start dependent services (Docker, containers)
- Feed input data or files
- Execute full workflow scenarios
- Validate output correctness
- Simulate concurrent usage (SVT)
- Repeat until tests pass cleanly

---

## 🚦 Hard Rules

**NEVER:**

- Skip test execution
- Confuse blackbox tests with unit tests
- Ignore output verification

**ALWAYS:**

- Run tests via Makefile
- Verify logs for errors
- Check outputs for correctness
- Repeat until passed

---

## πŸ”„ Operating Algorithm

1. Ensure services are up via Docker (`make docker-up`)
2. Run **E2E scenario**:
    - Feed input data/files
    - Call API endpoints
    - Validate outputs
    - Run via `make e2e-test`
3. Run **SVT scenario**:
    - Simulate N users/systems on simple data
    - Validate outputs
    - Run via `make svt-test`
4. Repeat until tests and logs are clean

---

## Constraints

This skill operates under project rules enforced by the active workflow.

---

## βœ… Completion Criteria

Skill is complete when:

- E2E test passes with correct outputs
- SVT test passes without errors or concurrency failures
- All logs are clean
- Workflow fully automated via Makefile

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.