원클릭으로 Manus에서 모든 스킬 실행

tests-common

스타1,020

포크364

업데이트2026년 3월 26일 10:03

TDD practices and test utilities for suite-common packages, including Red-Green-Refactor workflow and @suite-common/test-utils usage. Use when writing tests for suite-common packages.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

trezor

trezor/trezor-suite

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Writing Common Tests (TDD)

This skill enforces Test-Driven Development (TDD) practices for suite-common packages and ensures proper usage of the @suite-common/test-utils package.

Core Principles

1. Test-First Development

ALWAYS write tests before implementing features in suite-common packages.
Follow the Red-Green-Refactor cycle:
1. Red: Write a failing test that describes the desired behavior. Run test to confirm it fails for the right reason (e.g., "Expected value to be X but got Y").
2. Green: Write the minimum code to make the test pass. Run test to confirm it passes.
3. Refactor: Clean up the code while keeping tests green. Run test to confirm it still passes after refactoring.

2. Writing tests

Focus on testing behavior and user interactions, not implementation details.
Follow arrange-act-assert pattern for test structure.

3. Use @suite-common/test-utils Package

REQUIRED: Use @suite-common/test-utils for all suite-common testing that involves React hooks.
NEVER import directly from @testing-library/react when testing hooks.
The test-utils package provides all necessary utilities including renderHookWithStoreProvider.

Checklist

Before submitting code, ensure:

Tests were written BEFORE implementation
Using @suite-common/test-utils for hook tests (not direct @testing-library/react)
Correct render function used (renderHookWithStoreProvider for hooks needing store, renderHook otherwise)
Fixtures are properly typed
Tests focus on behavior, not implementation
Tests follow naming conventions (.hook.test.ts, .test.ts)
All tests pass locally

이 저장소의 다른 Skills

같은 저장소

publish-config

trezor/trezor-suite

publishConfig rules for public npm packages in the Trezor Suite monorepo. Use when adding or editing publishConfig, exports, or preparing a package for npm publishing.

2026-06-011.0k

packages

trezor/trezor-suite

How to create and structure packages in the Trezor Suite monorepo, including scopes and sizing guidance. Use when creating new packages or resolving cyclic dependencies.

2026-05-251.0k

tests-native

trezor/trezor-suite

Use when writing component or hook tests in suite-native and need to choose between renderWithBasicProvider, renderWithStoreProvider, or store helpers like createStoreFromPreloadedState, createLightStore, or mergePreloadedState.

2026-04-291.0k

security-headers

trezor/trezor-suite

Generated code must be aligned with security headers (e.g. no unsave JS eval). The permissions policy is especially relevant when changing any code related with the `navigator` object.

2026-04-201.0k

trezor-mcp

trezor/trezor-suite

Trigger on any mention of Trezor wallet interaction, crypto addresses, sending crypto, checking balances, signing messages, or hardware wallet operations via MCP. Also trigger when users mention configuring or troubleshooting the Trezor MCP server connection.

2026-04-101.0k

idb-migrations

trezor/trezor-suite

How to create and implement IndexedDB storage migrations in the Trezor Suite web app. Use when writing migrations that transform persisted data between Suite versions.

2026-03-271.0k

name	tests-common
description	TDD practices and test utilities for suite-common packages, including Red-Green-Refactor workflow and @suite-common/test-utils usage. Use when writing tests for suite-common packages.

Writing Common Tests (TDD)

This skill enforces Test-Driven Development (TDD) practices for suite-common packages and ensures proper usage of the @suite-common/test-utils package.

Core Principles

1. Test-First Development

ALWAYS write tests before implementing features in suite-common packages.
Follow the Red-Green-Refactor cycle:
1. Red: Write a failing test that describes the desired behavior. Run test to confirm it fails for the right reason (e.g., "Expected value to be X but got Y").
2. Green: Write the minimum code to make the test pass. Run test to confirm it passes.
3. Refactor: Clean up the code while keeping tests green. Run test to confirm it still passes after refactoring.

2. Writing tests

Focus on testing behavior and user interactions, not implementation details.
Follow arrange-act-assert pattern for test structure.

3. Use @suite-common/test-utils Package

REQUIRED: Use @suite-common/test-utils for all suite-common testing that involves React hooks.
NEVER import directly from @testing-library/react when testing hooks.
The test-utils package provides all necessary utilities including renderHookWithStoreProvider.

Checklist

Before submitting code, ensure:

Tests were written BEFORE implementation
Using @suite-common/test-utils for hook tests (not direct @testing-library/react)
Correct render function used (renderHookWithStoreProvider for hooks needing store, renderHook otherwise)
Fixtures are properly typed
Tests focus on behavior, not implementation
Tests follow naming conventions (.hook.test.ts, .test.ts)
All tests pass locally