Test Writing

Test Writing Skill

Overview

Create thorough test coverage for software components.

Workflow

1. Analyze Code: Understand what needs testing
2. Identify Test Cases:

• Happy path scenarios
• Edge cases
• Error conditions
• Boundary values

1. Write Tests: Create test files following project conventions
2. Verify: Run tests to ensure they pass
3. Document: Add test descriptions

Test Types

Unit Tests

• Test individual functions/methods
• Mock dependencies
• Fast execution
• High coverage

Integration Tests

• Test component interactions
• Real dependencies when possible
• Test data flow
• API contracts

End-to-End Tests

• Test complete user workflows
• Real environment
• Critical paths
• User scenarios

Test Quality Standards

• Clear test names describing what is tested
• Arrange-Act-Assert pattern
• One assertion per test (generally)
• Independent tests (no shared state)
• Fast and reliable

Tools

• view: To read code being tested
• create_file: To create new test files
• run_terminal_command: To execute test suites
• grep_search: To find existing tests

Best Practices

• Test behavior, not implementation
• Cover edge cases thoroughly
• Keep tests maintainable
• Use descriptive test names
• Don't test framework code
• Mock external dependencies

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: KarmaloopAI
• Source: KarmaloopAI/Jiva
• License: MIT
• Homepage: https://www.karmaloop.ai

Install and usage instructions live in the source repository linked above.