CodeVetter · Repo Unpack · Testing signals
SeaQL/sea-orm
Tests and CI were inspected, not executed; their existence does not establish passing results. The sampled suites combine Rust unit tests, async adapters, mock SQL assertions, live database integration, generation fixtures, and conversion tests. Feature gates and conditional CI jobs materially affect coverage, and this investigation does not establish exhaustive coverage or security validation.
- Integration tests using #[sea_orm_macros::test] become ordinary Rust tests gated on SQLx drivers in async mode or rusqlite in sync mode; the async wrapper executes through runtime-specific block_on macros.
- MockDatabase queues execution/query results and errors and records statements; sampled smol_potat cursor tests assert result reversal and exact PostgreSQL SQL/values, which verifies construction rather than a live database executing that SQL.
- The SQLite basic integration flow checks initial save, update through save, count, primary-key lookup, deletion, and final absence; common integration setup creates and drops named MySQL/PostgreSQL databases.
- Codegen writer tests compare parsed generated token streams against checked-in expanded fixtures, including schema-qualified variants; root rustfmt configuration excludes codegen tests_cfg because formatting changes test expectations.
- CLI generation tests cover URL database-name extraction and panic expectations for malformed or incomplete URLs; the inspected tests do not establish end-to-end schema discovery, output recovery, or identifier-escaping correctness.
- Migration tests use #[tokio::test] and DATABASE_URL, exercise multiple migrators/schema names and transaction tests, and assert that read-only status APIs leave a missing tracking table absent before and after queries.
- RBAC integration tests configure role inheritance and verify permitted versus denied inserts on restricted connections and transactions; Arrow unit tests assert primitive values and nullable cells restored from RecordBatch.
- Inspected CI defines workspace, RBAC, registry, CLI, SQLite, sync-rusqlite, and PostgreSQL test commands, plus compile-only combinations and example jobs; commit keywords select partial backend runs, and --no-run stages are compilation rather than test execution. None of these jobs was executed or its outcome retrieved during this investigation.