'pytest' 검색 결과

REST·GraphQL API 오류를 연결, 인증, 송수신 데이터 순으로 조사합니다. 재현 명령과 원인, 수정안을 정리하고 재발을 감지하는 회귀 테스트 작성을 돕습니다.

• API 인증 오류를 조사합니다
• Postman과 코드의 동작 차이를 재현합니다
• 페이지 분할과 호출 제한을 확인합니다

Python 실행을 멈추고 변수와 실행 흐름을 살펴 오류 원인을 찾습니다. 상황에 따라 pdb와 debugpy를 사용하며, 실패한 테스트와 실행 중인 프로세스도 조사합니다.

• 실패한 테스트의 변수를 확인합니다
• 함수 안에서 컬렉션의 변화를 추적합니다
• 예외 발생 지점의 변수를 확인합니다

Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding features with tests written first
• Reproducing a bug in a test before fixing it
• Refactoring while keeping tests passing

Create or revise skills shipped within the Hermes Agent repository. The guidance covers file placement, required metadata, clear procedures, platform checks, tests, and documentation updates so contributions follow the repository’s authoring standards.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a reusable skill to the Hermes Agent repository
• Revise an existing in-repository SKILL.md
• Choose bundled or optional placement

Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a feature from specifications and designs
• Developing authentication or APIs with tests
• Refactoring code while checking test results

Set up a realtime evaluation folder with a suitable shared harness, the framework that runs evaluations. Prepare prompts, tool definitions, realistic starter data, and a README, then validate the setup with evaluation and test runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a single-turn text-to-speech evaluation
• Set up evaluations using saved audio
• Build multi-turn simulations with mock tools

Build repeatable evaluations for AI agent responses, tool choices, and multi-step tasks. Use reference datasets and scoring criteria to compare changes, detect quality regressions, and set automated checks that must pass before deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare agent quality before and after prompt changes
• Test tool selection and multi-step task execution
• Evaluate resistance to prompt injection

Update Flask-AppBuilder in Apache Airflow’s FAB provider, including pinned versions, dependency locks, and documentation. Check compatibility tests and review copied security code, with asset and database migration updates when the upstream release requires them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrade the FAB provider to a newer Flask-AppBuilder release
• Review upstream authentication fixes against Airflow's copied code
• Resolve compatibility failures after a dependency update

Set up Python projects with uv, manage required packages, and create isolated environments for each project. Covers Python versions, dependency updates, migration from existing tools, and lockfiles that record package versions for repeatable installations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up a new Python project
• Migrate existing package management to uv
• Manage Python versions and isolated environments

Set up Python APIs with FastAPI using organized project templates. Build routes, asynchronous database operations, authentication, and error handling, with examples for sharing dependencies and testing endpoints through a separate test database.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up a new FastAPI project
• Build a Python API with asynchronous database access
• Organize authentication and shared dependencies

Design workflows that evaluate and refine AI outputs through self-review, separate generation and evaluation roles, tests, or weighted scoring criteria. Includes patterns for structured feedback, iteration limits, and stopping when quality stops improving.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding self-review and revision loops to AI outputs
• Separating generation from evaluation
• Refining generated code using test results

Plan features before coding by defining requirements, acceptance criteria, and scope. Validate the specification, generate starter tests from expected behaviors, and guide implementation and review so each delivered feature can be checked against its agreed requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define requirements before implementing a feature
• Turn acceptance criteria into starter tests
• Check specifications for missing requirements

Configure OpenTelemetry to send AI application traces, records of execution steps, to Confident AI. Reuse existing exporters, choose the regional endpoint, and add AI-specific attributes without requiring the deepeval Python package.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Send existing AI application traces to Confident AI
• Configure tracing for a non-Python AI application
• Choose the US or EU endpoint for an API key

Add DeepEval tracing to Python AI applications so execution steps appear in Confident AI. Choose a supported integration or manual @observe instrumentation, then capture inputs, outputs, step types, tags, and metadata.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace execution steps in a Python AI application
• Select tracing integrations for an existing framework
• Add manual tracing with @observe

Merge GitHub pull requests while preserving credit for the original contributors. Covers straightforward merges, conflict resolution, selective file inclusion, duplicate PR closure, and checks that confirm both attribution and working code after integration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merge external contributions while preserving author credit
• Resolve conflicts in a pull request
• Merge selected files from a pull request

Build Python APIs with FastAPI and Pydantic V2, including input validation, database operations that avoid blocking other work, and token-based authentication. Implement REST or WebSocket endpoints, then check their behavior with automated tests and generated API documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build REST APIs with FastAPI
• Validate input data with Pydantic V2
• Implement JWT authentication and authorization

Checks cryptographic code against known attacks and edge cases using Project Wycheproof test vectors, predefined inputs and expected results. Helps load cases, interpret failures, compare implementations, and integrate checks into automated testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing cryptographic code against known attacks
• Comparing results across cryptographic libraries
• Investigating rejected or incorrectly accepted signatures

Set up Python projects and standalone scripts with uv for dependencies, ruff for code checks and formatting, and ty for type checking. Configure tests and project files, or migrate existing workflows when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a Python project or reusable package
• Writing a standalone script with external dependencies
• Configuring formatting, type checks, and tests

Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the test suite for the current repo, auto-detecting Python (pytest/uv), Node (vitest/pnpm), or Rust (cargo test)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running tests before opening a pull request
• Checking Node types before pushing commits
• Getting the CI link after a push

Implement and maintain Nexent's traditional Python UT for product changes and bugfixes under test/backend, test/sdk, and test/ext_components. Cover unit behavior, boundaries, errors and regression assertions with isolated pytest tests. Formal D1-D5 assets in test-e2e use nexent-test-assets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for direct fixes: writing-mstest-tests owns supplied MSTest assertions; code-testing owns new cases. Use test-gap-analysis when asked whether tests would catch a production change, and test-anti-patterns for general severity-ranked audits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.