菜单
Writing and running tests for the Uvicore framework itself. Covers the bin/test*.sh scripts, the app1 reference-app fixture + in-memory SQLite bootstrap in tests/conftest.py, async pytest patterns, and where tests for each subsystem live. Use whenever adding/changing framework behavior that needs test coverage, or when running the suite.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use at the END of any substantive task in this repo (new feature, behavior change, notable refactor, non-trivial fix, doc/skill change) to append a dated journal entry, and WHENEVER you make a significant, hard-to-reverse architectural decision to also write an ADR. Covers the journal/ and adr/ folder conventions, the entry templates, ADR numbering and the supersede rule, and the repo-vs-machine-local knowledge principle. Invoke before finishing work so durable reasoning lands in the repo, not just in chat.
End-to-end workflow for adding a new capability to the Uvicore framework itself — a new bound service, a new framework package (provider + config + mixin), a new provider register_* helper, a new IoC-bound type, or a new CLI/event/job. Use when extending the framework's own feature set (not when building an app on top of Uvicore).
Core mental model for the Uvicore framework: the bootstrap sequence, IoC container, Application, Package, Provider lifecycle, the @uvicore decorators, and the IoC override/_BASE mechanism. Read this BEFORE editing anything under uvicore/foundation, uvicore/container, uvicore/package, or any provider/register/boot code, or when you need to understand how services are bound and resolved.
Working on the Uvicore ORM internals under uvicore/orm/ — Model, ModelMetaclass, Field, relations (BelongsTo/HasMany/HasOne/BelongsToMany/Morph*), the async ORM query builder, the mapper, and model lifecycle hooks. Read before editing model.py, metaclass.py, fields.py, query.py, mapper.py, or drivers/.
Quick public-API reference for Uvicore's leaf service subsystems that don't have a dedicated skill — templating (Jinja2), mail, redis, cache, logging, auth (UserInfo/authenticators/guards), and the exception classes (SmartException + HTTP exceptions + status codes). Use when working on or wiring up uvicore/templating, uvicore/mail, uvicore/redis, uvicore/cache, uvicore/logging, uvicore/auth, or uvicore/exceptions.
Run this WHENEVER you make a substantive change to the Uvicore framework (new feature, new/changed/removed/renamed public API, new config key, new CLI/event/job, or any user-observable behavior change) — ideally before you consider the change done. A framework code change is NOT complete until its matching TESTS and DOCS are updated. Docs means both the relevant docs/docs feature page(s) AND the epologue trio: release-notes, the major-version changelog, and the version upgrade guide. Use this because framework changes routinely ship without tests or docs — close that gap every time.
基于 SOC 职业分类
| name | uvicore-testing |
| description | Writing and running tests for the Uvicore framework itself. Covers the bin/test*.sh scripts, the app1 reference-app fixture + in-memory SQLite bootstrap in tests/conftest.py, async pytest patterns, and where tests for each subsystem live. Use whenever adding/changing framework behavior that needs test coverage, or when running the suite. |
| user-invocable | true |
Framework tests live in tests/ and run against the app1 reference app
(tests/apps/app1/) booted against an in-memory SQLite database. Reuse the existing fixtures
and app — do not invent a new bootstrap flow.
This repo uses Poetry — run everything through poetry run, from the framework/ directory.
poetry run ./bin/test.sh — sets PYTHONPATH=./tests/apps, runs pytest with color,
ignores tests/test_database, passes extra args through. (~500 tests, a few seconds.)poetry run ./bin/test.sh tests/test_db/test_orm or
poetry run ./bin/test.sh tests/test_db/test_orm/test_find.py.poetry run ./bin/test-cov.sh (term-missing over uvicore + tests/apps/app1), HTML
via poetry run ./bin/test-cov-html.sh.poetry run ./bin/black-check.sh.tests/conftest.py)event_loop — session-scoped loop.app1 (session, async) — the workhorse fixture. It:
from app1.package import bootstrap; bootstrap.Application(is_console=False)() (boots the full
Uvicore app — providers register + boot).console.events.command.PytestStartup (the DB layer listens → connects all DBs).db.drop_tables/create_tables/seed_tables('app1') to build + seed the in-memory schema.PytestShutdown (disconnect).client (session, async) — httpx.AsyncClient(app=uvicore.app.http, base_url='http://testserver')
for HTTP tests.Every test that touches the app takes the app1 fixture (and client for HTTP). Imports of
models/services go inside the test fn (after the app is booted), e.g.:
@pytest.mark.asyncio
async def test_orm_query_first(app1):
from uvicore.auth.models.user import User
users = await User.query().limit(1).get()
assert len(users) > 0
tests/ folders: test_auth, test_cache, test_configuration, test_console, test_contracts, test_db/{test_builder,test_orm,test_raw,test_sa,test_hybrid}, test_exceptions, test_foundation, test_http, test_http_client, test_ioc, test_jobs, test_logging, test_mail, test_package, test_redis, test_templating, test_typing, test_unit/test_support. (ORM tests live under
test_db/test_orm/, not a separate top-level test_orm.) IoC container + overrides → test_ioc/;
HTTP routing → test_http/ with live API behavior in test_api/; events → test_events.py. Plus
the cross-db matrix in tests/integration/. Genuinely cross-cutting top-level files:
test_uvicore.py, test_events.py, test_integration.py. Don't add loose top-level test_*.py files
for things that belong in a subsystem folder.
Put new framework tests in the closest matching folder. Do not add tests under tests/apps/
unless the change is about the stub app itself.
registers toggles.tests/test_db/test_orm/ has one file per relation), query building,
callbacks, lifecycle hooks; assert real query results, not just types.client fixture; Guard/scope enforcement.tests/test_contracts/.@pytest.mark.asyncio for async tests; depend on shared fixtures, keep setup minimal.