skills.rest
latticeHQ
latticeHQOFFICIAL
Explore all skills by this author →
GitHub

tests

Codify testing conventions for TypeScript unit and integration tests.

Updated Aug 27, 2026
Search Tags:#typescript#testing#jest#unit-testing#integration-testing#doctrine
One-click install
npx skills add https://github.com/latticeHQ/latticeWorkbench --skill tests-latticehq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/latticeHQ/latticeWorkbench/tree/main/.lattice/skills/tests
Command: npx skills add https://github.com/latticeHQ/latticeWorkbench --skill tests-latticehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a cohesive testing philosophy that reduces flaky tests and ensures verifiable behavior across unit, integration, and UI tests.

Core Features & Use Cases

  • Colocated tests with source code (e.g., .test.ts[x]) for easy maintenance.
  • Clear guidance for integration tests, unit tests, and end-to-end testing with dedicated tests/* directories.
  • Mocking and test strategy guidelines to avoid tautology and encourage meaningful invariants.

Quick Start

Run the test suite following the prescribed layout and doctrine to validate a new codebase.

Frequently Asked Questions about tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize unit and integration tests in a TypeScript project?▼

Organize TypeScript unit and integration tests by colocating .test.ts[x] files with source code or using dedicated tests/ directories, applying doctrine-driven conventions to reduce flaky tests and verify behavior.

What is the best way to manage mocks in TypeScript testing?▼

Manage mocks in TypeScript testing by following doctrine-driven guidelines that enforce strategies around real vs mock testing, avoiding tautology and encouraging meaningful invariants across your test suite.

Do I need bun and jest to run TypeScript unit tests?▼

Yes, you need bun and jest tooling to execute TypeScript unit tests and integration tests, as the testing doctrine requires these specific runtimes for test execution and configuration.

How does a doctrine-driven testing philosophy reduce flaky tests?▼

A doctrine-driven testing philosophy reduces flaky tests by codifying test layout conventions, mocking strategies, and deterministic utils, ensuring verifiable behavior across unit, integration, and UI tests.

Can I use this testing doctrine for end-to-end UI tests in TypeScript?▼

Yes, the testing doctrine applies to end-to-end UI tests in TypeScript projects, providing clear guidance for integration tests, unit tests, and UI testing with dedicated tests/* directories.

When should I use real dependencies vs mocks in integration tests?▼

Use real dependencies vs mocks in integration tests based on codified doctrine strategies that enforce test-runtime configuration and deterministic utils, avoiding tautology while maintaining meaningful invariants.

Related Skills

Explore More Software Engineering Skills→
codercoder
2.0k

tests

Enforce standardized unit and integration test organization and execution with bun x jest.

Official
Intermediate
advanced-securityadvanced-security
30

create-codeql-query-unit-test-java

Scaffold Java CodeQL query test suites with MCP Server tooling.

Official
Advanced
The13thNodeThe13thNode
3

test-automation

Generate unit, integration, and end-to-end test suites for JavaScript/TypeScript projects.

Community
Advanced
alexsandrocruzalexsandrocruz

javascript-testing-patterns

Guide Jest and Vitest tests for JavaScript and TypeScript projects.

Community
Intermediate