無料GitHub で公開

nexent-python-tests

Maintain the legacy implementation-oriented Nexent Python unit tests under test/backend, test/sdk, and test/ext_components. Use for pytest fixtures, lookup-site mocking, async behavior, isolation, and regression assertions in those existing suites. Do not create or maintain the requirement-driven D1-D5 baseline, automation, or manifest.

ModelEngine-Group/nexent

インストール方法を見る

含まれるファイル（1）

SKILL.md2.5 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Nexent legacy Python unit tests

Paths below are relative to the repository root.

These tests are a legacy suite kept separate from the requirement-driven D1-D5 system. Do not assign formal D1-D5 case IDs to them, add them to test/manifests/d1-d5.yaml, or count them in the generated functional baseline. Use nexent-test-assets for new D1-D5 work.

Identify the unit and behavior. Inspect neighboring tests, test/conftest.py, and test/pytest.ini before changing fixture/import setup.
Use pytest exclusively, pytest assertions, fixtures, and pytest-mock. Files/functions start with test_; test classes start with Test. Keep files below 500 lines or split by feature using test_<module>_<feature>.py; split package directories include __init__.py.
Import the unit and necessary test helpers. Mock collaborators rather than exercising external interfaces/clients/services. Patch the fully qualified lookup site determined from actual imports, not the dependency's definition module.

For example, if backend.services.example_service imports fetch using from provider import fetch, patch backend.services.example_service.fetch. If the runtime loads the module as services.example_service, use that actual path. Do not copy an unrelated service path from an example.

Isolate external I/O and APIs. Reset mutable state with fixtures; use autouse=True when every test in a scope requires it. Do not mock away the behavior being asserted.
Cover changed success/error flows and boundaries with specific observable assertions. Use side_effect for collaborator errors, @pytest.mark.parametrize for variants, and @pytest.mark.asyncio for async tests. Async collaborators need awaitable mocks.
Order imports as standard library, third-party, then project; write comments/docstrings in English.
Run narrow tests from the root with a working backend environment, such as pytest test/backend/apps/test_agent_app.py -v. Broaden when needed; python test/run_all_test.py is the existing broad runner.

Report commands, results, and environment failures. Unit-test isolation does not replace live-service functional checks or real-model acceptance.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

external-memory-plugin

無料

Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an existing memory plugin, validating partner adapters, or diagnosing plugin discovery, authentication, retrieval, ingestion, or CI failures.

日本語の概要は準備中です。原文の説明を表示しています。