메뉴
Use when writing tests, choosing test tiers, using test fixtures, or following TDD workflow. Covers the test pyramid (unit/component/integration/e2e), available test doubles, fixture catalog, and market scenarios.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ntrader-testing |
| description | Use when writing tests, choosing test tiers, using test fixtures, or following TDD workflow. Covers the test pyramid (unit/component/integration/e2e), available test doubles, fixture catalog, and market scenarios. |
Full reference:
docs/agent/testing.md
Every feature starts with a failing test. Follow Red-Green-Refactor:
make test-unit)make test-component)make test-integration)make test-e2e)Located in tests/component/doubles/. See docs/agent/testing.md for full API.
from tests.component.doubles import TestTradingEngine, TestOrder, TestPosition
engine = TestTradingEngine(initial_balance=Decimal("10000"))
order = TestOrder(symbol="BTCUSDT", side="BUY", quantity=Decimal("0.5"), order_type="MARKET")
position = TestPosition(symbol="BTCUSDT", quantity=Decimal("0.5"),
entry_price=Decimal("50000"), current_price=Decimal("51000"))
Integration tests MUST use --forked (already configured in make test-integration).
def teardown_method(self):
if self.engine:
self.engine.dispose()
gc.collect()
gc.collect() # Second pass for weak references
@pytest.mark.unit # Pure Python, parallelizable
@pytest.mark.component # Test doubles, parallelizable
@pytest.mark.integration # Nautilus + DB, needs --forked
@pytest.mark.e2e # Sequential, full workflow
See docs/agent/testing.md for fixture catalog, market scenarios, and component fixture reference.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Use when loading market data, working with the Parquet catalog, fetching from IBKR, converting CSV data, or diagnosing data availability issues. Covers the DataCatalogService API, catalog structure, and IBKR client configuration.
Use when running backtests, debugging engine crashes, working with BacktestEngine lifecycle, or encountering segfaults and LogGuard panics. Covers engine setup sequence, result extraction, and C extension isolation.
Use when diagnosing segfaults, test failures, data issues, or engine crashes. Covers LogGuard panics, C extension state leaks, common error messages with fixes, and debugging commands.
Use when creating a new trading strategy, modifying strategy logic, adding indicators, or working on position sizing. Covers the 4-file registration pattern, on_bar() flow, and Nautilus indicator gotchas.
Use when adding web UI pages, API endpoints, chart routes, or working with HTMX/Jinja2 templates. Covers the FastAPI app structure, router registration, HTMX patterns, and Tailwind CSS build process.