Struct TestDatabase 

pub struct TestDatabase { /* private fields */ }

Database access for tests.

Test database configuration is intentionally explicit to prevent accidental use of production databases.

Examples

// Option 1: Embedded Postgres (requires embedded-db feature)
// Run with: cargo test --features embedded-db
let db = TestDatabase::embedded().await?;

// Option 2: Explicit URL
let db = TestDatabase::from_url("postgres://localhost/test_db").await?;

// Option 3: From TEST_DATABASE_URL env var
let db = TestDatabase::from_env().await?;

Implementations

impl TestDatabase

pub async fn from_url(url: &str) -> Result<TestDatabase, ForgeError>

Connect to database at the given URL.

Use this for explicit database configuration in tests.

pub async fn from_env() -> Result<TestDatabase, ForgeError>

Connect using TEST_DATABASE_URL environment variable.

Note: This reads TEST_DATABASE_URL (not DATABASE_URL) to prevent accidental use of production databases in tests.

pub fn pool(&self) -> &Pool<Postgres>

Get the connection pool.

pub fn url(&self) -> &str

Get the database URL.

pub async fn execute(&self, sql: &str) -> Result<(), ForgeError>

Run raw SQL to set up test data or schema.

pub async fn isolated( &self, test_name: &str, ) -> Result<IsolatedTestDb, ForgeError>

Creates a dedicated database for a single test, providing full isolation.

Each call creates a new database with a unique name. Use this when tests modify data and could interfere with each other.