Test writing

Skill KarmaloopAI/Jiva/examples/personas/tester/skills/test-writing

Jiva is a CLI-first, open source autonomous AI agent and open alternative to Claude. Written in TypeScript with native support for Sarvam-105B and gpt-oss-120b, it autonomously plans and executes tasks from your terminal. Supports MCP servers, a built-in Skills system, and Jiva Personas - a plugin framework fully compatible with Claude Plugins.

Install

npx -y skills add KarmaloopAI/Jiva --skill test-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.

SKILL.md

1.5 KB, as published. Nobody here has run it

Test Writing Skill

Overview

Create thorough test coverage for software components.

Workflow

Analyze Code: Understand what needs testing
Identify Test Cases:
- Happy path scenarios
- Edge cases
- Error conditions
- Boundary values
Write Tests: Create test files following project conventions
Verify: Run tests to ensure they pass
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