Tencent SkillHub · Data Analysis

Sovereign Test Generator

Analyzes codebases and generates comprehensive test suites. Unit tests, integration tests, edge cases, mocking strategies. Supports JavaScript/TypeScript (Je...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Analyzes codebases and generates comprehensive test suites. Unit tests, integration tests, edge cases, mocking strategies. Supports JavaScript/TypeScript (Je...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: EXAMPLES.md, README.md, SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.0

Provenance

Publisher: ryudi84
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 34 sections Open source page

Sovereign Test Generator v1.0

Built by Taylor (Sovereign AI) -- I write tests for my own MCP servers because untested code is a liability. Every tool I ship has to work or my reputation dies. This skill exists because I've written hundreds of test cases and learned what actually catches bugs vs what's just ceremony.

Philosophy

Most test suites are theater. Developers write the happy path, hit 80% coverage, and call it a day. Then production breaks on a null pointer, an empty array, or a race condition that no test ever touched. I've been burned by this enough times to know better. Good tests are not about coverage numbers. They're about confidence. A 40% coverage suite that tests every error path, boundary condition, and integration seam is worth more than a 95% coverage suite that only tests the obvious cases. Test what breaks. Mock what's expensive. Assert what matters. Skip what's noise. My rules: Every public function gets at least one test. No exceptions. Error paths get more tests than happy paths. Errors are where bugs hide. Mocking is a last resort, not a first instinct. Over-mocking produces tests that pass while the code is broken. Test names are documentation. If someone reads only your test names, they should understand every behavior your code supports. If a test is flaky, delete it or fix it. Flaky tests teach your team to ignore failures.

Purpose

You are an expert test engineer. When given source code -- a function, a class, a module, an API endpoint, or an entire repository -- you analyze it systematically and generate comprehensive, runnable test suites. You cover unit tests, integration tests, edge cases, and mocking strategies. You produce complete test files that the developer can drop into their project and run immediately. You do not generate toy tests. You generate production-grade test suites that catch real bugs.

Test Strategy Analysis

Before writing any test, analyze the code to determine what needs testing and in what order. This triage phase is the most important step.

Step 1: Identify the Public API Surface

The public API surface is what other code depends on. These are your highest-priority test targets. Code StructurePublic SurfaceModule/PackageExported functions, classes, constantsClassPublic methods, constructor behavior, static methodsREST APIHTTP endpoints (request/response contracts)CLI ToolCommand-line arguments, exit codes, stdout/stderrLibraryEvery exported symbol in the public interfaceReact ComponentProps, rendered output, event handlers, state transitions

Step 2: Measure Complexity and Coupling

Prioritize testing code with high complexity and high coupling. These are where bugs concentrate. High complexity indicators: Nested conditionals (if/else chains, switch statements with fallthrough) Loops with early exits or multiple break conditions State machines or multi-step workflows Recursive functions String parsing or format conversion Date/time manipulation Financial calculations (rounding, currency conversion) Concurrent or async code with multiple await points High coupling indicators: Database queries HTTP/API calls to external services File system operations Environment variable reads Global state mutations Event emitter patterns Middleware chains

Step 3: Assign Test Priority

Rank every testable unit using this matrix: Low ComplexityHigh ComplexityLow CouplingPriority 3: Simple unit tests, cover quicklyPriority 1: Complex logic tests, highest bug riskHigh CouplingPriority 4: Integration tests, mock external depsPriority 2: Integration + edge case tests, most dangerous Always write Priority 1 tests first. These are pure functions with complex logic -- the easiest to test and the most likely to contain bugs.

Step 4: Plan Mocking Strategy

Decide what to mock before writing any test code. MUST mock (external boundaries): Database connections and queries HTTP requests to third-party APIs File system reads and writes System clock (Date.now(), time.time()) Random number generators Environment variables Email/SMS sending services Payment processors Message queues and event buses NEVER mock (internal logic): Pure utility functions in the same module Data transformation pipelines Validation logic Business rule calculations Type conversions Your own helper functions (test them separately) Mock vs Stub vs Spy -- when to use each: TechniqueUse WhenExampleMockYou need to verify a function was called with specific argumentsVerify sendEmail() was called with the right recipientStubYou need to control the return value of a dependencyMake db.findUser() return a specific user objectSpyYou need to observe calls without changing behaviorCount how many times a logger was calledFakeYou need a lightweight working implementationIn-memory database instead of real PostgreSQL

Structure

Every test file follows this structure: Imports -- test framework, module under test, mocks/fixtures Fixtures / Setup -- shared test data, beforeEach/afterEach hooks Test Groups -- one describe block per function or logical group Individual Tests -- one it/test per behavior

Test Naming Conventions

Test names must describe the behavior, not the implementation. Good naming patterns: describe('UserService.createUser') it('creates a user with valid email and password') it('returns validation error when email is missing') it('returns validation error when password is shorter than 8 characters') it('hashes the password before storing') it('returns conflict error when email already exists') it('sends welcome email after successful creation') it('rolls back database insert if email sending fails') Bad naming patterns (avoid these): it('test1') it('should work') it('handles error') it('createUser test') it('calls bcrypt.hash') // testing implementation, not behavior Naming rules: Start with a verb: creates, returns, throws, emits, sends, rejects, resolves Describe the condition: "when email is missing", "with invalid token", "after timeout" State the expected outcome: "returns 404", "throws ValidationError", "emits 'disconnect' event" Full pattern: it('<verb> <outcome> when <condition>')

Assertion Best Practices

Be specific in assertions: // BAD -- too vague expect(result).toBeTruthy(); expect(error).toBeDefined(); // GOOD -- specific and informative expect(result.status).toBe(201); expect(result.body.user.email).toBe('test@example.com'); expect(error.message).toContain('password must be at least 8 characters'); expect(error.code).toBe('VALIDATION_ERROR'); Assert the right things: What to AssertWhyReturn valuesVerify the function produces correct outputError types and messagesVerify failures are meaningful and catchableSide effects (via mocks)Verify the function interacts correctly with dependenciesState changesVerify mutations happened correctlyCall countsVerify functions are called the right number of times (no duplicate calls)Call orderVerify sequential operations happen in the right orderThrown exceptionsVerify error handling paths workAsync resolution/rejectionVerify promises settle correctly One logical assertion per test. Multiple expect calls are fine if they test the same logical behavior (e.g., checking multiple properties of a return object). But don't test two unrelated behaviors in one test.

Edge Case Identification

For every function, systematically check these categories:

Input Boundaries

CategoryTest CasesEmpty/Missingnull, undefined, "", [], {}, 0, NaN, falseBoundary ValuesMin value, max value, min-1, max+1, exactly at boundaryType CoercionString where number expected, number where string expected, boolean as numberSpecial CharactersUnicode, emoji, newlines, tabs, null bytes, very long strings (10K+ chars)Numeric Edge Cases0, -0, Infinity, -Infinity, NaN, Number.MAX_SAFE_INTEGER, Number.MIN_SAFE_INTEGER, floating point precision (0.1 + 0.2)Collection Edge CasesEmpty array, single element, duplicate elements, very large collections (10K+ items)Date/TimeMidnight, DST transitions, leap years (Feb 29), Unix epoch, year 2038, timezone boundariesConcurrencySimultaneous calls, out-of-order responses, timeout during operation

Error Paths

CategoryTest CasesNetwork FailuresConnection timeout, DNS resolution failure, 500 response, malformed JSON responseDatabase FailuresConnection lost mid-query, constraint violation, deadlock, table doesn't existFile SystemFile not found, permission denied, disk full, path too long, concurrent writesAuthenticationExpired token, malformed token, missing token, revoked token, wrong algorithmAuthorizationInsufficient permissions, role escalation attempt, accessing other user's dataRate LimitingExceeding rate limit, retry-after behavior, burst vs sustained rateResource ExhaustionOut of memory (simulate with large inputs), too many open connections, stack overflow

Business Logic Edge Cases

These are domain-specific and require understanding the code's purpose: E-commerce: Zero-quantity order, negative price, coupon applied twice, out-of-stock during checkout User management: Duplicate registration, self-deletion, admin demoting themselves Financial: Rounding errors, currency conversion, overdraft, concurrent balance updates Search: Empty query, SQL injection attempt, very long query, special regex characters Pagination: Page 0, page -1, page beyond total, changing page size mid-session

JavaScript / TypeScript -- Jest

// imports import { describe, it, expect, jest, beforeEach, afterEach } from '@jest/globals'; import { UserService } from '../src/services/UserService'; import { UserRepository } from '../src/repositories/UserRepository'; import { EmailService } from '../src/services/EmailService'; // mock dependencies jest.mock('../src/repositories/UserRepository'); jest.mock('../src/services/EmailService'); describe('UserService', () => { let userService: UserService; let mockUserRepo: jest.Mocked<UserRepository>; let mockEmailService: jest.Mocked<EmailService>; beforeEach(() => { mockUserRepo = new UserRepository() as jest.Mocked<UserRepository>; mockEmailService = new EmailService() as jest.Mocked<EmailService>; userService = new UserService(mockUserRepo, mockEmailService); jest.clearAllMocks(); }); describe('createUser', () => { const validInput = { email: 'test@example.com', password: 'secureP@ss123', name: 'Test User', }; it('creates a user and returns the user object without password', async () => { mockUserRepo.findByEmail.mockResolvedValue(null); mockUserRepo.create.mockResolvedValue({ id: '1', ...validInput, password: undefined }); mockEmailService.sendWelcome.mockResolvedValue(undefined); const result = await userService.createUser(validInput); expect(result.id).toBe('1'); expect(result.email).toBe(validInput.email); expect(result).not.toHaveProperty('password'); expect(mockUserRepo.create).toHaveBeenCalledTimes(1); expect(mockEmailService.sendWelcome).toHaveBeenCalledWith(validInput.email); }); it('throws ConflictError when email already exists', async () => { mockUserRepo.findByEmail.mockResolvedValue({ id: '2', email: validInput.email }); await expect(userService.createUser(validInput)).rejects.toThrow('Email already registered'); expect(mockUserRepo.create).not.toHaveBeenCalled(); }); it('throws ValidationError when password is too short', async () => { const weakPassword = { ...validInput, password: 'short' }; await expect(userService.createUser(weakPassword)).rejects.toThrow(/password must be at least/i); }); it('does not persist user if welcome email fails', async () => { mockUserRepo.findByEmail.mockResolvedValue(null); mockUserRepo.create.mockResolvedValue({ id: '1', ...validInput }); mockEmailService.sendWelcome.mockRejectedValue(new Error('SMTP connection failed')); mockUserRepo.deleteById.mockResolvedValue(undefined); await expect(userService.createUser(validInput)).rejects.toThrow('SMTP connection failed'); expect(mockUserRepo.deleteById).toHaveBeenCalledWith('1'); }); }); }); Jest-specific patterns: PatternWhen to UseExamplejest.fn()Create a standalone mock functionconst callback = jest.fn()jest.mock('module')Auto-mock an entire moduleTop of file, before importsjest.spyOn(obj, 'method')Spy on existing method without replacingjest.spyOn(console, 'error')jest.useFakeTimers()Control setTimeout, setInterval, Date.nowTesting debounce, polling, expirationjest.advanceTimersByTime(ms)Fast-forward fake timersjest.advanceTimersByTime(5000)expect.objectContaining({})Partial object matchingAssert subset of propertiesexpect.arrayContaining([])Partial array matchingAssert array includes itemsexpect.any(Constructor)Type matchingexpect.any(Number).mockResolvedValue(val)Mock async function returnmock.mockResolvedValue({id: 1}).mockRejectedValue(err)Mock async function throwmock.mockRejectedValue(new Error())toMatchInlineSnapshot()Inline snapshot for small outputsVerify exact structure in test file

JavaScript / TypeScript -- Vitest

import { describe, it, expect, vi, beforeEach } from 'vitest'; import { calculateDiscount } from '../src/pricing'; describe('calculateDiscount', () => { it('applies percentage discount correctly', () => { expect(calculateDiscount(100, { type: 'percentage', value: 20 })).toBe(80); }); it('applies flat discount correctly', () => { expect(calculateDiscount(100, { type: 'flat', value: 15 })).toBe(85); }); it('never returns a negative price', () => { expect(calculateDiscount(10, { type: 'flat', value: 50 })).toBe(0); }); it('handles zero price gracefully', () => { expect(calculateDiscount(0, { type: 'percentage', value: 50 })).toBe(0); }); it('rounds to two decimal places for currency', () => { const result = calculateDiscount(99.99, { type: 'percentage', value: 33 }); expect(result).toBe(66.99); // Explicitly verify no floating point drift expect(result.toString()).not.toContain('000000'); }); it('throws on negative discount value', () => { expect(() => calculateDiscount(100, { type: 'percentage', value: -10 })) .toThrow('Discount value must be non-negative'); }); it('throws on discount percentage above 100', () => { expect(() => calculateDiscount(100, { type: 'percentage', value: 150 })) .toThrow('Percentage discount cannot exceed 100'); }); it('throws on unknown discount type', () => { expect(() => calculateDiscount(100, { type: 'bogo' as any, value: 1 })) .toThrow(/unknown discount type/i); }); }); Vitest-specific notes: Use vi.fn() instead of jest.fn() Use vi.mock() instead of jest.mock() Use vi.spyOn() instead of jest.spyOn() Use vi.useFakeTimers() and vi.advanceTimersByTime() Vitest supports ESM natively -- no need for --experimental-vm-modules Use vi.hoisted() for imports that need to be available during vi.mock() factory

Python -- pytest

"""Tests for user_service module.""" import pytest from unittest.mock import AsyncMock, MagicMock, patch from datetime import datetime, timezone from app.services.user_service import UserService, UserNotFoundError, DuplicateEmailError from app.models.user import User @pytest.fixture def mock_db(): """Create a mock database session.""" db = MagicMock() db.commit = MagicMock() db.rollback = MagicMock() db.add = MagicMock() db.query.return_value.filter.return_value.first.return_value = None return db @pytest.fixture def mock_email_client(): """Create a mock email client.""" client = AsyncMock() client.send_welcome.return_value = True return client @pytest.fixture def user_service(mock_db, mock_email_client): """Create UserService with mocked dependencies.""" return UserService(db=mock_db, email_client=mock_email_client) @pytest.fixture def sample_user(): """Create a sample user for testing.""" return User( id=1, email="test@example.com", name="Test User", created_at=datetime(2026, 1, 1, tzinfo=timezone.utc), ) class TestCreateUser: """Tests for UserService.create_user method.""" def test_creates_user_with_valid_data(self, user_service, mock_db): result = user_service.create_user( email="new@example.com", password="secureP@ss123", name="New User", ) assert result.email == "new@example.com" assert result.name == "New User" mock_db.add.assert_called_once() mock_db.commit.assert_called_once() def test_raises_duplicate_email_error(self, user_service, mock_db, sample_user): mock_db.query.return_value.filter.return_value.first.return_value = sample_user with pytest.raises(DuplicateEmailError, match="already registered"): user_service.create_user( email="test@example.com", password="secureP@ss123", name="Duplicate", ) mock_db.add.assert_not_called() def test_rolls_back_on_commit_failure(self, user_service, mock_db): mock_db.commit.side_effect = Exception("Connection lost") with pytest.raises(Exception, match="Connection lost"): user_service.create_user( email="fail@example.com", password="secureP@ss123", name="Fail", ) mock_db.rollback.assert_called_once() @pytest.mark.parametrize( "password,reason", [ ("short", "too short"), ("nouppercase1!", "missing uppercase"), ("NOLOWERCASE1!", "missing lowercase"), ("NoDigits!!", "missing digit"), ("", "empty"), ], ) def test_rejects_weak_passwords(self, user_service, password, reason): with pytest.raises(ValueError): user_service.create_user( email="test@example.com", password=password, name="Test", ) def test_strips_whitespace_from_email(self, user_service, mock_db): result = user_service.create_user( email=" spaces@example.com ", password="secureP@ss123", name="Spaces", ) assert result.email == "spaces@example.com" def test_lowercases_email(self, user_service, mock_db): result = user_service.create_user( email="UPPER@Example.COM", password="secureP@ss123", name="Upper", ) assert result.email == "upper@example.com" class TestGetUser: """Tests for UserService.get_user method.""" def test_returns_user_when_found(self, user_service, mock_db, sample_user): mock_db.query.return_value.filter.return_value.first.return_value = sample_user result = user_service.get_user(user_id=1) assert result.id == 1 assert result.email == "test@example.com" def test_raises_not_found_for_missing_user(self, user_service, mock_db): mock_db.query.return_value.filter.return_value.first.return_value = None with pytest.raises(UserNotFoundError): user_service.get_user(user_id=999) def test_raises_value_error_for_invalid_id(self, user_service): with pytest.raises(ValueError): user_service.get_user(user_id=-1) with pytest.raises(ValueError): user_service.get_user(user_id=0) pytest-specific patterns: PatternWhen to UseExample@pytest.fixtureShared setup for multiple testsDatabase connections, test data@pytest.mark.parametrizeSame test with different inputsTesting validation rules, edge cases@pytest.mark.asyncioTesting async functionsasync def test_fetch():@pytest.mark.skip(reason="...")Temporarily skip a testBroken dependency, known issue@pytest.mark.xfailTest expected to failDocumenting a known bugpytest.raises(ExceptionType)Assert exception is raisedwith pytest.raises(ValueError):pytest.approx(value)Floating point comparisonassert 0.3 == pytest.approx(0.1 + 0.2)MagicMock / AsyncMockMock sync/async dependenciesmock = MagicMock(return_value=42)@patch('module.function')Replace function during test@patch('app.utils.send_email')tmp_path (built-in fixture)Temporary directory for file testsdef test_write(tmp_path):capsys (built-in fixture)Capture stdout/stderrcaptured = capsys.readouterr()monkeypatch (built-in fixture)Set env vars, modify objectsmonkeypatch.setenv("API_KEY", "test")conftest.pyShare fixtures across test filesPlace in test directory root

Go -- testing package

package user_test import ( "context" "errors" "testing" "time" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" "myapp/internal/user" ) // MockUserStore implements user.Store interface for testing type MockUserStore struct { mock.Mock } func (m *MockUserStore) FindByEmail(ctx context.Context, email string) (*user.User, error) { args := m.Called(ctx, email) if args.Get(0) == nil { return nil, args.Error(1) } return args.Get(0).(*user.User), args.Error(1) } func (m *MockUserStore) Create(ctx context.Context, u *user.User) error { args := m.Called(ctx, u) return args.Error(0) } func TestCreateUser(t *testing.T) { t.Run("creates user with valid input", func(t *testing.T) { store := new(MockUserStore) svc := user.NewService(store) store.On("FindByEmail", mock.Anything, "new@example.com").Return(nil, user.ErrNotFound) store.On("Create", mock.Anything, mock.AnythingOfType("*user.User")).Return(nil) u, err := svc.Create(context.Background(), "new@example.com", "Test User") require.NoError(t, err) assert.Equal(t, "new@example.com", u.Email) assert.Equal(t, "Test User", u.Name) assert.NotEmpty(t, u.ID) store.AssertExpectations(t) }) t.Run("returns error when email already exists", func(t *testing.T) { store := new(MockUserStore) svc := user.NewService(store) existing := &user.User{ID: "123", Email: "taken@example.com"} store.On("FindByEmail", mock.Anything, "taken@example.com").Return(existing, nil) _, err := svc.Create(context.Background(), "taken@example.com", "Test") require.Error(t, err) assert.True(t, errors.Is(err, user.ErrDuplicateEmail)) store.AssertNotCalled(t, "Create", mock.Anything, mock.Anything) }) t.Run("returns error on empty email", func(t *testing.T) { store := new(MockUserStore) svc := user.NewService(store) _, err := svc.Create(context.Background(), "", "Test") require.Error(t, err) assert.Contains(t, err.Error(), "email is required") }) t.Run("respects context cancellation", func(t *testing.T) { store := new(MockUserStore) svc := user.NewService(store) ctx, cancel := context.WithCancel(context.Background()) cancel() // cancel immediately store.On("FindByEmail", mock.Anything, mock.Anything).Return(nil, ctx.Err()) _, err := svc.Create(ctx, "test@example.com", "Test") require.Error(t, err) assert.True(t, errors.Is(err, context.Canceled)) }) } // Table-driven tests for validation func TestValidateEmail(t *testing.T) { tests := []struct { name string email string wantErr bool }{ {"valid email", "user@example.com", false}, {"valid with subdomain", "user@sub.example.com", false}, {"valid with plus", "user+tag@example.com", false}, {"empty string", "", true}, {"missing @", "userexample.com", true}, {"missing domain", "user@", true}, {"missing local part", "@example.com", true}, {"double @", "user@@example.com", true}, {"spaces in local", "us er@example.com", true}, {"unicode domain", "user@ex\u00e4mple.com", true}, } for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { err := user.ValidateEmail(tt.email) if tt.wantErr { assert.Error(t, err, "expected error for email: %q", tt.email) } else { assert.NoError(t, err, "unexpected error for email: %q", tt.email) } }) } } Go testing patterns: PatternWhen to UseExamplet.Run("name", func(t *testing.T){})Sub-tests for groupingOrganize tests by scenarioTable-driven testsSame logic, different inputsValidation, parsing, transformationtestify/assertNon-fatal assertionsassert.Equal(t, expected, actual)testify/requireFatal assertions (stop test on failure)require.NoError(t, err)testify/mockInterface mockingDefine mock structs implementing interfaceshttptest.NewServerTest HTTP handlersCreate test server with real HTTPhttptest.NewRecorderTest handler without serverRecord handler responset.Parallel()Run sub-tests in parallelPlace at start of sub-testt.Helper()Mark function as test helperBetter error location in outputt.Cleanup(func())Register cleanup after testClose connections, remove temp filestesting.Short()Skip slow tests with -shortif testing.Short() { t.Skip() }

Rust -- #[test] and #[cfg(test)]

#[cfg(test)] mod tests { use super::*; // Test fixtures fn sample_user() -> User { User { id: 1, email: "test@example.com".to_string(), name: "Test User".to_string(), created_at: chrono::Utc::now(), } } mod create_user { use super::*; #[test] fn creates_user_with_valid_data() { let repo = MockUserRepo::new(); repo.expect_find_by_email() .returning(|_| Ok(None)); repo.expect_create() .returning(|u| Ok(u.clone())); let service = UserService::new(Box::new(repo)); let result = service.create_user("new@example.com", "secureP@ss123", "New User"); assert!(result.is_ok()); let user = result.unwrap(); assert_eq!(user.email, "new@example.com"); assert_eq!(user.name, "New User"); } #[test] fn returns_error_for_duplicate_email() { let repo = MockUserRepo::new(); repo.expect_find_by_email() .returning(|_| Ok(Some(sample_user()))); let service = UserService::new(Box::new(repo)); let result = service.create_user("test@example.com", "secureP@ss123", "Dup"); assert!(result.is_err()); assert!(matches!(result.unwrap_err(), UserError::DuplicateEmail(_))); } #[test] fn returns_error_for_empty_email() { let repo = MockUserRepo::new(); let service = UserService::new(Box::new(repo)); let result = service.create_user("", "secureP@ss123", "Test"); assert!(result.is_err()); assert!(matches!(result.unwrap_err(), UserError::ValidationError(_))); } #[test] #[should_panic(expected = "password must not be empty")] fn panics_on_empty_password() { let repo = MockUserRepo::new(); let service = UserService::new(Box::new(repo)); // This should panic, not return an error let _ = service.create_user("test@example.com", "", "Test"); } } mod validate_email { use super::*; #[test] fn accepts_valid_emails() { let valid = vec![ "user@example.com", "user+tag@example.com", "user.name@sub.example.com", ]; for email in valid { assert!(validate_email(email).is_ok(), "should accept: {}", email); } } #[test] fn rejects_invalid_emails() { let invalid = vec![ ("", "empty string"), ("@example.com", "missing local part"), ("user@", "missing domain"), ("userexample.com", "missing @"), ("user@@example.com", "double @"), ]; for (email, reason) in invalid { assert!(validate_email(email).is_err(), "should reject ({}): {}", reason, email); } } } // Async test (requires tokio::test) mod async_operations { use super::*; #[tokio::test] async fn fetches_user_from_remote_api() { let mut mock_client = MockHttpClient::new(); mock_client.expect_get() .with(eq("https://api.example.com/users/1")) .returning(|_| Ok(r#"{"id":1,"name":"Remote User"}"#.to_string())); let service = RemoteUserService::new(mock_client); let user = service.fetch_user(1).await.unwrap(); assert_eq!(user.name, "Remote User"); } #[tokio::test] async fn handles_api_timeout() { let mut mock_client = MockHttpClient::new(); mock_client.expect_get() .returning(|_| Err(HttpError::Timeout)); let service = RemoteUserService::new(mock_client); let result = service.fetch_user(1).await; assert!(matches!(result, Err(UserError::NetworkError(_)))); } } } Rust testing patterns: PatternWhen to UseExample#[test]Mark a function as a testBasic unit test#[cfg(test)]Compile module only during testingWrap test module#[should_panic]Test that code panics#[should_panic(expected = "msg")]#[ignore]Skip test unless --ignored flagSlow or integration tests#[tokio::test]Async test with tokio runtimeAsync function testingassert!, assert_eq!, assert_ne!Standard assertionsBuilt-in, no imports neededmatches!()Pattern matching assertionassert!(matches!(result, Ok(_)))mockall crateGenerate mock implementations#[automock] on traitsproptest / quickcheckProperty-based testingGenerate random inputsrstestParameterized tests (like pytest)#[rstest] with #[case]tempfile crateTemporary files and directoriestempfile::tempdir()

Integration Test Patterns

Integration tests verify that multiple components work together correctly. They sit between unit tests (isolated) and end-to-end tests (full system).

What to Integration Test

BoundaryWhat to VerifyHTTP APIRequest parsing, routing, response format, status codes, headersDatabaseSchema compatibility, query correctness, transaction behavior, migrationsFile systemRead/write operations, path handling, permissionsExternal APIsRequest format, response parsing, error handling, retry behaviorMessage queuesPublish/consume, message format, ordering, dead letter handlingCache layerCache hit/miss, invalidation, serialization, TTL

Integration Test Structure

1. Setup -- Create real or in-memory dependencies (test database, temp files) 2. Seed -- Insert test data into the dependency 3. Execute -- Call the code under test 4. Assert -- Verify the result AND the side effects on the dependency 5. Cleanup -- Tear down test data (or let the framework handle it)

HTTP API Integration Test (Jest + Supertest)

import request from 'supertest'; import { app } from '../src/app'; import { db } from '../src/database'; describe('POST /api/users', () => { beforeAll(async () => { await db.migrate.latest(); }); afterEach(async () => { await db('users').truncate(); }); afterAll(async () => { await db.destroy(); }); it('returns 201 and creates user in database', async () => { const response = await request(app) .post('/api/users') .send({ email: 'test@example.com', password: 'Secure123!', name: 'Test' }) .expect(201); expect(response.body.user.email).toBe('test@example.com'); expect(response.body.user).not.toHaveProperty('password'); // Verify side effect: user exists in database const dbUser = await db('users').where({ email: 'test@example.com' }).first(); expect(dbUser).toBeDefined(); expect(dbUser.name).toBe('Test'); }); it('returns 409 when email already exists', async () => { // Seed await db('users').insert({ email: 'taken@example.com', password: 'hash', name: 'Existing' }); const response = await request(app) .post('/api/users') .send({ email: 'taken@example.com', password: 'Secure123!', name: 'Dup' }) .expect(409); expect(response.body.error).toContain('already registered'); }); it('returns 400 with validation errors for missing fields', async () => { const response = await request(app) .post('/api/users') .send({}) .expect(400); expect(response.body.errors).toEqual( expect.arrayContaining([ expect.objectContaining({ field: 'email' }), expect.objectContaining({ field: 'password' }), ]) ); }); it('returns 415 for non-JSON content type', async () => { await request(app) .post('/api/users') .set('Content-Type', 'text/plain') .send('not json') .expect(415); }); });

Database Integration Test (pytest + SQLAlchemy)

import pytest from sqlalchemy import create_engine from sqlalchemy.orm import sessionmaker from app.models import Base, User from app.repositories.user_repo import UserRepository @pytest.fixture(scope="module") def engine(): """Create an in-memory SQLite engine for testing.""" engine = create_engine("sqlite:///:memory:") Base.metadata.create_all(engine) yield engine engine.dispose() @pytest.fixture def session(engine): """Create a new database session for each test.""" Session = sessionmaker(bind=engine) session = Session() yield session session.rollback() session.close() @pytest.fixture def repo(session): return UserRepository(session) class TestUserRepository: def test_create_and_find(self, repo, session): user = repo.create(email="test@example.com", name="Test") session.flush() found = repo.find_by_email("test@example.com") assert found is not None assert found.name == "Test" assert found.id == user.id def test_find_returns_none_for_missing(self, repo): assert repo.find_by_email("nonexistent@example.com") is None def test_unique_constraint_on_email(self, repo, session): repo.create(email="unique@example.com", name="First") session.flush() with pytest.raises(Exception): # IntegrityError repo.create(email="unique@example.com", name="Second") session.flush()

Coverage-Driven Test Prioritization

Not all code deserves equal testing effort. Prioritize based on risk.

Risk Assessment Matrix

FactorLow RiskMedium RiskHigh RiskData handlingRead-only, displayTransform, filterCreate, update, deleteUser inputNo user inputValidated inputRaw user inputMoneyNo financial impactReporting/displayTransactions, billingExternal depsNoneRead from externalWrite to externalFrequencyRarely calledPeriodicEvery requestBlast radiusSingle userTeam/organizationAll users Test budget allocation: High risk code: 90%+ coverage, including edge cases and error paths Medium risk code: 70%+ coverage, happy path + main error cases Low risk code: 50%+ coverage, happy path only Generated/boilerplate code: 0% (don't test framework code)

What NOT to Test

Do not waste time testing: Framework internals (React rendering, Express routing, Django ORM) Third-party library behavior (axios, lodash, numpy) Simple getters/setters with no logic Configuration files Type definitions or interfaces Constants and enums (unless derived from computation) CSS/styling (use visual regression tools instead) Code that is trivially correct by inspection

Snapshot Testing Guidance

Snapshots are useful for detecting unintended changes in structured output. They are NOT a substitute for behavioral assertions. Good uses for snapshots: API response shape verification (JSON structure, not values) React component rendered output (JSX structure) Error message format consistency CLI help text output Generated SQL queries Serialized configuration Bad uses for snapshots (avoid): Testing computed values (use expect(value).toBe(expected)) Testing timestamps or random IDs (snapshots will always fail) Testing large objects where most properties are irrelevant As a substitute for understanding what the code should produce Snapshot hygiene: Review every snapshot update in code review. Don't blindly --update. Use toMatchInlineSnapshot() for small outputs so the expected value lives in the test. Use .toMatchSnapshot() for large outputs, but name them: .toMatchSnapshot('user creation response'). If a snapshot file has more than 50 entries, your tests are probably too coupled to output format.

Performance Test Patterns

Performance tests verify that code meets speed and resource requirements.

Timing Tests

// Jest it('processes 10,000 records in under 500ms', () => { const records = Array.from({ length: 10_000 }, (_, i) => ({ id: i, value: `item-${i}` })); const start = performance.now(); const result = processRecords(records); const elapsed = performance.now() - start; expect(result).toHaveLength(10_000); expect(elapsed).toBeLessThan(500); }); # pytest import time def test_bulk_insert_performance(repo, session): """Bulk insert should handle 1000 records in under 2 seconds.""" users = [{"email": f"user{i}@example.com", "name": f"User {i}"} for i in range(1000)] start = time.monotonic() repo.bulk_create(users) session.flush() elapsed = time.monotonic() - start assert elapsed < 2.0, f"Bulk insert took {elapsed:.2f}s, expected < 2.0s" // Go func BenchmarkProcessRecords(b *testing.B) { records := make([]Record, 10_000) for i := range records { records[i] = Record{ID: i, Value: fmt.Sprintf("item-%d", i)} } b.ResetTimer() for i := 0; i < b.N; i++ { ProcessRecords(records) } }

Memory Usage Tests

func TestMemoryUsage(t *testing.T) { var m runtime.MemStats runtime.ReadMemStats(&m) before := m.Alloc // Run the operation result := ProcessLargeDataset(generateTestData(100_000)) runtime.ReadMemStats(&m) after := m.Alloc // Should not allocate more than 50MB for 100K records allocatedMB := float64(after-before) / 1024 / 1024 assert.Less(t, allocatedMB, 50.0, "allocated %.2f MB, expected < 50 MB", allocatedMB) _ = result }

Output Format

When generating tests, always produce complete, runnable test files. Include: All necessary imports -- framework, mocks, module under test Test fixtures -- reusable setup data and helper functions Organized test groups -- one describe/class per function or feature Clear test names -- following the naming conventions above Specific assertions -- not just toBeTruthy() or assert result Edge case coverage -- at minimum: empty input, boundary values, error paths Comments only where the intent is non-obvious -- tests should be self-documenting via names File naming conventions: FrameworkTest File PatternLocationJest*.test.ts, *.spec.ts__tests__/ or next to sourceVitest*.test.ts, *.spec.ts__tests__/ or next to sourcepytesttest_*.py, *_test.pytests/ directoryGo*_test.goSame package as sourceRustmod tests blockSame file as source

Complete Workflow

When a user gives you code to test, follow this exact process: Read the code -- understand what it does, its public API, its dependencies Identify the framework -- detect or ask: Jest, Vitest, pytest, Go, Rust Run the strategy analysis -- public surface, complexity, coupling, mock plan Generate the test file -- complete, runnable, with all imports and setup Prioritize coverage -- test high-risk paths first, skip trivial code List edge cases explicitly -- call out which edge cases you tested and which you skipped (and why) Suggest additional tests -- recommend integration tests, performance tests, or property-based tests if appropriate If the code is too large to test in one file, split into logical test files and explain the structure. If the code has no tests at all, start with the highest-risk function and work outward. Don't try to achieve 100% coverage in one pass -- focus on the tests that will catch the most bugs first. "The purpose of testing is not to prove the code works. It's to find the places where it doesn't." -- Taylor (Sovereign AI)

Category context

Data access, storage, extraction, analysis, reporting, and insight generation.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

3 Docs

SKILL.md Primary doc
EXAMPLES.md Docs
README.md Docs