Skip to content
Back to skills

Api Testing 4

ASecurity

This skill should be used when the user asks to "test an API", "write API tests", "mock API responses", "validate API endpoints", or needs guidance on REST API testing strategies.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
testingbashtestingapi

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill api-testing-4 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Testing 4?

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

Security grade badge for Api Testing 4
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-api-testing-4/badge)](https://www.skillsdirectory.com/skills/david-li0406-api-testing-4)

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: API Testing
description: This skill should be used when the user asks to "test an API", "write API tests", "mock API responses", "validate API endpoints", or needs guidance on REST API testing strategies.
---

# API Testing

This skill provides guidance for testing REST APIs effectively.

## Quick Start

Test a simple endpoint:
```bash
curl -X GET https://api.example.com/users \
  -H "Authorization: Bearer $TOKEN"
```

## Testing Workflow

1. **Identify endpoints** - List all endpoints to test
2. **Set up test environment** - Configure base URL, auth tokens
3. **Write test cases** - Cover success, error, edge cases
4. **Run tests** - Execute and collect results
5. **Validate responses** - Check status codes, body, headers

## Common Test Cases

### Success Cases

- Valid request returns expected data
- Pagination works correctly
- Filtering/sorting produces correct results

### Error Cases

- Invalid auth returns 401
- Missing required fields return 400
- Non-existent resource returns 404
- Rate limiting returns 429

### Edge Cases

- Empty results return empty array, not null
- Large payloads handled correctly
- Special characters in inputs escaped properly

## Response Validation

Check these elements:
- **Status code**: 200, 201, 400, 401, 404, 500
- **Response body**: JSON structure matches schema
- **Headers**: Content-Type, pagination headers
- **Timing**: Response within acceptable limits

## Additional Resources

For detailed testing patterns and advanced techniques:

- **`references/detailed-guide.md`** - Comprehensive testing patterns, authentication strategies, and mock server setup

Files in this skill

  • SKILL.md1.6 KB
  • references/detailed-guide.md3.7 KB

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…