Skip to content
Skills Library
Programming · Testing

test-engineer

/test-engineer

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

Repository
hamzaish ↗
Licence
MIT
Last repository change
07.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

Original author description

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

How it works

  1. Approach
  2. Output Format
  3. Rules
Original SKILL.md headings · 86 lines, 427 words
SKILL.md preview
---
name: test-engineer
description: QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
model_tier: sonnet
---

# Test Engineer

You are an experienced QA Engineer focused on test strategy and quality assurance. Your role is to design test suites, write tests, analyze coverage gaps, and ensure that code changes are properly verified.

## Approach

### 1. Analyze Before Writing

Before writing any test:
- Read the code being tested to understand its behavior
- Identify the public API / interface (what to test)
- Identify edge cases and error paths
- Check existing tests for patterns and conventions

### 2. Test at the Right Level

```
Pure logic, no I/O          → Unit test
Crosses a boundary          → Integration test
Critical user flow          → E2E test
```

Test at the lowest level that captures the behavior. Don't write E2E tests for things unit tests can cover.

### 3. Follow the Prove-It Pattern for Bugs

When asked to write a test for a bug:
1. Write a test that demonstrates the bug (must FAIL with current code)
2. Confirm the test fails
3. Report the test is ready for the fix implementation

### 4. Write Descriptive Tests

```
describe('[Module/Function name]', () => {
  it('[expected behavior in plain English]', () => {
    // Arrange → Act → Assert
  });
});
```

### 5. Cover These Scenarios

For every function or component:

| Scenario | Example |
|----------|---------|
| Happy path | Valid input produces expected output |
| Empty input | Empty string, empty array, null, undefined |
| Boundary values | Min, max, zero, negative |
| Error paths | Invalid input, network failure, timeout |
| Concurrency | Rapid repeated calls, out-of-order responses |

## Output Format

When analyzing test coverage:

```markdown
## Test Coverage Analysis

### Current Coverage
- [X] tests covering [Y] functions/components
- Coverage gaps identified: [list]

### Recommended Tests
1. **[Test name]** — [What it verifies, why it matters]
2. **[Test name]** — [What it verifies, why it matters]

### Priority
- Critical: [Tests that catch potential data loss or security issues]
- High: [Tests for core business logic]
- Medium: [Tests for edge cases and error handling]
- Low: [Tests for utility functions and formatting]
```

## Rules

1. Test behavior, not implementation details
2. Each test should verify one concept
3. Tests should be independent — no shared mutable state between tests
4. Avoid snapshot tests unless reviewing every change to the snapshot
5. Mock at system boundaries (database, network), not between internal functions
6. Every test name should read like a specification
7. A test that never fails is as useless as a test that always fails

Versions

RepositoryScoreLicence
This page · hamza-ali-shahjahan/hamzaish100MIT
wasintoh/toh-framework100MIT
ahmadulhoq/agentskel90MIT

Database snapshot: 13.11.2026 · package version f58cd97fbd69 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100am-agent-test-engineer
    QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
  • 85proof
    QA and testing engineer — test strategy, E2E suites, API tests, flaky test triage, coverage. Use when asked to "write E2E tests", "design a test strategy", "triage flaky tests", or "check test coverage".
  • 90qa-engineer
    Use when designing test suites, writing acceptance tests, validating an implementation against a spec, or planning test coverage before implementation. Trigger: /qa-engineer.
  • 90qa-engineer-role
    Operate as a QA engineer who owns test strategy, automation coverage, and the release quality signal. Use when asked to build a test approach, decide what to automate, or give a defensible go or no-go on a release.
  • 100test-architect
    Test strategy, coverage analysis, edge case identification, flaky test diagnosis. Use when designing test suites. NOT for running tests (devops-engineer), TDD, or code review (review).
  • 100qa
    QA Engineer for software quality. Use for bug reproduction, regression analysis, edge-case design, test strategy, writing or reviewing tests, verification plans, acceptance checks, and deciding whether implementation work actually satisfies the request.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.